Check-Host.cc

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

ipdata.co

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

DNS Check HTTP Check Run Full Scan .co TLD

Run a live full scan of ipdata.co

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
18.238.243.33, 18.238.243.60, 18.238.243.81, 18.238.243.93, 3.160.196.105, 3.160.196.115, 3.160.196.57, 3.160.196.94
AAAA
—
MX
1 aspmx.l.google.com, 10 alt3.aspmx.l.google.com, 10 alt4.aspmx.l.google.com, 5 alt1.aspmx.l.google.com, 5 alt2.aspmx.l.google.com
NS
ns-1132.awsdns-13.org, ns-1668.awsdns-16.co.uk, ns-272.awsdns-34.com, ns-851.awsdns-42.net
TXT
TICKET-9318, ahrefs-site-verification_41e42b731254e20a0302a437699e8b2e8b7a83df101b932dec9d62915b4524d0, google-site-verification=xlRNXzlAYrfLpHzFEPCmTvGTkWMmkcDPWhYPCNg5XBc, v=spf1 ~all
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
api.ipdata.co
18.184.111.96 3.67.217.132 18.185.196.10 51.102.174.126 +14
2026-07-28 01:29:26.112
ipdata.co
18.238.243.93 99.84.152.93 99.84.152.115 99.84.152.113 +8
2026-07-25 10:44:24.403
docs.ipdata.co
104.16.241.118 104.16.242.118 2606:4700::6810:f176 2606:4700::6810:f276
2026-06-20 15:06:27.004
www.ipdata.co
99.84.152.113 99.84.152.93 99.84.152.115 99.84.152.54
2026-05-31 01:13:40.771
checkout.ipdata.co
1970-01-01 00:00:00.000
dashboard-apis.ipdata.co
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

176.97.119.37:443 74b2e22e4e80…
Subject: api-logger.risipdata.com
Issuer: E7
SANs: api-logger.risipdata.com
18.119.240.89:443 b23e9abef398…
Subject: *.ssivipdata.com
Issuer: Amazon RSA 2048 M01
SANs: *.ssivipdata.com
154.6.40.13:443 488dc5b49ff8…
Subject: thekipdata.com
Issuer: thekipdata.com
SANs: thekipdata.com
18.190.192.1:443 b23e9abef398…
Subject: *.ssivipdata.com
Issuer: Amazon RSA 2048 M01
SANs: *.ssivipdata.com
3.136.238.220:443 b23e9abef398…
Subject: *.ssivipdata.com
Issuer: Amazon RSA 2048 M01
SANs: *.ssivipdata.com

IPs Citing This Domain

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

173.249.203.64:443 href · ×4
39.105.186.182:80 href · ×2
124.221.161.98:80 href · ×2
47.242.234.71:443 href · ×1
52.170.56.153:443 href · ×1

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.