86.108.70.106 is an IPv4 address operated by GO-JOR (AS8376), geolocated to New York, United States. Its reverse DNS name is 86.108.x.106.go.com.jo. As of August 30, 2026, IPDebrief rates it Low Risk (25/100); no anonymizing service was detected.
# IP Intelligence Briefing: 86.108.70.106/32
## Executive Summary
IP 86.108.70.106 was classified as Low Risk (Risk Score: 25) during analysis. The address belongs to Jordan Data Communications Company LLC (GO-JOR), ASN 8376, though geolocation data indicated New York, US. The IP showed minimal threat activity with no known attacker indicators.
## Ownership and Infrastructure
The IP address is owned by Jordan Data Communications Company LLC (GO-JOR), ASN 8376, under the netname OR2-JOR2. Registration occurred via RIPE registry in 2005. The /24 subnet (86.108.70.0/24) contains 255 addresses. No cloud, CDN, VPN, or hosting infrastructure was detected. The network role was classified as "Firewalled / No Services" with no open ports discovered during scanning.
## Geolocation Assessment
Geolocation data showed conflicting signals: ASN registration indicated Jordan, while geolocation consensus placed the IP in New York, US. This discrepancy was flagged as geoConsensus: false. The address resolved to PTR hostname 86.108.x.106.go.com.jo under the com.jo domain. DNSSEC validation was confirmed as valid.
## Threat Indicators and Reputation
Threat assessment returned negative findings:
- Not identified as Tor exit node
- Not flagged as known attacker
- Not categorized as spam source
- Zero blacklist count
- Single DNSBL listing out of 8 total checks
- No associated threat campaigns or indicators
The IP showed no evidence of hosting malicious services or being used in known attack campaigns.
## Observation History
The IP generated 15 historical observations. Key signals included:
- ASN identification (AS8376, Jordan Data Communications Company LLC)
- DNS resolution for com.jo domain
- One recent blacklist listing with "high" severity noted on 2026-07-28
- DNSSEC validation signals
- No persistent threat activity observed
The threat persistence days remained at zero, indicating no sustained malicious behavior.
## Neighborhood Analysis
The /24 subnet (86.108.70.0/24) contained three neighbor IPs:
- 86.108.70.88: Risk Score 0, Authority Score 50
- 86.108.70.148: Risk Score 0, Authority Score 50
- 86.108.70.200: Risk Score 25, Authority Score 50
Subnet abuse density was rated at zero, with all neighbors classified as low risk.
## Relationship Graph
Three relationships were identified:
- Two Same Network links to OR2-JOR2 network
- One DNS Association to hostname 86.108.x.106.go.com.jo
## Recommended Actions
No specific firewall rules or mitigation actions were generated. The IP's low risk profile and absence of active threat indicators suggest standard monitoring is sufficient.
## Intelligence Conclusion
IP 86.108.70.106 presented a low-risk profile with no actionable threat indicators. The primary observation was a single blacklist listing that did not correlate with active malicious behavior. The geolocation discrepancy between ASN registration (Jordan) and geolocation consensus (US) warrants periodic re-validation but does not indicate compromise. Standard network monitoring is recommended.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | GO-JOR |
| ASN | AS8376 |
| Network Name | OR2-JOR2 |
| CIDR Block | 86.108.70.0/24 |
| RIR | RIPE |
| Country | JO |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | 86.108.x.106.go.com.jo |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | 86.108.x.106.go.com.jo |
🔐 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 | Firewalled / No Services |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🛡️ Public Network Snapshot
| Origin ASN | AS8376 |
| Network Prefix | 86.108.70.0/24 |
| Route mapping | Found |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 0% | 0 | 0 |
| routing | 0% | 0 | 0 |
| services | 0% | 0 | 0 |
| ownership | 25% | 1 | 2 |
| reputation | 0% | 0 | 0 |
| geolocation | 0% | 0 | 0 |
| Overall | 4% | 1 | 2 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-07-16 10:37:06 UTC |
| Last Seen | 2026-10-06 10:03:40 UTC |
| Profile Built | 2026-08-30 14:38:52 UTC |
| Data Freshness | Live |
| Signal Types | 22 |
| Total Observations | 23 |
Full dossier details are available via our API.
❓ Frequently Asked Questions About 86.108.70.106
Who owns the IP address 86.108.70.106?
86.108.70.106 is registered to GO-JOR. The address falls within the 86.108.70.0/24 network block. Registration is held at RIPE.
Where is 86.108.70.106 located?
Geolocation data places 86.108.70.106 in New York, US-NY, United States. The local time zone is America/New_York. IP geolocation is approximate and indicates the network's registered or routed location rather than a precise physical address.
Is 86.108.70.106 malicious or safe?
86.108.70.106 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 86.108.70.106?
The reverse DNS (PTR) record for 86.108.70.106 is 86.108.x.106.go.com.jo. This hostname is not forward-confirmed, so it should be treated as a weak signal.