Domain

g.cn

Aggregated from public BGP, CT logs, our scan layer, honeypots and global probes.

DNS Check HTTP Check Run Full Scan .cn TLD

Run a live full scan of g.cn

On-demand: ports, banners, TLS, tech-stack, subdomains and origin/IP-leak detection. Results are shared publicly for everyone to link to.

Deep-scan now

Hosting IPs

A/AAAA targets

Subdomains

CT + scan + body

Record Types

seen in DNS

Observed Certs

108

in our scans

DNS Records

142.251.168.94, 142.251.39.131, 172.217.17.195, 172.217.20.67, 216.58.198.35, 216.58.198.99

AAAA

2a00:1450:4001:c17::5e, 2a00:1450:4002:400::2003, 2a00:1450:400c:c0b::5e, 2a00:1450:400e:804::2003, 2a00:1450:400e:814::2003, 2a00:1450:4017:81e::2003, 2a00:1450:4025:401::5e

0 smtp.google.com

ns1.google.com, ns2.google.com, ns3.google.com, ns4.google.com

TXT

v=spf1 -all

CNAME

—

CAA

0 issue "pki.goog"

WHOIS / Registration

Registration data planned

Registrar, creation/expiry dates and domain status via RDAP. Rolling out gradually — bulk WHOIS is rate-limited, so we resolve on a prioritized cadence.

Subdomains

Every subdomain we know about — harvested from CT-log SANs, scan-observed certs and HTML body references — paired with its current A/AAAA target.

Subdomain	Resolves to	Last seen
g.cn	216.58.198.35 2a00:1450:4001:c17::5e 2a00:1450:400c:c0b::5e 2a00:1450:400e:804::2003 +9	2026-07-25 10:24:59.810
www.g.cn	74.125.206.94 66.102.1.94 2a00:1450:400c:c0b::5e 2a00:1450:400c:c02::5e +2	2026-06-17 13:15:17.954

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Certificate observations pending

TLS certs naming this domain in subject or SANs will appear here as our scan-layer catches them.

IPs Citing This Domain

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

101.254.113.7:443 href · ×1

Origin / IP-Leak

USP

When a hostname is served behind a CDN (e.g. Cloudflare), the origin server can sometimes be identified by matching its TLS cert against the protected hostname. Findings shown here are heuristic candidates, not guarantees.

No origin-IP leaks detected (yet)

Either this domain doesn't sit behind a CDN, or we haven't seen a TLS cert from a non-CDN IP matching this hostname. Run a fullscan to refresh the cert→IP cross-reference.

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type	Value	First seen	Last seen
TXT	v=spf1 -all	2026-06-02 02:09:23.865	2026-07-25 10:24:59.810
AAAA	2a00:1450:4001:c17::5e	2026-06-02 02:09:23.865	2026-06-02 02:09:23.865
NS	ns3.google.com	2026-06-02 02:09:23.865	2026-07-25 10:24:59.810
NS	ns1.google.com	2026-06-02 02:09:23.865	2026-07-25 10:24:59.810
MX	0 smtp.google.com	2026-06-02 02:09:23.865	2026-07-25 10:24:59.810
CAA	0 issue "pki.goog"	2026-06-02 02:09:23.865	2026-07-25 10:24:59.810
NS	ns4.google.com	2026-06-02 02:09:23.865	2026-07-25 10:24:59.810
A	142.251.168.94	2026-06-02 02:09:23.865	2026-06-02 02:09:23.865
NS	ns2.google.com	2026-06-02 02:09:23.865	2026-07-25 10:24:59.810
AAAA	2a00:1450:400c:c0b::5e	2026-06-03 22:21:28.970	2026-06-03 22:21:28.970
A	172.217.17.195	2026-06-03 22:21:28.970	2026-06-03 22:21:28.970
A	142.251.39.131	2026-06-17 06:55:00.993	2026-07-15 18:20:13.830
AAAA	2a00:1450:400e:804::2003	2026-06-17 06:55:00.993	2026-07-15 18:20:13.830
A	216.58.198.35	2026-06-20 04:54:46.728	2026-07-25 10:24:59.810
AAAA	2a00:1450:400e:814::2003	2026-06-20 04:54:46.728	2026-07-25 10:24:59.810
AAAA	2a00:1450:4002:400::2003	2026-07-15 18:11:18.022	2026-07-15 18:11:18.022
AAAA	2a00:1450:4025:401::5e	2026-07-15 20:04:13.980	2026-07-15 20:04:13.980
A	216.58.198.99	2026-07-15 20:04:13.980	2026-07-15 20:04:13.980
AAAA	2a00:1450:4017:81e::2003	2026-07-21 21:52:37.258	2026-07-21 21:52:37.258
A	172.217.20.67	2026-07-21 21:52:37.258	2026-07-21 21:52:37.258