Check-Host.cc
Domain

4passive.com

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

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

DNS Records

A
198.202.211.1
AAAA
MX
NS
ns-cloud-d1.googledomains.com, ns-cloud-d2.googledomains.com, ns-cloud-d3.googledomains.com, ns-cloud-d4.googledomains.com
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.

Subdomain Resolves to Last seen
4passive.com 2026-08-30 02:24:50.759

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.

CT-Log Evidence

Certificates from public Certificate Transparency logs whose subject or SAN names this domain — including historic certs we never observed live.

3072f43efd3dbf45… cloudflare · nimbus2026
Subject: 4passive.com
Issuer: YE1
SANs: 4passive.com
Valid: 2026-08-26 11:56:48 → 2026-11-24 11:56:47
aa1ebcdc19c9556a… google · xenon2026h2
Subject: 4passive.com
Issuer: YE1
SANs: 4passive.com
Valid: 2026-08-26 11:56:48 → 2026-11-24 11:56:47
9ca5aac6a30ab186… google · xenon2026h2
Subject: 4passive.com
Issuer: YR2
SANs: 4passive.com
Valid: 2026-08-26 11:56:40 → 2026-11-24 11:56:39
4c447a08a544b0e5… google · xenon2026h2
Subject: 4passive.com
Issuer: YE1
SANs: 4passive.com
Valid: 2026-08-26 11:21:32 → 2026-11-24 11:21:31
2b999fa8cecaf647… google · xenon2026h2
Subject: 4passive.com
Issuer: YR1
SANs: 4passive.com
Valid: 2026-08-26 11:21:29 → 2026-11-24 11:21:28

Threat Intelligence

Domain threat-intel pending

Matches in URLhaus, OpenPhish, PhishTank, malware feeds, and Spamhaus DBL.

History

Passive DNS — every value this name ever resolved to and when we first / last observed it. Updates every cycle of our forward-DNS crawler.

Type Value First seen Last seen
NS ns-cloud-d4.googledomains.com 2026-08-30 02:21:50.781 2026-08-30 02:24:50.759
NS ns-cloud-d2.googledomains.com 2026-08-30 02:21:50.781 2026-08-30 02:24:50.759
NS ns-cloud-d1.googledomains.com 2026-08-30 02:21:50.781 2026-08-30 02:24:50.759
NS ns-cloud-d3.googledomains.com 2026-08-30 02:21:50.781 2026-08-30 02:24:50.759
A 198.202.211.1 2026-08-30 02:21:50.781 2026-08-30 02:24:50.759