Check-Host.cc

Domain

g.page

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

Run a live full scan of g.page

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
42
A/AAAA targets
Subdomains
15
CT + scan + body
Record Types
5
seen in DNS
Observed Certs
35
in our scans

DNS Records

A
216.239.32.27
AAAA
2001:4860:4802:32::1b
MX
NS
ns1.zdns.google, ns2.zdns.google, ns3.zdns.google, ns4.zdns.google
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
www.g.page 2026-06-20 19:15:48.319
g.page 2026-07-28 20:47:52.650

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.

178.77.98.15:443 href · ×28
161.35.21.184:443 href · ×20
72.167.226.214:443 href · ×19
67.207.93.119:443 href · ×17
161.35.252.230:443 href · ×17
125.228.123.107:443 href · ×16
3.226.155.97:443 href · ×12
104.131.167.84:80 href · ×10
103.63.29.72:80 href · ×8
13.234.10.97:443 href · ×7
54.159.202.116:443 href · ×6
64.225.243.157:443 href · ×6
78.47.130.168:443 href · ×6
18.199.27.134:443 href · ×6
195.201.96.113:443 href · ×6
3.124.103.113:443 href · ×6
185.222.156.139:443 href · ×6
82.67.64.8:443 href · ×6
63.75.167.158:443 href · ×6
104.225.208.169:443 href · ×6
13.59.36.76:443 href · ×5
3.111.183.223:443 href · ×5
178.128.230.221:443 href · ×5
15.235.128.10:443 href · ×5
217.154.17.227:443 href · ×5
183.181.94.89:443 href · ×5
20.51.149.138:443 href · ×5
178.172.236.51:443 href · ×5
178.32.107.30:80 href · ×4
45.82.15.80:443 href · ×4
134.209.67.60:443 href · ×4
15.204.245.71:443 href · ×4
188.166.242.36:80 href · ×4
152.67.151.199:80 href · ×4
170.10.163.248:443 href · ×4
155.138.244.114:80 href · ×4
107.170.34.206:443 href · ×4
122.160.255.149:80 href · ×4
198.12.209.109:80 href · ×4
2.222.219.121:443 href · ×4
165.227.226.65:8443 href · ×4
134.199.184.117:443 href · ×4
142.44.213.171:80 href · ×4
209.188.114.77:443 href · ×4
34.110.135.146:443 href · ×4
18.135.71.2:80 href · ×4
47.206.165.203:443 href · ×4
104.131.87.136:443 href · ×4
139.59.191.48:443 href · ×4
71.31.157.240:80 href · ×4

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

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.