hsex.men
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
55
hsex.men was registered on 24 Jun 2017 via NameCheap, Inc. and the registry expiry is 24 Jun 2031. WHOIS data came from RDAP at https://rdap.nic.men/domain/hsex.men.
hsex.men publishes 2 nameservers. DNSSEC is signed.
hsex.men has 2 IPv4 addresses (104.21.71.68, 172.67.143.186) and 2 IPv6 addresses (2606:4700:3031::6815:4744, 2606:4700:3031::ac43:8fba). The geolocation database places 104.21.71.68 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 37 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, Cloudflare Browser Insights, Google Analytics, HTTP/3, PHP and jQuery. The fingerprints ran on the homepage that was already downloaded.
hsex.men was registered on 24 Jun 2017 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.nic.men/domain/hsex.men.
| Registered | since 24 Jun 2017 |
|---|---|
| Created | 24 June 2017 |
| Updated | 8 September 2026 |
| Expires | 24 June 2031 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | ara.ns.cloudflare.com, fred.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.nic.men/domain/hsex.men |
hsex.men 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 ara.ns.cloudflare.com is published for hsex.men in the registration record from https://rdap.nic.men/domain/hsex.men.
Nameserver fred.ns.cloudflare.com is published for hsex.men in the registration record from https://rdap.nic.men/domain/hsex.men.
hsex.men has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.71.68, 172.67.143.186 |
|---|---|
| AAAA | 2606:4700:3031::6815:4744, 2606:4700:3031::ac43:8fba |
| NS | ara.ns.cloudflare.com, fred.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.71.68 answers for hsex.men at resolver 1.1.1.1:53.
IPv4 address 172.67.143.186 answers for hsex.men at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3031::6815:4744 answers for hsex.men at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3031::ac43:8fba answers for hsex.men at resolver 1.1.1.1:53.
hsex.men is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.71.68 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for hsex.men is valid, with 37 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | hsex.men |
| Valid from | 9 September 2026 |
| Valid until | 8 December 2026 |
| Days left | 37 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.hsex.men, hsex.men.
Tech detection checked the fetched homepage and named 7 products. Source: wappalyzergo.
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
PHP is filed under Programming languages.
jQuery is filed under JavaScript libraries.
The homepage returned HTTP 200 in 6636 ms. The target title is 6 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 6636 ms |
| Title length | 6 yes |
| Quoted title | "好色™ Tv" |
| Meta description | "好色™ Tv,汇聚91porn原创自拍、国产自拍、伦理大片、热门成人视频、国产精品大片。海量高清内容每日更新,免费高清在线观看,发现你喜欢的精彩视频,就在好色™ Tv!" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | index, follow, nosnippet |
| Canonical | — |
| Language | zh-CN |
| Links | 187 |
| Images | 1 |
| Favicon | yes |
The quoted title and meta description are measurements of the other site. They are not this page's title or description.
Family DNS for hsex.men 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 hsex.men. 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 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.
First checked on 30 October 2026; changes will appear here.
Cloudflare family DNS returned a block for hsex.men. That resolver covers adult and malware names.
hsex.men is placed in Toronto, Canada.
hsex.men expires on 24 June 2031 according to https://rdap.nic.men/domain/hsex.men.
The registry did not return a person or a company for hsex.men. 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.