sex8.cc
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
OfflineFamily DNS blockedSSL: 73 days left18 years oldTranco #250606
35
sex8.cc was registered on 11 Jan 2008 via GoDaddy.com, LLC and the registry expiry is 11 Jan 2035. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/sex8.cc.
sex8.cc publishes 4 nameservers. DNSSEC is not signed.
sex8.cc has 2 IPv4 addresses (185.206.180.161, 185.206.180.173) and 2 IPv6 addresses (2a0b:1640:1:1:1007:1:1:1, 2a0b:1640:1:1:1:1:178d:cfae). The geolocation database places 185.206.180.161 in Frankfurt am Main, Germany.
The TLS certificate from ZeroSSL ECC DV SSL CA 2 is valid and has 73 days left (TLS 1.3).
Domain · RDAP/WHOIS
sex8.cc was registered on 11 Jan 2008 via GoDaddy.com, LLC. The registry returned 1 status value and 4 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/sex8.cc.
| Registered | since 11 Jan 2008 |
|---|---|
| Created | 11 January 2008 |
| Updated | 9 June 2025 |
| Expires | 11 January 2035 |
| Registrar | GoDaddy.com, LLC |
| Status | active |
| Nameservers | pns51.cloudns.net, pns52.cloudns.net, pns53.cloudns.net, pns54.cloudns.net |
| DNSSEC | no |
| Source | https://tld-rdap.verisign.com/cc/v1/domain/sex8.cc |
Nameserver pns51.cloudns.net is published for sex8.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/sex8.cc.
Nameserver pns52.cloudns.net is published for sex8.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/sex8.cc.
Nameserver pns53.cloudns.net is published for sex8.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/sex8.cc.
Nameserver pns54.cloudns.net is published for sex8.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/sex8.cc.
DNS
sex8.cc has 4 address records, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 185.206.180.161, 185.206.180.173 |
|---|---|
| AAAA | 2a0b:1640:1:1:1007:1:1:1, 2a0b:1640:1:1:1:1:178d:cfae |
| NS | pns51.cloudns.net, pns52.cloudns.net, pns53.cloudns.net, pns54.cloudns.net |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 185.206.180.161 answers for sex8.cc at resolver 1.1.1.1:53.
IPv4 address 185.206.180.173 answers for sex8.cc at resolver 1.1.1.1:53.
IPv6 address 2a0b:1640:1:1:1007:1:1:1 answers for sex8.cc at resolver 1.1.1.1:53.
IPv6 address 2a0b:1640:1:1:1:1:178d:cfae answers for sex8.cc at resolver 1.1.1.1:53.
Hosting and geo
sex8.cc is placed in Frankfurt am Main, Germany by the local geolocation database (db-ip).
| Address | 185.206.180.161 |
|---|---|
| Country | Germany |
| City | Frankfurt am Main |
| Source | db-ip |
SSL/TLS
The certificate for sex8.cc is valid, with 73 days left and 3 subject alternative names. Source: tls:443.
| Issuer | ZeroSSL ECC DV SSL CA 2 |
|---|---|
| Subject | sex8.cc |
| Valid from | 14 October 2026 |
| Valid until | 12 January 2027 |
| Days left | 73 |
| SAN count | 3 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.bak.sex8.cc, *.sex8.cc, sex8.cc.
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://www.sex8.cc/": read tcp 10.0.0.3:60724->20.205.36.161:443: read: connection reset by peer
Security
Family DNS for sex8.cc is blocked, and URLhaus is clear. Source: family DNS and local lists.
| Family DNS | blocked |
|---|---|
| URLhaus | clear |
| UT1 | — |
| Web Risk | not run |
| Source | family DNS and local lists |
| HSTS | no |
| CSP | no |
Cloudflare family DNS returned a block for sex8.cc. That resolver covers adult and malware names.
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 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 0 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 Frankfurt am Main.
- October 2026: geo country changed from empty to Germany.
Questions
Is sex8.cc safe?
Cloudflare family DNS returned a block for sex8.cc. That resolver covers adult and malware names.
Who hosts sex8.cc?
sex8.cc is placed in Frankfurt am Main, Germany.
When does sex8.cc expire?
sex8.cc expires on 11 January 2035 according to https://tld-rdap.verisign.com/cc/v1/domain/sex8.cc.
Who owns sex8.cc?
The registry did not return a person or a company for sex8.cc. RDAP often redacts the registrant. The registrar on file is GoDaddy.com, LLC.
Sources
- RDAP source https://tld-rdap.verisign.com/cc/v1/domain/sex8.cc at 2026-10-30T13:34:59Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:34:59Z
- TLS source tls:443 at 2026-10-30T13:34:59Z
- HTTP source https://sex8.cc/ at 2026-10-30T13:34:59Z
- Tech source not available at 2026-10-30T13:34:59Z
- Geo source db-ip at 2026-10-30T13:34:59Z
- Safety source family DNS and local lists at 2026-10-30T13:34:59Z
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.