zhuafan.tech
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
HTTP 403SafeSSL: 76 days leftUnder 1 year old
45
zhuafan.tech was registered on 18 Oct 2026 via Dynadot Inc and the registry expiry is 18 Oct 2027. WHOIS data came from RDAP at https://rdap.radix.host/rdap/domain/zhuafan.tech.
zhuafan.tech publishes 2 nameservers. DNSSEC is not signed.
zhuafan.tech has 2 IPv4 addresses (188.114.96.3, 188.114.97.3) and 2 IPv6 addresses (2a06:98c1:3120::3, 2a06:98c1:3121::3). The geolocation database places 188.114.96.3 in Toronto, Canada.
The TLS certificate from YE1 is valid and has 76 days left (TLS 1.3).
No safety warning was recorded for zhuafan.tech in the checks that ran.
Domain · RDAP/WHOIS
zhuafan.tech was registered on 18 Oct 2026 via Dynadot Inc. The registry returned 1 status value and 2 nameservers from https://rdap.radix.host/rdap/domain/zhuafan.tech.
| Registered | since 18 Oct 2026 |
|---|---|
| Created | 18 October 2026 |
| Updated | 23 October 2026 |
| Expires | 18 October 2027 |
| Registrar | Dynadot Inc |
| Status | active |
| Nameservers | nova.ns.cloudflare.com, rommy.ns.cloudflare.com |
| DNSSEC | no |
| Source | https://rdap.radix.host/rdap/domain/zhuafan.tech |
Nameserver nova.ns.cloudflare.com is published for zhuafan.tech in the registration record from https://rdap.radix.host/rdap/domain/zhuafan.tech.
Nameserver rommy.ns.cloudflare.com is published for zhuafan.tech in the registration record from https://rdap.radix.host/rdap/domain/zhuafan.tech.
DNS
zhuafan.tech has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 188.114.96.3, 188.114.97.3 |
|---|---|
| AAAA | 2a06:98c1:3120::3, 2a06:98c1:3121::3 |
| NS | nova.ns.cloudflare.com, rommy.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | on |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 188.114.96.3 answers for zhuafan.tech at resolver 1.1.1.1:53.
IPv4 address 188.114.97.3 answers for zhuafan.tech at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3120::3 answers for zhuafan.tech at resolver 1.1.1.1:53.
IPv6 address 2a06:98c1:3121::3 answers for zhuafan.tech at resolver 1.1.1.1:53.
A random label under zhuafan.tech also resolved, which means wildcard DNS is on.
Hosting and geo
zhuafan.tech is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 188.114.96.3 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for zhuafan.tech is valid, with 76 days left and 2 subject alternative names. Source: tls:443.
| Issuer | YE1 |
|---|---|
| Subject | zhuafan.tech |
| Valid from | 18 October 2026 |
| Valid until | 16 January 2027 |
| Days left | 76 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: *.zhuafan.tech, zhuafan.tech.
Tech stack
Tech detection checked the fetched homepage and named 0 products. Source: wappalyzergo.
The fingerprint set matched no product. That is a result, not a skipped check.
On-page checks
The homepage returned HTTP 403 in 24 ms. The target title is 20 characters and the page has 1 H1 heading.
| Status | 403 |
|---|---|
| TTFB | 24 ms |
| Title length | 20 yes |
| Quoted title | "ERROR: ACCESS DENIED" |
| Meta description | none no |
| H1 count | 1 |
| HSTS | no no |
| CSP | no |
| X-Frame-Options | — |
| 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.
Security
Family DNS for zhuafan.tech 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 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 0 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 15 of 15. Points only when the checks ran and came back clean. Unknown is not clean.
Domain age 0 of 5. Five points at one year, two points at 30 days.
Change history
- October 2026: dns aaaa changed from 2a06:98c1:3120::4,2a06:98c1:3121::4 to 2a06:98c1:3120::3,2a06:98c1:3121::3.
Questions
Is zhuafan.tech 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 zhuafan.tech?
zhuafan.tech is placed in Toronto, Canada.
When does zhuafan.tech expire?
zhuafan.tech expires on 18 October 2027 according to https://rdap.radix.host/rdap/domain/zhuafan.tech.
Who owns zhuafan.tech?
The registry did not return a person or a company for zhuafan.tech. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.
Sources
- RDAP source https://rdap.radix.host/rdap/domain/zhuafan.tech at 2026-10-30T15:14:36Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:14:36Z
- TLS source tls:443 at 2026-10-30T15:14:36Z
- HTTP source https://zhuafan.tech/ at 2026-10-30T15:14:36Z
- Tech source wappalyzergo at 2026-10-30T15:14:36Z
- Geo source db-ip at 2026-10-30T15:14:36Z
- Safety source family DNS and local lists at 2026-10-30T15:14:36Z
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.