Check-Host.cc

Domain

threatpost.com

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

Run a live full scan of threatpost.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
82.202.190.241
AAAA
MX
0 threatpost-com.mail.protection.outlook.com
NS
ns1.yandexcloud.net, ns2.yandexcloud.net
TXT
MS=ms46391769, _txtgz6goyzdtxawkcq5is98p30s2z88, google-site-verification=IAC53QOVd-CRvhQSmvtMwg2rfhe3Ku8AcQW-_TUue5U, mailru-verification: 37d00c741a9b052a, v=spf1 include:spf.protection.outlook.com -all,3600, vwy3przbhtm2gg0ybwdcs5j2lx3cy1tv, y7ksf87msb7d4tbrkncvg7c1v09s5mqq, yandex-verification: d2cfa297d6302d69
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
threatpost.com 2026-07-25 08:00:00.813

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.

15.188.50.123:80 href · ×44
41.78.83.104:443 href · ×11
44.199.99.192:443 href · ×10
192.241.134.186:80 href · ×10
173.255.249.99:443 href · ×2
65.21.148.202:443 href · ×1
207.246.109.180:443 href · ×1
54.150.251.223:80 href · ×1
136.55.235.129:80 href · ×1
196.200.160.10:443 href · ×1
80.78.31.143:443 href · ×1
108.161.135.192:80 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

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
TXT mailru-verification: 37d00c741a9b052a 2026-05-26 03:07:47.855 2026-07-25 08:00:00.813
TXT _txtgz6goyzdtxawkcq5is98p30s2z88 2026-05-26 03:07:47.855 2026-07-25 08:00:00.813
TXT MS=ms46391769 2026-05-26 03:07:47.855 2026-07-25 08:00:00.813
MX 0 threatpost-com.mail.protection.outlook.com 2026-05-26 03:07:47.855 2026-07-25 08:00:00.813
TXT yandex-verification: d2cfa297d6302d69 2026-05-26 03:07:47.855 2026-07-25 08:00:00.813
TXT y7ksf87msb7d4tbrkncvg7c1v09s5mqq 2026-05-26 03:07:47.855 2026-07-25 08:00:00.813
A 82.202.190.241 2026-05-26 03:07:47.855 2026-07-25 08:00:00.813
TXT v=spf1 include:spf.protection.outlook.com -all,3600 2026-05-26 03:07:47.855 2026-07-25 08:00:00.813
TXT google-site-verification=IAC53QOVd-CRvhQSmvtMwg2rfhe3Ku8AcQW-_TUue5U 2026-05-26 03:07:47.855 2026-07-25 08:00:00.813
NS ns1.yandexcloud.net 2026-05-26 03:07:47.855 2026-07-25 08:00:00.813
NS ns2.yandexcloud.net 2026-05-26 03:07:47.855 2026-07-25 08:00:00.813
TXT vwy3przbhtm2gg0ybwdcs5j2lx3cy1tv 2026-05-26 03:07:47.855 2026-07-25 08:00:00.813