182.31.35.187
IP Threat Intelligence Briefing: 182.31.35.187
Date: 2026-06-17
---
**1. Core Profile**
- Risk Score: 80 (High Risk)
- Ownership: Registered to *IP Manager* (AS9694) in South Korea (KR).
- Geolocation: Jinju, South Korea (35.91°N, 127.77°E).
- Network Role: Firewalled / No Services (no open ports or TLS certs detected).
- Threat Indicators:
- DNSBL listings (5/8 total).
- Minimal reputation with no known campaigns or malware indicators.
- BGP route stability issues (route changes in last 30 days).
---
**2. Observation History**
- Recent Activity (Last 30 Days):
- 19 observations, with confidence scores ranging from 0.21 to 0.90.
- Notable anomalies:
- DNSSEC validation issues.
- Routing inconsistencies (AS9694).
- High RTT (210ms) with plausible geolocation.
- No persistent malicious behavior detected.
---
**3. Network Relationships**
- Subnet: 182.31.35.187/24.
- Key Relationships:
- Linked to *SCSNET-KR* (local ISP/organization).
- Neighboring IPs:
- 182.31.35.115 (risk score 80, high-risk neighbor).
- Subnet Abuse Density: 1 (high risk).
---
**4. Threat Context**
- DNSBL Listings: Appears in 5/8 DNSBLs (e.g., Spamhaus, OpenBL).
- BGP Behavior: Unstable route (route changes detected).
- Geolocation Consistency: RTT matches South Korea (8788km distance).
---
**5. Recommendations**
1. Monitor Subnet: High-risk subnet (182.31.35.0/24) with abuse density 1.
2. Block IP: Consider blocking based on DNSBL listings and high risk score.
3. Investigate Network: Review SCSNET-KR for potential compromised infrastructure.
4. Check Neighbors: 182.31.35.115 shares similar risk profile.
---
Source: IPDebrief Threat Intelligence Platform
Note: This IP shows no direct malware indicators but warrants monitoring due to DNSBL associations and network anomalies.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | IP Manager |
| ASN | AS9694 |
| Network Name | — |
| CIDR Block | — |
| RIR | APNIC |
| Country | — |
| Abuse Contact | Available via RDAP |
🌐 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 | Firewalled / No Services |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Server | — |
| HTTP Title | — |
🔐 TLS Certificate
| SANs | None |
| Valid From | — |
| Valid Until | — |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 24% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 8% | 1 | 1 |
| ownership | 27% | 2 | 3 |
| reputation | 21% | 1 | 3 |
| geolocation | 30% | 2 | 3 |
| Overall | 20% | 9 | 14 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-07 23:03:58 UTC |
| Last Seen | 2026-06-26 02:15:05 UTC |
| Profile Built | 2026-06-22 23:32:14 UTC |
| Data Freshness | Live |
| Signal Types | 17 |
| Total Observations | 19 |
Full dossier details are available via our API.