Check-Host.cc

Domain

share.google

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

Run a live full scan of share.google

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
in our scans

DNS Records

A
216.239.32.27
AAAA
2001:4860:4802:32::1b
MX
NS
ns1.googledomains.com, ns2.googledomains.com, ns3.googledomains.com, ns4.googledomains.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

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.

211.72.250.163:443 href · ×90
84.46.253.189:443 href · ×20
13.233.190.155:443 href · ×16
204.168.132.23:443 href · ×12
75.119.142.165:80 href · ×10
85.215.124.8:443 href · ×10
8.215.42.178:443 href · ×9
52.58.216.245:443 href · ×8
63.181.213.90:443 href · ×8
52.26.19.31:80 href · ×8
212.227.26.6:443 href · ×8
13.206.88.132:443 href · ×8
43.204.162.68:80 href · ×6
78.47.130.168:443 href · ×6
162.0.239.252:443 href · ×6
204.168.132.23:8080 href · ×6
195.20.225.94:80 href · ×6
34.31.164.13:80 href · ×6
52.86.71.37:80 href · ×6
117.53.46.12:443 href · ×5
162.241.27.237:443 href · ×5
13.134.13.226:443 href · ×5
3.19.235.210:443 href · ×5
198.38.90.32:443 href · ×5
178.128.1.68:443 href · ×4
91.218.230.19:443 href · ×4
27.54.133.169:443 href · ×4
87.106.47.147:443 href · ×4
204.168.163.218:443 href · ×4
103.39.135.26:443 href · ×4
66.116.199.88:443 href · ×4
192.243.103.101:443 href · ×4
23.88.39.87:443 href · ×4
3.135.181.139:443 href · ×4
13.140.140.167:80 href · ×4
8.232.223.176:443 href · ×4
51.83.159.215:443 href · ×4
143.244.161.152:443 href · ×4
135.181.92.230:443 href · ×4
114.202.247.36:443 href · ×4
191.252.110.212:80 href · ×4
162.144.238.11:443 href · ×4
91.99.173.73:443 href · ×4
168.144.152.175:443 href · ×4
57.131.49.225:443 href · ×4
178.104.41.231:443 href · ×3
206.189.90.106:443 href · ×3
129.121.74.156:443 href · ×3
3.25.131.101:80 href · ×3
204.168.212.58:443 href · ×3

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.