49.173.65.19
IP Intelligence Dossier
Your IP: 216.73.216.123
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
Narrative
The IP address 49.173.65.19 is located in Seoul, South Korea, and presents no significant risk indicators. It is classified as having an unknown infrastructure type with minimal data available for classification.
Classification Tags
Signal Summary Table
| Category | Finding | Confidence |
|---|---|---|
| Geolocation | Seoul, South Korea | 20% |
| Ownership | Unknown | 0% |
| Infrastructure | Unknown | 0% |
| Threat Lists | Not listed | 0% |
| Open Ports | Firewalled / No Services | 0% |
| Risk Score | 0 (Very Low) | 11.25% |
| TLS | None | 0% |
| PTR | None | 0% |
| FCrDNS | None | 0% |
| BGP | Unknown | 0% |
Notable Findings
- ✅ Clear: No significant risk indicators present.
- ℹ️ Info: The IP is located in Seoul, South Korea, with minimal data available for infrastructure classification.
- ❓ Unknown: Ownership and infrastructure type are unknown.
Recommended Actions
Allow with monitoring — no significant risk indicators detected, but limited data available for full classification.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | IP Manager |
| ASN | AS17858 |
| Network Name | — |
| CIDR Block | 49.168.0.0/13 |
| 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 | Tier 3 — Basic operator with some routing infrastructure |
🔌 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
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 | 26% | 2 | 4 |
| routing | 32% | 4 | 5 |
| services | 12% | 2 | 2 |
| ownership | 27% | 2 | 3 |
| reputation | 23% | 1 | 3 |
| geolocation | 27% | 2 | 3 |
| Overall | 24% | 13 | 20 |
Coverage: 6/6 dimensions · Data sufficiency: sufficient
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (65%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-07 23:04:24 UTC |
| Last Seen | 2026-06-26 18:11:24 UTC |
| Profile Built | 2026-06-26 18:20:59 UTC |
| Data Freshness | Live |
| Signal Types | 28 |
| Total Observations | 29 |
🔍 28 signal types · 29 observations collected
This report is generated from 28+ 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.