Check-Host.cc

Domain

wwd.com

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

Run a live full scan of wwd.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
AAAA
MX
NS
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
image.email.wwd.com 2026-06-23 01:39:09.544
tollbit.wwd.com 2026-07-26 10:46:00.019
cdn.wwd.com
1970-01-01 00:00:00.000
cloud.email.wwd.com
1970-01-01 00:00:00.000
mi.wwd.com
1970-01-01 00:00:00.000
pages.email.wwd.com
1970-01-01 00:00:00.000
read.wwd.com
1970-01-01 00:00:00.000
ssc.wwd.com
1970-01-01 00:00:00.000
subscribe.wwd.com
1970-01-01 00:00:00.000
view.email.wwd.com
1970-01-01 00:00:00.000
wwd.com 2026-07-15 20:04:13.980
www.wwd.com
1970-01-01 00:00:00.000

Tech Stack

Tech detection pending

Wappalyzer-rules detect CMS, frameworks, analytics, JS libs and server-side languages on this domain.

TLS Certificates

Subject: www.mewwwd.com
Issuer: YR2
SANs: mewwwd.com, other.mewwwd.com, www.mewwwd.com, www.other.mewwwd.com
Subject: *.iwwd.com
Issuer: Sectigo Public Server Authentication CA DV R36
SANs: *.iwwd.com, iwwd.com
Subject: *.awwd.com
Issuer: Go Daddy Secure Certificate Authority - G2
SANs: *.awwd.com, awwd.com
Subject: tmall.fffwwwd.com
Issuer: R12
SANs: tmall.fffwwwd.com
Subject: wwd.com
Issuer: E5
SANs: wwd.com

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.