sexgames.cc

Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .

Online · 200Family DNS blockedSSL: 36 days left20 years oldTranco #434465

One re-check per domain each UTC day.

55

sexgames.cc was registered on 18 Oct 2006 via GoDaddy.com, LLC and the registry expiry is 18 Oct 2028. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/sexgames.cc.

sexgames.cc publishes 2 nameservers. DNSSEC is not signed.

sexgames.cc has 3 IPv4 addresses (104.26.2.207, 104.26.3.207, 172.67.72.145) and 3 IPv6 addresses (2606:4700:20::681a:2cf, 2606:4700:20::681a:3cf, 2606:4700:20::ac43:4891). The geolocation database places 104.26.2.207 in Toronto, Canada.

The TLS certificate from WE1 is valid and has 36 days left (TLS 1.3). The homepage answered HTTP 200.

Tech detection named Cloudflare, Cloudflare Browser Insights, HTTP/3 and ShareThis. The fingerprints ran on the homepage that was already downloaded.

Domain · RDAP/WHOIS

sexgames.cc was registered on 18 Oct 2006 via GoDaddy.com, LLC. The registry returned 4 status values and 2 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/sexgames.cc.

Registeredsince 18 Oct 2006
Created18 October 2006
Updated8 February 2026
Expires18 October 2028
RegistrarGoDaddy.com, LLC
Statusclient delete prohibited, client renew prohibited, client transfer prohibited, client update prohibited
Nameserversduke.ns.cloudflare.com, rosemary.ns.cloudflare.com
DNSSECno
Sourcehttps://tld-rdap.verisign.com/cc/v1/domain/sexgames.cc

sexgames.cc 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.

sexgames.cc carries the status "client renew prohibited". The registrar has asked the registry to refuse a renewal. The expiry date still stands until a different status is set.

sexgames.cc 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.

sexgames.cc 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 duke.ns.cloudflare.com is published for sexgames.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/sexgames.cc.

Nameserver rosemary.ns.cloudflare.com is published for sexgames.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/sexgames.cc.

DNS

sexgames.cc has 6 address records, 1 mail exchanger and 2 nameservers, measured at 1.1.1.1:53.

A104.26.2.207, 104.26.3.207, 172.67.72.145
AAAA2606:4700:20::681a:2cf, 2606:4700:20::681a:3cf, 2606:4700:20::ac43:4891
NSduke.ns.cloudflare.com, rosemary.ns.cloudflare.com
MXforwarders.webair.com (10)
SPFabsent
DMARCabsent
CAAissue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com
Wildcardoff
DNSSECnot signed
Resolver1.1.1.1:53

IPv4 address 104.26.2.207 answers for sexgames.cc at resolver 1.1.1.1:53.

IPv4 address 104.26.3.207 answers for sexgames.cc at resolver 1.1.1.1:53.

IPv4 address 172.67.72.145 answers for sexgames.cc at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::681a:2cf answers for sexgames.cc at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::681a:3cf answers for sexgames.cc at resolver 1.1.1.1:53.

IPv6 address 2606:4700:20::ac43:4891 answers for sexgames.cc at resolver 1.1.1.1:53.

Mail exchanger forwarders.webair.com has preference 10.

Hosting and geo

sexgames.cc is placed in Toronto, Canada by the local geolocation database (db-ip).

Address104.26.2.207
CountryCanada
CityToronto
Sourcedb-ip

IP geolocation by DB-IP

SSL/TLS

The certificate for sexgames.cc is valid, with 36 days left and 2 subject alternative names. Source: tls:443.

IssuerWE1
Subjectsexgames.cc
Valid from7 September 2026
Valid until6 December 2026
Days left36
SAN count2
ProtocolTLS 1.3
Sourcetls:443

Subject alternative names: *.sexgames.cc, sexgames.cc.

Tech stack

Tech detection checked the fetched homepage and named 4 products. Source: wappalyzergo.

  • Cloudflare · CDN
  • Cloudflare Browser Insights · Analytics, RUM
  • HTTP/3 · Miscellaneous
  • ShareThis · Widgets

Cloudflare is filed under CDN.

Cloudflare Browser Insights is filed under Analytics, RUM.

HTTP/3 is filed under Miscellaneous.

ShareThis is filed under Widgets.

On-page checks

The homepage returned HTTP 200 in 102 ms. The target title is 9 characters and the page has 1 H1 heading.

Status200
TTFB102 ms
Title length9 yes
Quoted title"Sex Games"
Meta description"Welcome to my sex games site. Here you will find the best free sex games for your pleasure. I use to update often, so don't forget to return soon. Enjoy! :-)" yes
H1 count1
HSTSno no
CSPno
X-Frame-Options—
Robots metaall
Canonicalhttps://www.sexgames.cc/
Language—
Links321
Images74
Faviconyes

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 sexgames.cc is blocked, and URLhaus is clear. Source: family DNS and local lists.

Family DNSblocked
URLhausclear
UT1—
Web Risknot run
Sourcefamily DNS and local lists
HSTSno
CSPno

Cloudflare family DNS returned a block for sexgames.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 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 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 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

First checked on 30 October 2026; changes will appear here.

Questions

Is sexgames.cc safe?

Cloudflare family DNS returned a block for sexgames.cc. That resolver covers adult and malware names.

Who hosts sexgames.cc?

sexgames.cc is placed in Toronto, Canada.

When does sexgames.cc expire?

sexgames.cc expires on 18 October 2028 according to https://tld-rdap.verisign.com/cc/v1/domain/sexgames.cc.

Who owns sexgames.cc?

The registry did not return a person or a company for sexgames.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/sexgames.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://sexgames.cc/ at 2026-10-30T13:34:59Z
  • Tech source wappalyzergo 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

Methodology

Related reports

No other indexable reports share this TLD, host, or registrar yet.

.cc GoDaddy.com, LLC

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.

Removal policy

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.