Check-Host.cc

Domain

join.com

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

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

DNS Records

A
104.20.25.174, 172.66.155.68
AAAA
2606:4700:10::6814:19ae, 2606:4700:10::ac42:9b44
MX
1 aspmx.l.google.com, 10 aspmx2.googlemail.com, 10 aspmx3.googlemail.com, 5 alt1.aspmx.l.google.com, 5 alt2.aspmx.l.google.com
NS
clayton.ns.cloudflare.com, journey.ns.cloudflare.com
TXT
MS=93EB2F9ED1D2406DFB1DCE7EC87538C0D338BAA4, detectify-verification=b83668654ea6d415c1f09675639f49f6, facebook-domain-verification=gdi7ron8li5j1p2y071i1dzm7x3ikn, google-site-verification=O2t9Hgx708PQvBYijkZnOZS0SW63D_R3YWaJPtkp6bk, google-site-verification=yqCwOIkEOc1329nzN_RE1G4h2cP8lK0ZDyJ-M7ovyhw, stripe-verification=36a9877e50d4e1c02e0c0b4c3c606f5ba70d87c5dddf07a5747d25f531e8fd3f, v=spf1 include:spf.mandrillapp.com include:servers.mcsv.net include:_spf.google.com include:_spf.salesforce.com ~all
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

No citing IPs found yet

As the world-sweep progresses, hosts referencing this domain in their HTML will surface here.

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.