Domain

ai.google.dev

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

DNS Check HTTP Check Run Full Scan .dev TLD

Run a live full scan of ai.google.dev

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

133

A/AAAA targets

Subdomains

—

CT + scan + body

Record Types

seen in DNS

Observed Certs

in our scans

DNS Records

108.177.15.100, 108.177.15.101, 108.177.15.102, 108.177.15.113, 108.177.15.138, 108.177.15.139, 142.250.110.100, 142.250.110.101

AAAA

2a00:1450:4001:c0f::64, 2a00:1450:4001:c0f::65, 2a00:1450:4001:c0f::66, 2a00:1450:4001:c0f::71, 2a00:1450:4001:c0f::8a, 2a00:1450:4001:c15::65, 2a00:1450:4001:c15::66, 2a00:1450:4001:c15::8a

—

TXT

—

CNAME

—

CAA

—

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

Subdomain enumeration pending

Every subdomain ever issued a TLS cert under this apex — extracted from Certificate Transparency logs, our own scan observations and body references.

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.

139.196.197.45:443 href · ×4

34.70.228.39:443 href · ×3

182.92.221.242:80 href · ×3

69.12.65.113:443 href · ×2

144.24.78.22:8081 href · ×2

118.25.194.65:80 href · ×2

132.145.100.69:80 href · ×2

155.94.173.199:443 href · ×2

194.39.123.145:443 href · ×2

89.167.113.212:80 href · ×2

52.35.88.118:80 href · ×2

43.153.219.204:443 href · ×2

80.97.27.68:8888 href · ×1

47.85.167.182:80 href · ×1

139.162.175.101:443 href · ×1

122.51.232.171:80 href · ×1

152.70.107.243:8080 href · ×1

119.91.44.75:443 href · ×1

47.93.42.201:443 href · ×1

193.242.109.112:443 href · ×1

8.155.27.198:80 href · ×1

43.155.206.116:443 href · ×1

101.35.249.212:443 href · ×1

49.233.210.82:8888 href · ×1

101.96.195.70:443 href · ×1

47.76.61.170:80 href · ×1

43.133.225.82:443 href · ×1

23.141.172.213:443 href · ×1

52.33.198.55:443 href · ×1

147.182.143.164:443 href · ×1

104.249.10.72:80 href · ×1

193.112.95.186: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

Domain timeline pending

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