204.8.96.160
Thinking Process:
1. Analyze the Request:
* Role: IP intelligence analyst for IPDebrief (legitimate cybersecurity threat intelligence platform).
* Task: Generate an intelligence briefing for IP 204.8.96.160/32.
* Constraints: Concise, actionable threat intelligence narrative suitable for a SOC analyst. Use provided profile data. Do not mention internal tools. Write in third person, past tense. Do not speculate beyond data. Do not include disclaimers.
* Input Data: A JSON-like
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Quintex Alliance Consulting |
| ASN | AS62744 |
| Network Name | QUINTEX96 |
| CIDR Block | 204.8.96.0/22 |
| RIR | ARIN |
| Country | United States |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | tor71.quintex.com |
| Forward Confirmed | Yes — FCrDNS verified |
| Forward Hostnames | tor71.quintex.com |
🔐 DNS Hygiene
| Hygiene Score | 60% (Good) |
| SPF | 2/2 domains |
| DMARC | 2/2 domains |
| FCrDNS | Verified |
| DNSSEC | Not signed |
| CAA | Not configured |
| Domains Checked | 2 domains |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Web Server |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 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-07-03T00:00:00+00:00 |
| Valid Until | 2027-02-21T00:00:00+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 233 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 | 24% | 2 | 4 |
| routing | 21% | 2 | 4 |
| services | 17% | 2 | 3 |
| ownership | 19% | 3 | 4 |
| reputation | 19% | 1 | 4 |
| geolocation | 21% | 2 | 4 |
| Overall | 20% | 12 | 23 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Moderate (55%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-02 04:19:52 UTC |
| Last Seen | 2026-09-29 22:33:39 UTC |
| Profile Built | 2026-09-29 22:59:33 UTC |
| Data Freshness | Live |
| Signal Types | 30 |
| Total Observations | 51 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 204.8.96.160
Who owns the IP address 204.8.96.160?
204.8.96.160 is registered to Quintex Alliance Consulting. The address falls within the 204.8.96.0/22 network block. Registration is held at ARIN.
Where is 204.8.96.160 located?
Geolocation data places 204.8.96.160 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.160 malicious or safe?
204.8.96.160 currently carries a moderate risk assessment, meaning some indicators warrant caution, but the evidence is mixed. This assessment is generated from continuously collected signals and can change over time.
What is the hostname for 204.8.96.160?
The reverse DNS (PTR) record for 204.8.96.160 is tor71.quintex.com. This hostname is forward-confirmed, meaning it resolves back to the same address.
What ports are open on 204.8.96.160?
Responsive ports observed on 204.8.96.160 include 80, 443, 22. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.
Is 204.8.96.160 a VPN, proxy, or data center address?
204.8.96.160 is classified as the Tor network based on network ownership and behavioural analysis.