Check-Host.cc

Domain

linkdata.org

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

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

DNS Records

A
133.125.237.192
AAAA
MX
1 aspmx.l.google.com, 10 aspmx2.googlemail.com, 10 aspmx3.googlemail.com, 5 alt1.aspmx.l.google.com, 5 alt2.aspmx.l.google.com
NS
01.dnsv.jp, 02.dnsv.jp, 03.dnsv.jp, 04.dnsv.jp
TXT
MS=AA1BDB345F76C6F6B8964E49DB48782E40E57FE6, google-site-verification=RaI9-wIuEP3AHR8Fvf6NEcsif_QsIYLRr3S0fVffneQ, google-site-verification=uXFK-kF19EE0DZLRzlX0T7Kgf8lQQcVb84ATbgLXbRU
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
app.linkdata.org
1970-01-01 00:00:00.000
dss.staging.linkdata.org
1970-01-01 00:00:00.000
idea.linkdata.org
1970-01-01 00:00:00.000
linkdata.org 2026-07-17 05:58:17.649
news.linkdata.org
1970-01-01 00:00:00.000
repo.linkdata.org 2026-06-23 10:02:09.592
test.linkdata.org
1970-01-01 00:00:00.000
user.linkdata.org
1970-01-01 00:00:00.000
user.test.linkdata.org
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: repo.linkdata.org
Issuer: R12
SANs: repo.linkdata.org

IPs Citing This Domain

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

116.80.78.250:443 href · ×4
54.64.201.53: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

Domain timeline pending

Passive-DNS history accumulates as our forward-DNS crawler observes A/AAAA/MX/NS/TXT records over time.