Check-Host.cc

Try 1.1.1.1 AS13335 check-host.cc /country/de /tld/cc
Domain

validator.w3.org

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

DNS Check HTTP Check Run Full Scan .org TLD

Run a live full scan of validator.w3.org

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
4
A/AAAA targets
Subdomains
—
CT + scan + body
Record Types
2
seen in DNS
Observed Certs
—
in our scans

DNS Records

A
104.18.22.19, 104.18.23.19
AAAA
2606:4700::6812:1613, 2606:4700::6812:1713
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

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

Hosts whose HTML body references this domain. Strong signal for origin/mirror/embed discovery.

64.62.211.22:80 href · ×8
109.109.205.8:443 href · ×6
157.173.112.208:80 href · ×6
82.98.90.146:80 href · ×4
83.238.166.222:80 href · ×4
72.52.110.30:80 href · ×4
45.189.170.10:80 href · ×3
200.150.114.123:443 href · ×3
31.31.73.190:80 href · ×3
80.150.124.83:443 href · ×3
149.56.117.44:80 href · ×3
15.236.109.111:443 href · ×3
64.182.120.229:80 href · ×3
202.72.239.61:80 href · ×3
66.39.154.38:80 href · ×3
45.56.83.197:80 href · ×3
59.167.177.213:80 href · ×3
212.79.110.217:80 href · ×3
162.243.156.85:80 href · ×3
12.218.7.37:80 href · ×3
153.122.148.65:443 href · ×3
66.39.33.5:443 href · ×3
146.66.74.99:80 href · ×3
96.49.240.220:80 href · ×3
40.70.79.242:80 href · ×3
23.111.69.243:443 href · ×3
50.116.48.129:80 href · ×3
212.36.22.44:80 href · ×3
74.207.251.48:80 href · ×3
195.210.28.115:80 href · ×3
141.94.5.97:80 href · ×3
88.99.30.137:80 href · ×3
45.77.138.221:443 href · ×3
191.37.176.127:80 href · ×3
107.178.97.141:80 href · ×3
88.198.46.232:443 href · ×3
13.38.108.151:80 href · ×3
149.202.171.186:80 href · ×3
91.205.40.18:80 href · ×3
62.115.181.45:80 href · ×3
95.131.48.73:80 href · ×3
94.172.162.24:80 href · ×3
194.181.67.74:443 href · ×3
199.168.185.91:80 href · ×3
110.173.227.241:443 href · ×2
192.99.19.27:80 href · ×2
79.137.34.72:80 href · ×2
107.170.220.54:80 href · ×2
193.19.136.125:80 href · ×2
89.105.221.130:80 href · ×2

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

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
A 104.18.22.19 2026-05-25 21:54:50.392 2026-07-28 20:39:29.599
AAAA 2606:4700::6812:1713 2026-05-25 21:54:50.392 2026-07-28 20:39:29.599
AAAA 2606:4700::6812:1613 2026-05-25 21:54:50.392 2026-07-28 20:39:29.599
A 104.18.23.19 2026-05-25 21:54:50.392 2026-07-28 20:39:29.599