zi0.cc
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 18 days left4 years old
70
zi0.cc was registered on 4 Oct 2022 via Dynadot Inc and the registry expiry is 4 Oct 2027. WHOIS data came from RDAP at https://tld-rdap.verisign.com/cc/v1/domain/zi0.cc.
zi0.cc publishes 4 nameservers. DNSSEC is not signed.
zi0.cc has 1 IPv4 address (5.34.218.89). The geolocation database places 5.34.218.89 in Los Angeles, United States.
The TLS certificate from YR2 is valid and has 18 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named HSTS and Vercel. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for zi0.cc in the checks that ran.
Domain · RDAP/WHOIS
zi0.cc was registered on 4 Oct 2022 via Dynadot Inc. The registry returned 1 status value and 4 nameservers from https://tld-rdap.verisign.com/cc/v1/domain/zi0.cc.
| Registered | since 4 Oct 2022 |
|---|---|
| Created | 4 October 2022 |
| Updated | 12 June 2026 |
| Expires | 4 October 2027 |
| Registrar | Dynadot Inc |
| Status | client transfer prohibited |
| Nameservers | ns1.huaweicloud-dns.cn, ns1.huaweicloud-dns.com, ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org |
| DNSSEC | no |
| Source | https://tld-rdap.verisign.com/cc/v1/domain/zi0.cc |
zi0.cc 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 ns1.huaweicloud-dns.cn is published for zi0.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/zi0.cc.
Nameserver ns1.huaweicloud-dns.com is published for zi0.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/zi0.cc.
Nameserver ns1.huaweicloud-dns.net is published for zi0.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/zi0.cc.
Nameserver ns1.huaweicloud-dns.org is published for zi0.cc in the registration record from https://tld-rdap.verisign.com/cc/v1/domain/zi0.cc.
DNS
zi0.cc has 1 address record, 0 mail exchangers and 4 nameservers, measured at 1.1.1.1:53.
| A | 5.34.218.89 |
|---|---|
| AAAA | — |
| NS | ns1.huaweicloud-dns.cn, ns1.huaweicloud-dns.com, ns1.huaweicloud-dns.net, ns1.huaweicloud-dns.org |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | — |
| Wildcard | off |
| DNSSEC | not signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 5.34.218.89 answers for zi0.cc at resolver 1.1.1.1:53.
Hosting and geo
zi0.cc is placed in Los Angeles, United States by the local geolocation database (db-ip).
| Address | 5.34.218.89 |
|---|---|
| Country | United States |
| City | Los Angeles |
| Source | db-ip |
SSL/TLS
The certificate for zi0.cc is valid, with 18 days left and 1 subject alternative name. Source: tls:443.
| Issuer | YR2 |
|---|---|
| Subject | zi0.cc |
| Valid from | 20 August 2026 |
| Valid until | 18 November 2026 |
| Days left | 18 |
| SAN count | 1 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: zi0.cc.
Tech stack
Tech detection checked the fetched homepage and named 2 products. Source: wappalyzergo.
- HSTS · Security
- Vercel · PaaS
HSTS is filed under Security.
Vercel is filed under PaaS.
On-page checks
The homepage returned HTTP 200 in 164 ms. The target title is 9 characters and the page has 1 H1 heading.
| Status | 200 |
|---|---|
| TTFB | 164 ms |
| Title length | 9 yes |
| Quoted title | "梓澪の妙妙屋导航页" |
| Meta description | "梓澪の妙妙屋防失联导航页" yes |
| H1 count | 1 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | — |
| Canonical | https://galfor.you/ |
| Language | zh-CN |
| Links | 7 |
| 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.
Security
Family DNS for zi0.cc 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 | yes |
| 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 0 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
- October 2026: geo city changed from empty to Los Angeles.
- October 2026: geo country changed from empty to United States.
Questions
Is zi0.cc 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 zi0.cc?
zi0.cc is placed in Los Angeles, United States.
When does zi0.cc expire?
zi0.cc expires on 4 October 2027 according to https://tld-rdap.verisign.com/cc/v1/domain/zi0.cc.
Who owns zi0.cc?
The registry did not return a person or a company for zi0.cc. RDAP often redacts the registrant. The registrar on file is Dynadot Inc.
Sources
- RDAP source https://tld-rdap.verisign.com/cc/v1/domain/zi0.cc at 2026-10-30T13:36:20Z
- DNS source 1.1.1.1:53 at 2026-10-30T13:36:20Z
- TLS source tls:443 at 2026-10-30T13:36:20Z
- HTTP source https://zi0.cc/ at 2026-10-30T13:36:20Z
- Tech source wappalyzergo at 2026-10-30T13:36:20Z
- Geo source db-ip at 2026-10-30T13:36:20Z
- Safety source family DNS and local lists at 2026-10-30T13:36:20Z
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.