Check-Host.cc

Domain

www.digg.com

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

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

DNS Records

A
216.150.1.1, 216.150.1.129, 216.150.1.193, 216.150.1.65, 216.150.16.1, 216.150.16.129, 216.150.16.193, 216.150.16.65
AAAA
MX
NS
TXT
CNAME
CAA
0 issue "globalsign.com", 0 issue "letsencrypt.org", 0 issue "pki.goog", 0 issue "sectigo.com"

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.

198.199.119.201:80 href · ×21
111.67.23.243:443 href · ×10
198.199.115.101:80 href · ×10
173.236.241.121:80 href · ×8
192.71.105.140:80 href · ×8
50.59.99.202:80 href · ×8
209.126.180.251:443 href · ×5
209.114.176.61:443 href · ×1
188.226.171.173:443 href · ×1
67.210.32.188:80 href · ×1
37.35.105.230:80 href · ×1
198.235.63.150:443 href · ×1
170.168.15.175:80 href · ×1
213.108.199.173:443 href · ×1
66.246.119.71:443 href · ×1
151.252.31.185:443 href · ×1
37.35.105.230:443 href · ×1
185.154.15.204:443 href · ×1
52.90.157.194:80 href · ×1
57.129.70.10:443 href · ×1
162.243.62.89: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

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 216.150.16.65 2026-05-26 06:36:35.881 2026-07-16 23:06:50.819
CAA 0 issue "sectigo.com" 2026-05-26 06:36:35.881 2026-07-28 08:31:23.092
CAA 0 issue "pki.goog" 2026-05-26 06:36:35.881 2026-07-28 08:31:23.092
CAA 0 issue "letsencrypt.org" 2026-05-26 06:36:35.881 2026-07-28 08:31:23.092
CAA 0 issue "globalsign.com" 2026-05-26 06:36:35.881 2026-07-28 08:31:23.092
A 216.150.1.65 2026-05-26 06:36:35.881 2026-07-16 23:06:50.819
A 216.150.1.1 2026-05-26 11:56:55.544 2026-07-19 20:15:00.065
A 216.150.16.1 2026-05-26 11:56:55.544 2026-07-19 20:15:00.065
A 216.150.16.193 2026-05-26 21:42:58.912 2026-07-24 17:22:51.458
A 216.150.1.193 2026-05-26 21:42:58.912 2026-07-24 17:22:51.458
A 216.150.1.129 2026-07-25 15:25:35.996 2026-07-28 08:31:23.092
A 216.150.16.129 2026-07-25 15:25:35.996 2026-07-28 08:31:23.092