Domain

googleapis.com

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

DNS Check HTTP Check Run Full Scan .com TLD

Run a live full scan of googleapis.com

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

139

A/AAAA targets

Subdomains

CT + scan + body

Record Types

seen in DNS

Observed Certs

in our scans

DNS Records

108.177.15.103, 108.177.15.104, 108.177.15.105, 108.177.15.106, 108.177.15.147, 108.177.15.99, 142.250.110.103, 142.250.110.104

AAAA

2a00:1450:4001:c0f::63, 2a00:1450:4001:c0f::68, 2a00:1450:4001:c0f::69, 2a00:1450:4001:c0f::6a, 2a00:1450:4001:c0f::93, 2a00:1450:4001:c13::63, 2a00:1450:4001:c13::67, 2a00:1450:4001:c13::68

—

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

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
googleapis.com	142.251.142.196 2a00:1450:400c:c06::6a 2a00:1450:400c:c06::93 2a00:1450:400e:806::2004 +135	2026-07-28 02:05:12.153

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.

210.211.109.3:80 href · ×2

84.38.66.224:443 href · ×2

158.23.139.16:443 href · ×2

2.26.109.137:443 href · ×2

38.15.130.54:443 href · ×2

34.101.156.191:443 href · ×2

141.101.178.105:443 href · ×2

54.205.248.116:443 href · ×2

168.119.246.75:443 href · ×2

38.15.130.54:80 href · ×2

51.222.139.117:443 href · ×2

198.54.123.165:443 href · ×2

141.101.178.121:443 href · ×2

89.169.38.185:80 href · ×2

185.125.202.164:443 href · ×2

109.224.242.253:80 href · ×2

188.120.236.162:443 href · ×2

72.56.32.42:443 href · ×2

45.205.6.140:80 href · ×2

193.31.98.178:80 href · ×2

16.58.21.5:443 href · ×1

3.20.238.11:80 href · ×1

3.128.139.124:443 href · ×1

217.149.25.37:443 href · ×1

5.42.221.110:443 href · ×1

35.200.197.149:443 href · ×1

34.72.252.47:443 href · ×1

100.55.151.247:8000 href · ×1

43.205.138.210:80 href · ×1

178.172.242.78:443 href · ×1

185.180.3.235:80 href · ×1

44.223.68.102:80 href · ×1

95.165.100.11:443 href · ×1

70.32.80.74:443 href · ×1

138.197.22.182:443 href · ×1

210.219.216.226:80 href · ×1

82.14.201.155:443 href · ×1

66.116.245.238:8000 href · ×1

44.219.90.21:80 href · ×1

89.125.198.136:443 href · ×1

35.223.121.122:80 href · ×1

85.209.0.59:443 href · ×1

52.14.64.1:443 href · ×1

94.130.229.220:80 href · ×1

218.212.7.187:80 href · ×1

5.39.250.228:443 href · ×1

46.59.71.72:80 href · ×1

80.96.109.61:443 href · ×1

78.17.198.221:80 href · ×1

157.22.192.126:80 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.