Check-Host.cc

Domain

rdfs.org

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

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

DNS Records

A
78.153.210.11
AAAA
2a01:a8:dc0:334:1::4e2
MX
NS
ns1.blacknight.com, ns2.blacknight.com, ns3.blacknight.com, ns4.blacknight.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
rdfs.org 2026-07-28 20:39:29.599

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.

3.89.169.150:80 href · ×20
79.72.57.8:443 href · ×10
206.87.224.235:443 href · ×10
34.193.211.208:80 href · ×8
34.205.21.209:443 href · ×8
198.252.110.193:80 href · ×8
34.193.211.208:443 href · ×8
202.68.188.58:443 href · ×6
100.22.2.250:443 href · ×6
68.115.195.23:443 href · ×6
107.180.99.211:80 href · ×6
89.111.146.187:80 href · ×6
64.71.164.172:443 href · ×6
45.55.234.213:443 href · ×6
54.152.206.211:80 href · ×4
178.172.41.72:80 href · ×4
128.138.136.220:443 href · ×4
209.190.172.16:443 href · ×4
139.78.203.106:443 href · ×4
68.178.175.147:80 href · ×4
128.119.49.23:443 href · ×4
108.167.173.108:443 href · ×4
154.26.196.227:443 href · ×4
79.137.38.18:80 href · ×4
148.228.156.86:80 href · ×4
199.107.16.154:443 href · ×4
129.21.16.82:443 href · ×4
144.122.145.143:443 href · ×4
207.231.205.8:443 href · ×4
5.9.226.35:80 href · ×4
164.30.70.145:443 href · ×4
103.11.191.184:443 href · ×4
154.26.196.228:443 href · ×4
34.76.49.176:443 href · ×4
206.12.88.137:80 href · ×4
67.55.94.158:80 href · ×4
154.31.188.70:443 href · ×4
47.76.115.10:80 href · ×4
154.31.184.81:443 href · ×4
45.33.61.121:443 href · ×4
23.235.205.175:443 href · ×4
109.74.203.117:443 href · ×4
128.249.207.16:443 href · ×4
148.202.228.13:80 href · ×4
154.23.142.105:443 href · ×4
81.200.114.114:443 href · ×4
98.86.80.101:443 href · ×2
154.26.196.251:443 href · ×2
192.186.213.39:80 href · ×2
178.57.217.82:443 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 78.153.210.11 2026-05-25 21:56:50.553 2026-07-28 20:39:29.599
AAAA 2a01:a8:dc0:334:1::4e2 2026-05-25 21:56:50.553 2026-07-28 20:39:29.599
NS ns1.blacknight.com 2026-05-25 22:07:29.493 2026-07-28 20:39:29.599
NS ns3.blacknight.com 2026-05-25 22:07:29.493 2026-07-28 20:39:29.599
NS ns4.blacknight.com 2026-05-25 22:07:29.493 2026-07-28 20:39:29.599
NS ns2.blacknight.com 2026-05-25 22:07:29.493 2026-07-28 20:39:29.599