fanhaolou.com
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
40
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
40
fanhaolou.com was registered on 31 Dec 2016 via Dynadot Inc and the registry expiry is 31 Dec 2027. WHOIS data came from RDAP at https://rdap.verisign.com/com/v1/domain/fanhaolou.com.
fanhaolou.com publishes 2 nameservers. DNSSEC is signed.
fanhaolou.com has 5 IPv4 addresses (104.16.133.220, 104.17.48.205, 104.20.28.74, 104.21.71.249, 172.67.172.155) and 6 IPv6 addresses (2606:4700:10::ac42:9e73, 2606:4700:3030::6815:47f9, 2606:4700:3034::ac43:ac9b, 2606:4700:56::b19:6aa4, 2606:4700:91b0::7785:cc1a, 2a06:98c1:3100::6812:29be). The geolocation database places 104.16.133.220 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 76 days left (TLS 1.3).
fanhaolou.com was registered on 31 Dec 2016 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.verisign.com/com/v1/domain/fanhaolou.com.
| Registered | since 31 Dec 2016 |
|---|---|
| Created | 31 December 2016 |
| Updated | 3 January 2026 |
| Expires | 31 December 2027 |
| Registrar | Dynadot Inc |
| Status | client transfer prohibited |
| Nameservers | dave.ns.cloudflare.com, mona.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.verisign.com/com/v1/domain/fanhaolou.com |
fanhaolou.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 dave.ns.cloudflare.com is published for fanhaolou.com in the registration record from https://rdap.verisign.com/com/v1/domain/fanhaolou.com.
Nameserver mona.ns.cloudflare.com is published for fanhaolou.com in the registration record from https://rdap.verisign.com/com/v1/domain/fanhaolou.com.
fanhaolou.com has 11 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.16.133.220, 104.17.48.205, 104.20.28.74, 104.21.71.249, 172.67.172.155 |
|---|---|
| AAAA | 2606:4700:10::ac42:9e73, 2606:4700:3030::6815:47f9, 2606:4700:3034::ac43:ac9b, 2606:4700:56::b19:6aa4, 2606:4700:91b0::7785:cc1a, 2a06:98c1:3100::6812:29be |
| NS | dave.ns.cloudflare.com, mona.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.16.133.220 answers for fanhaolou.com at resolver 1.1.1.1:53.
IPv4 address 104.17.48.205 answers for fanhaolou.com at resolver 1.1.1.1:53.
IPv4 address 104.20.28.74 answers for fanhaolou.com at resolver 1.1.1.1:53.
IPv4 address 104.21.71.249 answers for fanhaolou.com at resolver 1.1.1.1:53.
IPv4 address 172.67.172.155 answers for fanhaolou.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:10::ac42:9e73 answers for fanhaolou.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3030::6815:47f9 answers for fanhaolou.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3034::ac43:ac9b answers for fanhaolou.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:56::b19:6aa4 answers for fanhaolou.com at resolver 1.1.1.1:53.
IPv6 address 2606:4700:91b0::7785:cc1a answers for fanhaolou.com at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3100::6812:29be answers for fanhaolou.com at resolver 1.1.1.1:53.
A random label under fanhaolou.com also resolved, which means wildcard DNS is on.
fanhaolou.com is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.16.133.220 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
The certificate for fanhaolou.com is valid, with 76 days left and 1 subject alternative name. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | fanhaolou.com |
| Valid from | 17 October 2026 |
| Valid until | 16 January 2027 |
| Days left | 76 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: fanhaolou.com.
Tech detection did not run.
| Checked | no |
|---|---|
| Source | wappalyzergo |
The homepage fetch did not return a status code.
| Status | none |
|---|
Get "https://fanhaolou.com/": context deadline exceeded
Family DNS for fanhaolou.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 fanhaolou.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 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 fanhaolou.com. That resolver covers adult and malware names.
fanhaolou.com is placed in Toronto, Canada.
fanhaolou.com expires on 31 December 2027 according to https://rdap.verisign.com/com/v1/domain/fanhaolou.com.
The registry did not return a person or a company for fanhaolou.com. RDAP often redacts the registrant. The registrar on file is Dynadot 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.