hanman18.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 80 days left4 years oldTranco #186652
75
hanman18.com was registered on 26 Nov 2021 via NameCheap, Inc. and the registry expiry is 26 Nov 2026. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/hanman18.com.
hanman18.com publishes 2 nameservers. DNSSEC is not signed.
hanman18.com has 2 IPv4 addresses (104.21.25.109, 172.67.134.8) and 2 IPv6 addresses (2606:4700:3030::ac43:8608, 2606:4700:3036::6815:196d). The geolocation database places 104.21.25.109 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 80 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, BootstrapCDN, Cloudflare, CodeIgniter, FancyBox, Google Analytics, HTTP/3, OWL Carousel, PHP, TrafficStars, cdnjs, jQuery, jQuery CDN, jQuery UI and jsDelivr. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for hanman18.com in the checks that ran.
Domain · RDAP/WHOIS
hanman18.com was registered on 26 Nov 2021 via NameCheap, Inc.. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/hanman18.com.
| Registered | since 26 Nov 2021 |
|---|---|
| Created | 26 November 2021 |
| Updated | 9 November 2025 |
| Expires | 26 November 2026 |
| Registrar | NameCheap, Inc. |
| Status | client transfer prohibited |
| Nameservers | dion.ns.cloudflare.com, tara.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.verisign.com/com/v1/domain/hanman18.com |
hanman18.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 dion.ns.cloudflare.com is published for hanman18.com in the registration record from https://rdap.verisign.com/com/v1/domain/hanman18.com.
Nameserver tara.ns.cloudflare.com is published for hanman18.com in the registration record from https://rdap.verisign.com/com/v1/domain/hanman18.com.
DNS
hanman18.com has 4 address records, 5 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.25.109, 172.67.134.8 |
|---|---|
| AAAA | 2606:4700:3030::ac43:8608, 2606:4700:3036::6815:196d |
| NS | dion.ns.cloudflare.com, tara.ns.cloudflare.com |
| MX | eforward1.registrar-servers.com (10), eforward2.registrar-servers.com (10), eforward3.registrar-servers.com (10), eforward4.registrar-servers.com (15), eforward5.registrar-servers.com (20) |
| SPF | present |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
The SPF text record at hanman18.com is "v=spf1 include:spf.efwd.registrar-servers.com ~all".
IPv4 address 104.21.25.109 answers for hanman18.com at resolver 1.1.1.1:53.
IPv4 address 172.67.134.8 answers for hanman18.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3030::ac43:8608 answers for hanman18.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3036::6815:196d answers for hanman18.com at resolver 1.1.1.1:53.
Mail exchanger eforward1.registrar-servers.com has preference 10.
Mail exchanger eforward2.registrar-servers.com has preference 10.
Mail exchanger eforward3.registrar-servers.com has preference 10.
Mail exchanger eforward4.registrar-servers.com has preference 15.
Mail exchanger eforward5.registrar-servers.com has preference 20.
Hosting and geo
hanman18.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.25.109 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for hanman18.com is valid, with 80 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | hanman18.com |
| Valid from | 22 October 2026 |
| Valid until | 20 January 2027 |
| Days left | 80 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.hanman18.com, hanman18.com.
Tech stack
Tech detection checked the fetched homepage and named 15 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- BootstrapCDN · CDN
- Cloudflare · CDN
- CodeIgniter · Web frameworks
- FancyBox · JavaScript libraries
- Google Analytics · Analytics
- HTTP/3 · Miscellaneous
- OWL Carousel · JavaScript libraries
- PHP · Programming languages
- TrafficStars · Advertising
- cdnjs · CDN
- jQuery · JavaScript libraries
- jQuery CDN · CDN
- jQuery UI · JavaScript libraries
- jsDelivr · CDN
Bootstrap is filed under UI frameworks.
BootstrapCDN is filed under CDN.
Cloudflare is filed under CDN.
CodeIgniter is filed under Web frameworks.
FancyBox is filed under JavaScript libraries.
Google Analytics is filed under Analytics.
HTTP/3 is filed under Miscellaneous.
OWL Carousel is filed under JavaScript libraries.
PHP is filed under Programming languages.
TrafficStars is filed under Advertising.
cdnjs is filed under CDN.
jQuery is filed under JavaScript libraries.
jQuery CDN is filed under CDN.
jQuery UI is filed under JavaScript libraries.
jsDelivr is filed under CDN.
On-page checks
The homepage returned HTTP 200 in 141 ms. The target title is 19 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 141 ms |
| Title length | 19 yes |
| Quoted title | "Hanman18.com - 禁漫天堂" |
| Meta description | "免費成人Hanman漫線上看" yes |
| H1 count | 0 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | SAMEORIGIN |
| Robots meta | — |
| Canonical | https://hanman18.com/ |
| Language | en |
| Links | 458 |
| Images | 102 |
| Favicon | yes |
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 hanman18.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 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 5 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
First checked on 30 October 2026; changes will appear here.
Questions
Is hanman18.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 hanman18.com?
hanman18.com is placed in Toronto, Canada.
When does hanman18.com expire?
hanman18.com expires on 26 November 2026 according to https://rdap.verisign.com/com/v1/domain/hanman18.com.
Who owns hanman18.com?
The registry did not return a person or a company for hanman18.com. RDAP often redacts the registrant. The registrar on file is NameCheap, Inc..
Sources
- RDAP source https://rdap.verisign.com/com/v1/domain/hanman18.com at 2026-10-30T13:57:00Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:57:00Z
- TLS source tls:443 at 2026-10-30T13:57:00Z
- HTTP source https://hanman18.com/ at 2026-10-30T13:57:00Z
- Tech source wappalyzergo at 2026-10-30T13:57:00Z
- Geo source db-ip at 2026-10-30T13:57:00Z
- Safety source family DNS and local lists at 2026-10-30T13:57:00Z
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.