sexyforums.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
sexyforums.com was registered on 24 Sep 2022 via NameCheap, Inc. and the registry expiry is 24 Sep 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/sexyforums.com.
sexyforums.com publishes 2 nameservers. DNSSEC is not signed.
sexyforums.com has 2 IPv4 addresses (104.21.40.199, 172.67.138.143) and 2 IPv6 addresses (2606:4700:3030::6815:28c7, 2606:4700:3030::ac43:8a8f). The geolocation database places 104.21.40.199 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 67 days left (TLS 1.3).
Tech detection named Cloudflare and HTTP/3. The fingerprints ran on the homepage that was already downloaded.
sexyforums.com was registered on 24 Sep 2022 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/sexyforums.com.
| Registered | since 24 Sep 2022 |
|---|---|
| Created | 24 September 2022 |
| Updated | 25 August 2026 |
| Expires | 24 September 2027 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | burt.ns.cloudflare.com, elle.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/sexyforums.com |
sexyforums.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 burt.ns.cloudflare.com is published for sexyforums.com in the registration record from https://rdap.verisign.com/com/v1/domain/sexyforums.com.
Nameserver elle.ns.cloudflare.com is published for sexyforums.com in the registration record from https://rdap.verisign.com/com/v1/domain/sexyforums.com.
sexyforums.com has 4 address records, 3 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.40.199, 172.67.138.143 |
|---|---|
| AAAA | 2606:4700:3030::6815:28c7, 2606:4700:3030::ac43:8a8f |
| NS | burt.ns.cloudflare.com, elle.ns.cloudflare.com |
| MX | route2.mx.cloudflare.net (27), route1.mx.cloudflare.net (29), route3.mx.cloudflare.net (71) |
| SPF | present |
| DMARC | present |
| CAA | issue 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 |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at sexyforums.com is "v=spf1 include:_spf.mx.cloudflare.net ~all".
The DMARC text record at _dmarc.sexyforums.com is "v=DMARC1; p=none;".
IPv4 address 104.21.40.199 answers for sexyforums.com at resolver 1.1.1.1:53.
IPv4 address 172.67.138.143 answers for sexyforums.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3030::6815:28c7 answers for sexyforums.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3030::ac43:8a8f answers for sexyforums.com at resolver 1.1.1.1:53.
Mail exchanger route2.mx.cloudflare.net has preference 27.
Mail exchanger route1.mx.cloudflare.net has preference 29.
Mail exchanger route3.mx.cloudflare.net has preference 71.
sexyforums.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.40.199 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for sexyforums.com is valid, with 67 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | sexyforums.com |
| Valid from | 10 October 2026 |
| Valid until | 8 January 2027 |
| Days left | 67 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: mta-sts.sexyforums.com, sexyforums.com.
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
Cloudflare is filed under CDN.
HTTP/3 is filed under Miscellaneous.
The homepage returned HTTP 403 in 7 ms. The target title is 0 characters and the page has 0 H1 headings.
| Status | 403 |
|---|---|
| TTFB | 7 ms |
| Title length | 0 no |
| Quoted title | none |
| Meta description | none no |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | — |
| Language | — |
| Links | 0 |
| Images | 0 |
| Favicon | no |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for sexyforums.com 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 sexyforums.com. 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.
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 15 of 20. SPF, DMARC, CAA, and DNSSEC are five points each.
Security headers 5 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.
First checked on 30 October 2026; changes will appear here.
Cloudflare family DNS returned a block for sexyforums.com. That resolver covers adult and malware names.
sexyforums.com is placed in Toronto, Canada.
sexyforums.com expires on 24 September 2027 according to https://rdap.verisign.com/com/v1/domain/sexyforums.com.
The registry did not return a person or a company for sexyforums.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
No other indexable reports share this TLD, host, or registrar yet.
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.
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.