nnia.space
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: 42 days left6 years old
55
nnia.space was registered on 24 May 2020 via Tucows Domains Inc. and the registry expiry is 24 May 2027. WHOIS data came from RDAP at https://rdap.radix.host/rdap/domain/nnia.space.
nnia.space publishes 2 nameservers. DNSSEC is not signed.
nnia.space has 2 IPv4 addresses (104.21.20.183, 172.67.194.13) and 2 IPv6 addresses (2606:4700:3034::6815:14b7, 2606:4700:3037::ac43:c20d). The geolocation database places 104.21.20.183 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 42 days left (TLS 1.3).
No safety warning was recorded for nnia.space in the checks that ran.
Domain · RDAP/WHOIS
nnia.space was registered on 24 May 2020 via Tucows Domains Inc.. The registry returned 2 status values and 2 nameservers from https://rdap.radix.host/rdap/domain/nnia.space.
| Registered | since 24 May 2020 |
|---|---|
| Created | 24 May 2020 |
| Updated | 26 May 2026 |
| Expires | 24 May 2027 |
| Registrar | Tucows Domains Inc. |
| Status | client transfer prohibited, client update prohibited |
| Nameservers | colin.ns.cloudflare.com, veda.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.radix.host/rdap/domain/nnia.space |
nnia.space 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.
nnia.space carries the status "client update prohibited". The registrar has asked the registry to refuse updates to the domain object. Contact and nameserver changes wait until the lock is lifted by the registrar of record.
Nameserver colin.ns.cloudflare.com is published for nnia.space in the registration record from https://rdap.radix.host/rdap/domain/nnia.space.
Nameserver veda.ns.cloudflare.com is published for nnia.space in the registration record from https://rdap.radix.host/rdap/domain/nnia.space.
DNS
nnia.space has 4 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.20.183, 172.67.194.13 |
|---|---|
| AAAA | 2606:4700:3034::6815:14b7, 2606:4700:3037::ac43:c20d |
| NS | colin.ns.cloudflare.com, veda.ns.cloudflare.com |
| MX | pegging.liberato.io (0) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at nnia.space is "v=spf1 mx a:furry.adultrefuge.com ip4:207.148.79.230 ~all".
IPv4 address 104.21.20.183 answers for nnia.space at resolver 1.1.1.1:53.
IPv4 address 172.67.194.13 answers for nnia.space at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::6815:14b7 answers for nnia.space at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::ac43:c20d answers for nnia.space at resolver 1.1.1.1:53.
Mail exchanger pegging.liberato.io has preference 0.
Hosting and geo
nnia.space is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.20.183 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for nnia.space is valid, with 42 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | nnia.space |
| Valid from | 14 September 2026 |
| Valid until | 13 December 2026 |
| Days left | 42 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.nnia.space, nnia.space.
Tech stack
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
On-page checks
The homepage fetch did not return a status code.
| Status | none |
|---|
context deadline exceeded
Security
Family DNS for nnia.space 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 | no |
| CSP | no |
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 10 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 5 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 0 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
First checked on 30 October 2026; changes will appear here.
Questions
Is nnia.space 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 nnia.space?
nnia.space is placed in Toronto, Canada.
When does nnia.space expire?
nnia.space expires on 24 May 2027 according to https://rdap.radix.host/rdap/domain/nnia.space.
Who owns nnia.space?
The registry did not return a person or a company for nnia.space. RDAP often redacts the registrant. The registrar on file is Tucows Domains Inc..
Sources
- RDAP source https://rdap.radix.host/rdap/domain/nnia.space at 2026-10-30T15:12:22Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:12:22Z
- TLS source tls:443 at 2026-10-30T15:12:22Z
- HTTP source https://nnia.space/ at 2026-10-30T15:12:22Z
- Tech source not available at 2026-10-30T15:12:22Z
- Geo source db-ip at 2026-10-30T15:12:22Z
- Safety source family DNS and local lists at 2026-10-30T15:12:22Z
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.