204.8.96.156 is an IPv4 address operated by Tor Exit Nodes, geolocated to Chicago, United States. Its reverse DNS name is tor67.quintex.com. As of November 7, 2026, IPDebrief rates it Low Risk (25/100); no anonymizing service was detected.
Intellective briefing for IP 204.8.96.156 indicates a low-risk profile with a risk score of 25. Analysis confirmed the host functions as a web server located in the United States. Routing data originated from ASN 62744 within the 204.8.96.0/24 block, with valid RPKI state and IRR consistency.
Open services included HTTP, HTTPS, and SSH on ports 80, 443, and 22 respectively. TLS certificate inspection revealed a mismatch between the issuer and subject domains. No active attacker classifications or known malicious campaigns were observed, and blacklist enumeration returned zero entries.
Behavioral analysis categorized the host as a "Suspicious Host" with low-grade risk indicators. The primary recommendation is to monitor the address with low severity alerting.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Tor Exit Nodes |
| ASN | — |
| Network Name | — |
| CIDR Block | — |
| RIR | ARIN |
| Country | — |
| Abuse Contact | — |
🌐 DNS Intelligence
| PTR | tor67.quintex.com |
| 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 |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | 2026-03-09T00:00:00+00:00 |
| Valid Until | 2026-12-19T00:00:00+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 201 days |
🛡️ 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 | 26% | 2 | 13 |
| routing | 26% | 3 | 140 |
| services | 31% | 2 | 10 |
| ownership | 8% | 1 | 1 |
| reputation | 20% | 1 | 9 |
| geolocation | 13% | 1 | 2 |
| Overall | 21% | 10 | 175 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (45%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-02 04:19:52 UTC |
| Last Seen | 2026-11-07 12:15:33 UTC |
| Profile Built | 2026-11-07 03:33:32 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 10000 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 204.8.96.156
Who owns the IP address 204.8.96.156?
204.8.96.156 is registered to Tor Exit Nodes.
Where is 204.8.96.156 located?
Geolocation data places 204.8.96.156 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.156 malicious or safe?
204.8.96.156 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 is the hostname for 204.8.96.156?
The reverse DNS (PTR) record for 204.8.96.156 is tor67.quintex.com. This hostname is not forward-confirmed, so it should be treated as a weak signal.
What ports are open on 204.8.96.156?
Responsive ports observed on 204.8.96.156 include 80, 443, 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.