example.com
HOSTPublic feed matches
No public feed evidence matches this value.
Passive DNS relationships
12 observations
Observed relationships do not establish maliciousness.
| Hostname | IP | Last seen | Hits | Provenance |
|---|---|---|---|---|
| example.com | 2606:4700:10::ac42:93f3 | Sep 2026First seen: Sep 2026 | 3 | CTIDAO DNS |
| example.com | 2606:4700:10::6814:179a | Sep 2026First seen: Sep 2026 | 3 | CTIDAO DNS |
| example.com | 172.66.147.243 | Sep 2026First seen: Sep 2026 | 3 | CTIDAO DNS |
| example.com | 104.20.23.154 | Sep 2026First seen: Sep 2026 | 3 | CTIDAO DNS |
Current DNS
Active DNS lookup; this is separate from passive DNS history.
Checked 9/28/2026, 5:33:35 AM
Popularity
Daily link and hosting prominence from top1m.org; not a security verdict or traffic estimate.
host · example.com
#1,170
domain · example.com
#817
Private research
Take this investigation further
4 public pDNS relationships are available. Private research adds exact timing, focused pivots, and matching paid-feed intelligence. Eligible logged-in entity visits cost 1 CTIDAO, including pivots, refreshes and returns.