lzacg.one
Domain report: WHOIS, DNS, hosting, SSL and safety. Checked .
Online · 200SafeSSL: 70 days left4 years old
80
lzacg.one was registered on 3 May 2022 via NameSilo, LLC and the registry expiry is 3 May 2028. WHOIS data came from RDAP at https://rdap.nic.one/domain/lzacg.one.
lzacg.one publishes 2 nameservers. DNSSEC is signed.
lzacg.one has 2 IPv4 addresses (104.21.76.130, 172.67.195.123) and 2 IPv6 addresses (2606:4700:3036::6815:4c82, 2606:4700:3037::ac43:c37b). The geolocation database places 104.21.76.130 in Toronto, Canada.
The TLS certificate from WE1 is valid and has 70 days left (TLS 1.3). The homepage answered HTTP 200.
Tech detection named Bootstrap, Cloudflare, Cloudflare Browser Insights, HSTS, HTTP/3, MySQL, PHP, Redis, Redis Object Cache, Super Page Cache, WordPress and jQuery. The fingerprints ran on the homepage that was already downloaded.
No safety warning was recorded for lzacg.one in the checks that ran.
Domain · RDAP/WHOIS
lzacg.one was registered on 3 May 2022 via NameSilo, LLC. The registry returned 1 status value and 2 nameservers from https://rdap.nic.one/domain/lzacg.one.
| Registered | since 3 May 2022 |
|---|---|
| Created | 3 May 2022 |
| Updated | 15 October 2025 |
| Expires | 3 May 2028 |
| Registrar | NameSilo, LLC |
| Status | client transfer prohibited |
| Nameservers | salvador.ns.cloudflare.com, rayne.ns.cloudflare.com |
| DNSSEC | yes |
| Source | https://rdap.nic.one/domain/lzacg.one |
lzacg.one 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 salvador.ns.cloudflare.com is published for lzacg.one in the registration record from https://rdap.nic.one/domain/lzacg.one.
Nameserver rayne.ns.cloudflare.com is published for lzacg.one in the registration record from https://rdap.nic.one/domain/lzacg.one.
DNS
lzacg.one has 4 address records, 0 mail exchangers and 2 nameservers, measured at 1.1.1.1:53.
| A | 104.21.76.130, 172.67.195.123 |
|---|---|
| AAAA | 2606:4700:3036::6815:4c82, 2606:4700:3037::ac43:c37b |
| NS | rayne.ns.cloudflare.com, salvador.ns.cloudflare.com |
| MX | — |
| SPF | absent |
| DMARC | absent |
| CAA | issue comodoca.com, issue digicert.com; cansignhttpexchanges=yes, issue letsencrypt.org, issue pki.goog; cansignhttpexchanges=yes, issue ssl.com, issuewild comodoca.com, issuewild digicert.com; cansignhttpexchanges=yes, issuewild letsencrypt.org, issuewild pki.goog; cansignhttpexchanges=yes, issuewild ssl.com |
| Wildcard | off |
| DNSSEC | signed |
| Resolver | 1.1.1.1:53 |
IPv4 address 104.21.76.130 answers for lzacg.one at resolver 1.1.1.1:53.
IPv4 address 172.67.195.123 answers for lzacg.one at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3036::6815:4c82 answers for lzacg.one at resolver 1.1.1.1:53.
IPv6 address 2606:4700:3037::ac43:c37b answers for lzacg.one at resolver 1.1.1.1:53.
Hosting and geo
lzacg.one is placed in Toronto, Canada by the local geolocation database (db-ip).
| Address | 104.21.76.130 |
|---|---|
| Country | Canada |
| City | Toronto |
| Source | db-ip |
SSL/TLS
The certificate for lzacg.one is valid, with 70 days left and 2 subject alternative names. Source: tls:443.
| Issuer | WE1 |
|---|---|
| Subject | lzacg.one |
| Valid from | 11 October 2026 |
| Valid until | 9 January 2027 |
| Days left | 70 |
| SAN count | 2 |
| Protocol | TLS 1.3 |
| Source | tls:443 |
Subject alternative names: auth.worker.lzacg.one, lzacg.one.
Tech stack
Tech detection checked the fetched homepage and named 12 products. Source: wappalyzergo.
- Bootstrap · UI frameworks
- Cloudflare · CDN
- Cloudflare Browser Insights · Analytics, RUM
- HSTS · Security
- HTTP/3 · Miscellaneous
- MySQL · Databases
- PHP · Programming languages
- Redis · Databases
- Redis Object Cache · Caching
- Super Page Cache · Caching, WordPress plugins
- WordPress · CMS, Blogs
- jQuery · JavaScript libraries
Bootstrap is filed under UI frameworks.
Cloudflare is filed under CDN.
Cloudflare Browser Insights is filed under Analytics, RUM.
HSTS is filed under Security.
HTTP/3 is filed under Miscellaneous.
MySQL is filed under Databases.
PHP is filed under Programming languages.
Redis is filed under Databases.
Redis Object Cache is filed under Caching.
Super Page Cache is filed under Caching, WordPress plugins.
WordPress is filed under CMS, Blogs.
jQuery is filed under JavaScript libraries.
On-page checks
The homepage returned HTTP 200 in 37 ms. The target title is 5 characters and the page has 0 H1 headings.
| Status | 200 |
|---|---|
| TTFB | 37 ms |
| Title length | 5 yes |
| Quoted title | "量子ACG" |
| Meta description | "量子ACG是一个以游戏为主，进而推动日语学习的网站" yes |
| H1 count | 0 |
| HSTS | yes yes |
| CSP | no |
| X-Frame-Options | — |
| Robots meta | max-image-preview:large |
| Canonical | https://lzacg.cc/ |
| Language | zh-Hans |
| Links | 1049 |
| Images | 70 |
| 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 lzacg.one 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 10 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: rdap created changed from empty to 2022-05-03T14:51:25Z.
- October 2026: rdap dnssec changed from empty to yes.
- October 2026: rdap expires changed from empty to 2028-05-03T14:51:25Z.
- October 2026: rdap nameservers changed from empty to rayne.ns.cloudflare.com,salvador.ns.cloudflare.com.
- October 2026: rdap registered changed from unknown to yes.
- October 2026: rdap registrar changed from empty to NameSilo, LLC.
- October 2026: rdap statuses changed from empty to client transfer prohibited.
- October 2026: rdap updated changed from empty to 2025-10-15T18:24:19Z.
Questions
Is lzacg.one 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 lzacg.one?
lzacg.one is placed in Toronto, Canada.
When does lzacg.one expire?
lzacg.one expires on 3 May 2028 according to https://rdap.nic.one/domain/lzacg.one.
Who owns lzacg.one?
The registry did not return a person or a company for lzacg.one. RDAP often redacts the registrant. The registrar on file is NameSilo, LLC.
Sources
- RDAP source https://rdap.nic.one/domain/lzacg.one at 2026-10-30T15:00:32Z
- DNS source 1.1.1.1:53 at 2026-10-30T15:00:32Z
- TLS source tls:443 at 2026-10-30T15:00:32Z
- HTTP source https://lzacg.one/ at 2026-10-30T15:00:32Z
- Tech source wappalyzergo at 2026-10-30T15:00:32Z
- Geo source db-ip at 2026-10-30T15:00:32Z
- Safety source family DNS and local lists at 2026-10-30T15:00:32Z
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.