wavacity.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 82 days left4 years old
95
wavacity.com was registered on 12 Sep 2022 via Squarespace Domains II LLC and the registry expiry is 12 Sep 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/wavacity.com.
wavacity.com publishes 4 nameservers. DNSSEC is signed.
wavacity.com has 1 IPv4 address (34.111.9.130). The geolocation database places 34.111.9.130 in Kansas City, United States.
The TLS certificate from WR3 is valid and has 82 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Google Cloud, Google Cloud CDN, HSTS, HTTP/3 and Nginx. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for wavacity.com in the checks that ran.
Domain · RDAP/WHOIS
wavacity.com was registered on 12 Sep 2022 via Squarespace Domains II LLC. The registry returned 2 status values and 4 nameservers from https://rdap.verisign.com/com/v1/domain/wavacity.com.
| Registered | since 12 Sep 2022 |
|---|---|
| Created | 12 September 2022 |
| Updated | 29 August 2026 |
| Expires | 12 September 2027 |
| Registrar | Squarespace Domains II LLC |
| Status | client delete prohibited, client transfer prohibited |
| Nameservers | ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/wavacity.com |
wavacity.com carries the status "client delete prohibited". The registrar has asked the registry to refuse a delete. This is an EPP status on the domain object. It does not say the website is safe, and it does not name the person who registered it.
wavacity.com carries the status "client transfer prohibited". The registrar has asked the registry to refuse a transfer to another registrar. The status is a lock on the domain object. It is not evidence about the content of the site.
Nameserver ns-cloud-d1.googledomains.com is published for wavacity.com in the registration record from https://rdap.verisign.com/com/v1/domain/wavacity.com.
Nameserver ns-cloud-d2.googledomains.com is published for wavacity.com in the registration record from https://rdap.verisign.com/com/v1/domain/wavacity.com.
Nameserver ns-cloud-d3.googledomains.com is published for wavacity.com in the registration record from https://rdap.verisign.com/com/v1/domain/wavacity.com.
Nameserver ns-cloud-d4.googledomains.com is published for wavacity.com in the registration record from https://rdap.verisign.com/com/v1/domain/wavacity.com.
DNS
wavacity.com has 1 address record, 5 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 34.111.9.130 |
|---|---|
| AAAA | — |
| NS | ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com |
| MX | aspmx.l.google.com (1) Google, alt1.aspmx.l.google.com (5) Google, alt2.aspmx.l.google.com (5) Google, alt3.aspmx.l.google.com (10) Google, alt4.aspmx.l.google.com (10) Google |
| SPF | present |
| DMARC | present |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at wavacity.com is "v=spf1 include:_spf.google.com ~all".
The DMARC text record at _dmarc.wavacity.com is "v=DMARC1; p=none; rua=mailto:[email protected]; pct=100; adkim=s; aspf=s".
IPv4 address 34.111.9.130 answers for wavacity.com at resolver 1.1.1.1:53.
Mail exchanger aspmx.l.google.com has preference 1. The host is recognised as Google.
Mail exchanger alt1.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt2.aspmx.l.google.com has preference 5. The host is recognised as Google.
Mail exchanger alt3.aspmx.l.google.com has preference 10. The host is recognised as Google.
Mail exchanger alt4.aspmx.l.google.com has preference 10. The host is recognised as Google.
Hosting and geo
wavacity.com is placed in Kansas City, United States by the local geolocation database (db-ip).
| Address | 34.111.9.130 |
|---|---|
| Country | United States |
| City | Kansas City |
| Source | db-ip |
SSL/TLS
The certificate for wavacity.com is valid, with 82 days left and 1 subject alternative name. Source: tls:443.
| Issuer | WR3 |
|---|---|
| Subject | wavacity.com |
| Valid from | 23 October 2026 |
| Valid until | 21 January 2027 |
| Days left | 82 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: wavacity.com.
Tech stack
Tech detection checked the fetched homepage and named 5 products. Source: wappalyzergo.
- Google Cloud · IaaS
- Google Cloud CDN · CDN
- HSTS · Security
- HTTP/3 · Miscellaneous
- Nginx · Web servers, Reverse proxies
Google Cloud is filed under IaaS.
Google Cloud CDN is filed under CDN.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
Nginx is filed under Web servers, Reverse proxies.
On-page checks
The homepage returned HTTP 200 in 6 ms. The target title is 48 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 6 ms |
| Title length | 48 yes |
| Quoted title | "Wavacity | Online Audio Editor Based on Audacity" |
| Meta description | "Wavacity is a port of the Audacity audio editor to the web browser. Free and open-source. No install required." yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | yes |
| X-Frame-Options | DENY |
| Robots meta | — |
| Canonical | — |
| Language | en |
| Links | 5 |
| Images | 1 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Security
Family DNS for wavacity.com is clear, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | clear |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | yes |
| CSP | yes |
Google Web Risk did not run. No API key is configured, and this report does not invent a clean result from that service.
Score breakdown
Availability 25 of 25. DNS answer plus a homepage status in the 2xx or 3xx range.
TLS 20 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 15 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 15 of 15. HSTS, CSP, and X-Frame-Options or CSP frame-ancestors.
Safety lists 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 5 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: geo city changed from empty to Kansas City.
- October 2026: geo country changed from empty to United States.
Questions
Is wavacity.com safe?
The checks that ran did not produce a safety warning, and a score is not a promise that the site is safe.
Who hosts wavacity.com?
wavacity.com is placed in Kansas City, United States.
When does wavacity.com expire?
wavacity.com expires on 12 September 2027 according to https://rdap.verisign.com/com/v1/domain/wavacity.com.
Who owns wavacity.com?
The registry did not return a person or a company for wavacity.com. RDAP often redacts the registrant. The registrar on file is Squarespace Domains II LLC.
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/wavacity.com at 2026-10-30T14:19:41Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:19:41Z
- TLS source tls:443 at 2026-10-30T14:19:41Z
- HTTP source https://wavacity.com/ at 2026-10-30T14:19:41Z
- Tech source wappalyzergo at 2026-10-30T14:19:41Z
- Geo source db-ip at 2026-10-30T14:19:41Z
- Safety source family DNS and local lists at 2026-10-30T14:19:41Z
Related reports
No other indexable reports share this TLD, host, or registrar yet.
Owner of this site?
Ask for a correction or for the report to be removed from search. Public DNS facts stay on the page. An optional badge is not inserted for you.
How to read this report
The sentences under each heading are filled from the latest snapshot. If a collector had nothing to say, that sentence is left out. The target site's own title and meta description, when shown, are quoted as measurements. They are not this page's title. Change history only lists a difference between two snapshots, so the first check starts the clock and later edits are the history. A malware blocklist is the only reason the homepage body is skipped. That fact stays on the report. It does not by itself drop the page from the sitemap or from related-report links.