Your IP: 216.73.217.131
🏢 Ownership & Registration
| Organization | Tor Exit Nodes |
| ASN | — |
| Network Name | — |
| CIDR Block | — |
| RIR | — |
| Country | — |
| Abuse Contact | — |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 40% (Fair) |
| SPF | Present |
| DMARC | Present |
| FCrDNS | Not verified |
| DNSSEC | Not signed |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Tier 3 — Basic operator with some routing infrastructure |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| 22 | ssh | tcp | Banner detected |
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
CN=www.5hwz5xhz4yv.net
Issued by CN=www.rbesrohxtqlvkgdm5jj.com
Self-signed: No
| SANs | None |
| Valid From | 2025-12-30T00:00:00+00:00 |
| Valid Until | 2026-12-06T23:59:59+00:00 |
🛡️ Public Network Snapshot
| Origin ASN | AS62744 |
| Network Prefix | 204.8.96.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 25% | 1 | 1 |
| routing | 60% | 1 | 199 |
| services | 0% | 0 | 0 |
| ownership | 0% | 0 | 0 |
| reputation | 0% | 0 | 0 |
| geolocation | 0% | 0 | 0 |
| Overall | 14% | 2 | 200 |
Coverage: 2/6 dimensions · Data sufficiency: partial
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Very Low (15%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
⚠ Claimed geolocation contradicts RTT physics measurement
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-02 04:19:52 UTC |
| Last Seen | 2026-09-29 23:34:42 UTC |
| Profile Built | 2026-09-29 23:43:43 UTC |
| Data Freshness | Live |
| Signal Types | 14 |
| Total Observations | 10000 |
🔍 14 signal types · 10000 observations collected
This report is generated from 14+ independent intelligence signals including
ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds,
behavioral fingerprinting, and more.
Full dossier details are available via our API.
Full dossier details are available via our API.
❓ Frequently Asked Questions About 204.8.96.76
Who owns the IP address 204.8.96.76?
204.8.96.76 is registered to Tor Exit Nodes.
Where is 204.8.96.76 located?
Geolocation data places 204.8.96.76 in Chicago, TX, United States. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 204.8.96.76 malicious or safe?
204.8.96.76 currently carries a low risk assessment, meaning no significant threat indicators have been observed. This assessment is generated from continuously collected signals and can change over time.
What ports are open on 204.8.96.76?
Responsive ports observed on 204.8.96.76 include 80, 443, 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.
🏘️ Related IP Addresses
Nearby addresses
204.8.96.64204.8.96.65204.8.96.66204.8.96.67204.8.96.68204.8.96.69204.8.96.70204.8.96.71204.8.96.72204.8.96.73204.8.96.74204.8.96.75
Browse related networks
ℹ️ About This Report
All data shown is publicly available network metadata — IP addresses do not reliably identify individuals.
Assessments are probabilistic and should not be used as sole basis for access control decisions.
To report an issue or request data review, contact admin@ipdebrief.com.