Check-Host.cc

Domain

firefox.com

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

Run a live full scan of firefox.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
35.190.14.201
AAAA
2600:1901:0:c197::
MX
10 smtp1.mdc1.mozilla.com
NS
ns1-240.akam.net, ns4-64.akam.net, ns5-65.akam.net, ns7-66.akam.net
TXT
3mjnbdj3h9wpslgz0gfly0pbr94wd12y, _vrrc3v9222jxd6yhvt728lc4om6z0ff, facebook-domain-verification=wcer1w80xkwrzqftwc3shhkel9ys8m, google-gws-recovery-domain-verification=70476672, google-site-verification=ZqFMUZ8Gzf13U_nchwvBgRE_sRAxAR5xLz-X5w4BU4s, kr1887r7cjn94rzlgp1bpnj8v94wd3mg, v=spf1 mx a include:amazonses.com include:mail.zendesk.com include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email -all
CNAME
CAA
128 iodef "mailto:foxsec+caaiodef@mozilla.com", 128 issue "amazon.com", 128 issue "amazonaws.com", 128 issue "amazontrust.com", 128 issue "awstrust.com", 128 issue "digicert.com", 128 issue "letsencrypt.org"

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

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.