spank520.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineSafeSSL: -1539 days left4 years old
30
spank520.com was registered on 7 Sep 2022 via Gname.com Pte. Ltd. and the registry expiry is 7 Sep 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/spank520.com.
spank520.com publishes 1 nameserver. DNSSEC is not signed.
spank520.com has 2 IPv4 addresses (207.56.119.16, 38.6.115.1). The geolocation database places 207.56.119.16 in Toronto, Canada.
The TLS certificate from Default Company Ltd is not valid (TLS 1.2).
No safety warning was recorded for spank520.com in the checks that ran.
Domain · RDAP/WHOIS
spank520.com was registered on 7 Sep 2022 via Gname.com Pte. Ltd.. The registry returned 1 status value and 3 nameservers from https://rdap.verisign.com/com/v1/domain/spank520.com.
| Registered | since 7 Sep 2022 |
|---|---|
| Created | 7 September 2022 |
| Updated | 3 September 2026 |
| Expires | 7 September 2027 |
| Registrar | Gname.com Pte. Ltd. |
| Status | client transfer prohibited |
| Nameservers | ns1.peacedns.com, ns2.peacedns.com, ns3.peacedns.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/spank520.com |
spank520.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 ns1.peacedns.com is published for spank520.com in the registration record from https://rdap.verisign.com/com/v1/domain/spank520.com.
Nameserver ns2.peacedns.com is published for spank520.com in the registration record from https://rdap.verisign.com/com/v1/domain/spank520.com.
Nameserver ns3.peacedns.com is published for spank520.com in the registration record from https://rdap.verisign.com/com/v1/domain/spank520.com.
DNS
spank520.com has 2 address records, 1 mail exchanger and 1 nameserver, measured at 1.1.1.1:53.
| A | 207.56.119.16, 38.6.115.1 |
|---|---|
| AAAA | — |
| NS | planthree.seihappy.com |
| MX | planthree.seihappy.com (1) |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 207.56.119.16 answers for spank520.com at resolver 1.1.1.1:53.
IPv4 address 38.6.115.1 answers for spank520.com at resolver 1.1.1.1:53.
Mail exchanger planthree.seihappy.com has preference 1.
A random label under spank520.com also resolved, which means wildcard DNS is on.
Hosting and geo
spank520.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 207.56.119.16 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for spank520.com is not valid, with -1539 days left and 0 subject alternative names. Source: tls:443.
| Issuer | Default Company Ltd |
|---|---|
| Subject | — |
| Valid from | 13 August 2021 |
| Valid until | 13 August 2022 |
| Days left | -1539 |
| SAN count | 0 |
| Protocol | TLS 1.2 |
| Source | tls:443 |
Validation result: certificate did not validate
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 |
|---|
Get "https://spank520.com/": tls: failed to verify certificate: x509: certificate has expired or is not yet valid: current time 2026-10-30T14:14:49Z is after 2022-08-13T15:26:37Z
Security
Family DNS for spank520.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 | 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 0 of 20. A valid certificate, with extra points when it has at least 14 days left.
DNS hygiene 0 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
- October 2026: geo city changed from empty to Toronto.
- October 2026: geo country changed from empty to Canada.
Questions
Is spank520.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 spank520.com?
spank520.com is placed in Toronto, Canada.
When does spank520.com expire?
spank520.com expires on 7 September 2027 according to https://rdap.verisign.com/com/v1/domain/spank520.com.
Who owns spank520.com?
The registry did not return a person or a company for spank520.com. RDAP often redacts the registrant. The registrar on file is Gname.com Pte. Ltd..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/spank520.com at 2026-10-30T14:14:49Z
- DNS source 1.1.1.1:53 at 2026-10-30T14:14:49Z
- TLS source tls:443 at 2026-10-30T14:14:49Z
- HTTP source https://spank520.com/ at 2026-10-30T14:14:49Z
- Tech source not available at 2026-10-30T14:14:49Z
- Geo source db-ip at 2026-10-30T14:14:49Z
- Safety source family DNS and local lists at 2026-10-30T14:14:49Z
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.