Check-Host.cc

Domain

google-analytics.com

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

Run a live full scan of google-analytics.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
310
A/AAAA targets
Subdomains
33
CT + scan + body
Record Types
5
seen in DNS
Observed Certs
171
in our scans

DNS Records

A
0.0.0.0, 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
AAAA
2a00:1450:4001:c0f::63, 2a00:1450:4001:c0f::67, 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
MX
NS
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.

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.

141.101.178.121:443 href · ×3
141.101.178.105:443 href · ×3
68.183.248.195:443 href · ×2
38.108.68.87:80 href · ×2
200.57.176.98:443 href · ×2
207.58.129.133:443 href · ×2
188.245.175.52:80 href · ×2
142.11.198.182:80 href · ×2
85.159.150.160:80 href · ×2
188.128.202.211:443 href · ×2
50.63.129.190:443 href · ×2
45.76.252.248:443 href · ×2
142.11.198.149:443 href · ×2
80.77.124.105:443 href · ×2
188.225.82.94:443 href · ×2
83.148.16.192:80 href · ×2
87.229.102.192:443 href · ×2
13.60.30.137:443 href · ×2
65.21.243.217:443 href · ×1
216.251.255.101:443 href · ×1
75.119.155.28:443 href · ×1
159.203.35.65:443 href · ×1
3.218.54.184:443 href · ×1
160.16.224.226:443 href · ×1
142.11.198.182:443 href · ×1
34.51.81.136:443 href · ×1
5.144.166.23:443 href · ×1
167.99.121.111:443 href · ×1
46.105.74.39:443 href · ×1
3.111.81.63:443 href · ×1
54.66.25.137:443 href · ×1
139.59.246.90:443 href · ×1
202.139.216.122:443 href · ×1
50.62.139.141:80 href · ×1
167.172.20.237:443 href · ×1
173.255.198.105:443 href · ×1
216.185.13.161:443 href · ×1
18.181.149.33:443 href · ×1
167.172.20.237:80 href · ×1
167.172.89.9:80 href · ×1
50.87.143.224:80 href · ×1
192.185.49.68:443 href · ×1
128.140.26.83:443 href · ×1
192.64.78.27:443 href · ×1
164.90.146.238:80 href · ×1
184.169.226.208:443 href · ×1
173.255.194.198:443 href · ×1
45.76.188.200:443 href · ×1
159.198.40.209:80 href · ×1
18.116.16.1: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.