102.165.53.82
The IP address 102.165.53.82 was attributed to the IPXO Incident Response Team (ASN 61317) within the 102.165.52.0/22 block. Geolocation data identified the origin as South Africa. Risk assessment assigned a reputation of Low Risk with a score of 25. Threat intelligence feeds indicated no known attacker status, spam source, or blacklist presence. Network reconnaissance revealed no open ports, classifying the service purpose as Firewalled / No Services. DNS analysis showed no forward resolution or PTR hostnames. Control plane data identified the BGP origin as ASN 61317, though route stability was recorded as false. No active threat indicators or evidence of malicious activity were observed.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | IPXO Incident Response Team |
| ASN | AS61317 |
| Network Name | 102.165.52.0 - 102.165.55.255 |
| CIDR Block | 102.165.52.0/22 |
| RIR | AFRINIC |
| Country | ZA |
| 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 | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Unknown |
| Service Purpose | Single-Service Host |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| Closed Ports | 22, 25, 443, 3389, 8080, 8443 (1 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS61317 |
| Network Prefix | 102.165.52.0/22 |
| Route mapping | Found |
| HSTS | Not detected |
| CSP | Not detected |
| HTTP/2 | Not detected |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 41% | 2 | 7 |
| routing | 8% | 1 | 1 |
| services | 32% | 2 | 3 |
| ownership | 28% | 2 | 2 |
| reputation | 20% | 1 | 3 |
| geolocation | 25% | 2 | 3 |
| Overall | 25% | 10 | 19 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-19 05:57:53 UTC |
| Last Seen | 2026-09-05 18:55:08 UTC |
| Profile Built | 2026-09-06 21:01:47 UTC |
| Data Freshness | Live |
| Signal Types | 19 |
| Total Observations | 28 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 102.165.53.82
Who owns the IP address 102.165.53.82?
102.165.53.82 is registered to IPXO Incident Response Team. The address falls within the 102.165.52.0/22 network block. Registration is held at AFRINIC.
Where is 102.165.53.82 located?
Geolocation data places 102.165.53.82 in Frankfurt. The local time zone is Africa/Johannesburg. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 102.165.53.82 malicious or safe?
102.165.53.82 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 102.165.53.82?
Responsive ports observed on 102.165.53.82 include 80. Port visibility reflects the most recent scan and may change as the host's configuration or firewall rules change.