IPDebrief

14.51.223.135

IP Intelligence Dossier
Your IP: 216.73.216.123
{ } JSON πŸ”§ Full Actions API
πŸ€– Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.

IP Intelligence Briefing: 14.51.223.135

Date: 2026-06-02

---

**1. Risk Profile**

---

**2. Network & Mobile Carrier**

- High Risk (80): 14.51.223.142

- Medium Risk (40–55): 14.51.223.137, 14.51.223.152, 14.51.223.173, etc.

- Low Risk (0): Majority of siblings.

---

**3. Historical Observations (Last 30 Days)**

- Geolocation inferred via multi-signal consensus.

- Control plane stability: DNSSEC valid, but route stability flagged.

- 2 DNSBL listings (out of 8 total lists).

---

**4. Relationships & Threat Context**

---

**5. Actionable Recommendations**

1. Monitor Neighbors: Focus on high-risk neighbors (e.g., 14.51.223.142) for potential lateral movement or关联.

2. Check Route Stability: Investigate route instability (BGP prefix 14.48.0.0/13) and DNSBL listings.

3. Block High-Risk Subnet: Consider firewall rules to restrict traffic from 14.51.223.0/24 if suspicious activity is detected.

4. Verify Ownership: Confirm KT Corporation’s compliance with IP abuse policies, given the subnet’s moderate abuse density.

---

Note: No immediate mitigation required for the IP itself, but contextualize within the subnet’s risk profile.

This summary was generated by AI and may contain inaccuracies. Verify critical details independently.

🌍 Geolocation

CountryπŸ‡°πŸ‡· South Korea
RegionNorth Chungcheong
CityChungju
TimezoneAsia/Seoul
Latitude35.91
Longitude127.77

🏒 Ownership & Registration

OrganizationIP Manager
ASNAS4766
Network Nameβ€”
CIDR Blockβ€”
RIRAPNIC
Countryβ€”
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)

πŸ” DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

☁️ Network Classification

InfrastructureMobile
Service PurposeFirewalled / No Services
Network TierUnknown β€” Insufficient routing data to classify
Mobile

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Serverβ€”
HTTP Titleβ€”

πŸ” TLS Certificate

πŸ”’
No certificate
Issued by β€”
N/A
SANsNone
Valid Fromβ€”
Valid Untilβ€”

🎯 Confidence Breakdown

Per-dimension confidence scores based on source diversity and data freshness

DimensionScoreSourcesObservations
threat
32%
23
routing
13%
11
services
8%
11
ownership
26%
23
reputation
28%
13
geolocation
21%
22
Overall21%913
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-07 23:03:41 UTC
Last Seen2026-06-22 14:54:57 UTC
Profile Built2026-06-22 14:57:20 UTC
Data FreshnessLive
Signal Types16
Total Observations17
πŸ” 16 signal types Β· 17 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.
{ } JSON API πŸ”§ Actions API πŸ“§ Enterprise Access

ℹ️ 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.