Check-Host.cc

Domain

firehydrant.com

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

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

DNS Records

A
75.2.60.5
AAAA
MX
1 aspmx.l.google.com, 10 alt3.aspmx.l.google.com, 10 alt4.aspmx.l.google.com, 5 alt1.aspmx.l.google.com, 5 alt2.aspmx.l.google.com
NS
ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com, ns-cloud-b4.googledomains.com
TXT
MS=msms78984336, POSTHOG-SITE-VERIFICATION=LjxMNqZMzgtBRHaTYCBAAUwVVBBw4q6r, ZOOM_verify_LS6YJcV3d08z2IDNiKCOT8, apple-domain-verification=B2m6aTP5RVkCcSLI, atlassian-domain-verification=lvSwio2W6egrCJJ2JEstGLwpYiXFbilpLx6tCtEO7KKqThKctbxByK/muFeU5BxA, docusign=4aa8fd4c-85e1-4e7e-be35-99cc37e4fbef, google-site-verification=QMnx-lFoFap1z9LBw3bDExm3W6S-LUefS8BQI32iLks, google-site-verification=ZUkagCmJS6bUu6M-tSZSdzE3yJwb2NPpF1i9O-cvKm4
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.