220.80.66.168
IP Intelligence Dossier
Your IP: 216.73.216.123
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 220.80.66.168
Date: 2026-06-18
---
**1. Risk Profile**
- Risk Score: 80 (High Risk)
- Threat Indicators: 5 DNSBL listings (minimal severity), no direct malicious activity detected.
- Network Role: Mobile network (KT Corporation, LTE/5G).
- Geolocation: South Korea (Jeollabuk-do, Gimje-si), latitude 35.91, longitude 127.77.
---
**2. Ownership & Infrastructure**
- ASN: 4766 (IP Manager).
- Mobile Carrier: KT Corporation (MCC 450, MNC 08).
- Network Classification: Firewalled / No Services.
- Subnet: 220.80.66.168/24 (abuse density: 1/10, mostly clean).
---
**3. Threat Observations**
- DNSBL Listings: 5/8 DNSBL entries (e.g., Spamhaus, OpenDNS).
- Historical Activity:
- 1 observation (June 18, 2026) with 5 DNSBL hits.
- No persistent malicious activity or service exposure.
- Control Plane: DNSSEC valid, but DNSBL listings suggest potential spam or abuse.
---
**4. Relationships & Neighborhood**
- Network Relationships: Linked to "KORNET-KR" network (same subnet).
- Subnet Neighbors: 0 active IPs in 220.80.66.168/24 subnet.
- Subnet Abuse: Low risk (abuse density: 1/10).
---
**5. Recommendations**
- Monitor: Track DNSBL activity and correlate with other IPs in the subnet.
- Block: Consider blocking based on DNSBL listings if further activity is detected.
- Investigate: Verify if the mobile network (KT) has reported abuse or if the IP is part of a larger campaign.
Note: No active services or direct malicious indicators detected, but DNSBL associations warrant vigilance.
---
*Generated via IPDebrief threat intelligence analysis.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | IP Manager |
| ASN | AS4766 |
| 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 | Mobile |
| 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
No certificate
Issued by —
N/A
| SANs | None |
| Valid From | — |
| Valid Until | — |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 35% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 8% | 1 | 1 |
| ownership | 27% | 2 | 3 |
| reputation | 24% | 1 | 3 |
| geolocation | 21% | 2 | 2 |
| Overall | 21% | 9 | 13 |
Coverage: 6/6 dimensions · Data sufficiency: sufficient
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-07 23:04:13 UTC |
| Last Seen | 2026-06-26 18:11:10 UTC |
| Profile Built | 2026-06-23 08:36:51 UTC |
| Data Freshness | Live |
| Signal Types | 16 |
| Total Observations | 18 |
🔍 16 signal types · 18 observations collected
This report is generated from 16+ independent intelligence signals including
ownership records, DNS analysis, BGP routing, TLS certificates, port scanning, threat feeds,
behavioral fingerprinting, and more.
Full dossier details are available via our API.
Full dossier details are available via our API.
ℹ️ About This Report
All data shown is publicly available network metadata — IP addresses do not reliably identify individuals.
Assessments are probabilistic and should not be used as sole basis for access control decisions.
To report an issue or request data review, contact admin@ipdebrief.com.