IPDebrief

183.109.153.175

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: 183.109.153.175/32

*Generated via IPDebrief Analysis*

---

**Risk Profile**

---

**Observation History**

- DNSSEC validation confirmed (score 0.15).

- BGP prefix stability: 14 observations over 30 days (route stability: false).

- No persistent threat signals or abuse reports.

---

**Network Relationships**

- Same network: KORNET-KR (APNIC, Korea Telecom).

- Subnet siblings: 2 IPs with risk scores of 80.

- BGP origin ASN: 4766 (KIXS-AS-KR).

- DNSSEC valid, but 4/8 DNSBL lists flagged.

---

**Neighbor Analysis**

- 183.109.153.173: Risk 80, Authority 50.

- 183.109.153.176: Risk 80, Authority 50.

---

**Recommended Actions**

1. Monitor Neighbors: Investigate high-risk siblings (173, 176) for potential关联.

2. Verify Geolocation: Confirm if the US geolocation is accurate or a mobile carrier misattribution.

3. Block Subnet: Consider firewall rules to restrict traffic from 183.109.153.0/24 due to high abuse density.

4. Check DNSBL Status: Validate if the IP is listed on any DNSBLs (4/8 flagged).

---

*End of Briefing*

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

🌍 Geolocation

CountryπŸ‡°πŸ‡· South Korea
RegionJeollabuk-do
CityGimje-si
TimezoneAsia/Seoul
Latitude35.91
Longitude127.77

🏒 Ownership & Registration

OrganizationIP Manager
ASNAS4766
Network NameKORNET-KR
CIDR Block183.96.0.0/11
RIRAPNIC
CountryKR
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
27%
23
routing
13%
11
services
8%
11
ownership
27%
23
reputation
22%
13
geolocation
19%
22
Overall19%913
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Fresh

First Seen2026-05-24 18:40:25 UTC
Last Seen2026-06-26 18:10:53 UTC
Profile Built2026-06-26 05:44:49 UTC
Data FreshnessFresh
Signal Types17
Total Observations17
πŸ” 17 signal types Β· 17 observations collected
This report is generated from 17+ 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.