138.124.123.62
IP Intelligence Briefing: 138.124.123.62
*Last Updated: 2026-06-08*
---
**1. Core Profile**
- Risk Score: 0 (Low Risk)
- Provider Score: 0 | Authority Score: 0 | Stability Score: 0
- Geolocation:
- Country: United States (US) | City: Charlotte | Region: NC
- Coordinates: 35.23°N, -80.84°E | Timezone: America/New_York
- Ownership:
- ASN: Unassigned | Organization: "Abuse contact role object" (ARIN registry)
- Abuse Contact: Available via RDAP | Subnet: 138.124.123.0/24
---
**2. Threat Indicators**
- No Malicious Activity: No indicators of compromise (IOC), spam, or known attacker associations.
- Network Role: Firewalled / No Services | Cloud/Hosting: Not detected.
- DNS Configuration:
- No PTR records | No active domains | DNS resolution errors observed (likely misconfigured resolver).
---
**3. Observation History**
- Recent Activity (30 Days):
- Minimal Risk: Consistent low-risk signals (0.2174 operator score).
- Stability: No significant changes in geolocation or network behavior.
- Threat Persistence: No persistent malicious activity detected.
---
**4. Relationships & Network Context**
- Linked Entities:
- Network: Netcrafters-OU (same /24 subnet).
- DNS Associations: Failed to resolve hostnames (likely private resolver or misconfigured DNS).
- Subnet Analysis:
- Abuse Density: 0% | Active Siblings: 1 (138.124.123.129, risk unknown).
- Neighbor Risk: No high/medium risk IPs in subnet.
---
**5. Actionable Insights**
- Monitor DNS Configuration: Investigate recurring DNS resolution failures (e.g., 192.168.2.108).
- Validate Subnet Security: Confirm 138.124.123.129’s legitimacy, as it lacks risk data.
- Maintain Current Controls: No immediate mitigation needed due to low risk, but ensure firewall rules align with network role.
---
Conclusion: This IP appears benign with no malicious activity detected. Focus on resolving DNS issues and verifying subnet neighbor integrity. No urgent action required.
*Generated by IPDebrief Threat Intelligence Platform.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Abuse contact role object |
| ASN | AS203273 |
| Network Name | — |
| CIDR Block | — |
| RIR | ARIN |
| Country | — |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR | mightymoccasin.ptr.network |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | mightymoccasin.ptr.network |
🔐 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 | Single-Service Host |
| Network Tier | Unknown — Insufficient routing data to classify |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 22 | ssh | tcp | |
| Closed Ports | 25, 80, 443, 3389, 8080, 8443 (1 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
| SSH Version | SSH-2.0-OpenSSH_10.2p1 Ubuntu-2ubuntu3.2 |
🔐 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 | 13% | 1 | 1 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 1 |
| ownership | 27% | 2 | 3 |
| reputation | 13% | 1 | 2 |
| geolocation | 13% | 1 | 1 |
| Overall | 16% | 7 | 9 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-16 20:59:32 UTC |
| Last Seen | 2026-06-08 01:08:57 UTC |
| Profile Built | 2026-06-08 01:38:49 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 22 |
Full dossier details are available via our API.