IP Intelligence Briefing: 139.144.26.48
Date: 2026-06-01
---
**1. Core Profile**
- Risk Score: 25 (Low Risk)
- Ownership: Owned by Linode (ASN 63949), a cloud infrastructure provider.
- Geolocation: Registered to the U.S., but geoPlausible is false due to RTT anomalies (observed RTT: 37ms vs. expected minimum 143ms for 7165km).
- Network Role: CloudCompute infrastructure (hosting, no residential/mobile attributes).
- Threat Indicators: No malicious activity detected (no indicators, blacklists, or campaigns).
---
**2. Observational History**
- 17 observations over 30 days:
- Geolocation inconsistencies: Multiple entries show U.S. country code ("US") but inconsistent RTT/latency values.
- DNSBL listing: Detected in 1 of 8 DNSBL checks (low severity).
- Network stability: BGP route stability flagged as unstable (routeChanges30d: 0, but isRouteStable: false).
- No persistent threats: ThreatObservationCount = 0, no malicious persistence.
---
**3. Network Relationships**
- Linked entities:
- Linode network (same ASN/organization).
- DNS hostname: `139-144-26-48.ip.linodeusercontent.com` (no malicious domain associations).
- No external connections: No subnets, certificates, or organizations tied to this IP.
---
**4. Subnet Neighborhood**
- Subnet: 139.144.26.48/24
- Neighbor data: No active/sibling IPs reported (neighborCount = 0).
- Abuse density: 0% (clean subnet).
---
**5. Key Anomalies**
- Geolocation mismatch: RTT values suggest a closer geographical location than the registered U.S. IP.
- DNSBL alert: Minor listing in 1 of 8 DNSBL checks (low risk).
- BGP instability: Route stability flags may indicate misconfiguration or network churn.
---
**6. Recommendations**
- Monitor geolocation consistency: Investigate RTT anomalies to rule out spoofing or misconfigured routing.
- Review DNSBL context: Check if the DNSBL listing is false positive or tied to Linodeβs infrastructure.
- Validate BGP stability: Confirm route stability with Linodeβs network team if critical services rely on this IP.
Conclusion: This IP is a low-risk Linode cloud instance with no direct malicious activity. However, geolocation inconsistencies and minor DNSBL alerts warrant further scrutiny for potential misconfigurations or spoofing.
---
*Generated by IPDebrief threat intelligence platform.*
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | Linode |
| ASN | AS63949 |
| Network Name | LINODE |
| CIDR Block | 139.144.0.0/16 |
| RIR | ARIN |
| Country | United States |
| Abuse Contact | Available via RDAP |
π DNS Intelligence
| PTR | 139-144-26-48.ip.linodeusercontent.com |
| Forward Confirmed | Yes β FCrDNS verified |
| Forward Hostnames | 139-144-26-48.ip.linodeusercontent.com |
π DNS Hygiene
| Hygiene Score | 40% (Fair) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Verified |
| DNSSEC | Valid |
| CAA | Not configured |
βοΈ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| 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 | |||
| Server | β |
| HTTP Title | β |
π 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 | 27% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 13% | 1 | 2 |
| ownership | 27% | 2 | 3 |
| reputation | 22% | 1 | 3 |
| geolocation | 27% | 2 | 3 |
| Overall | 22% | 9 | 15 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (70%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-30 17:01:19 UTC |
| Last Seen | 2026-06-29 07:50:54 UTC |
| Profile Built | 2026-06-29 07:54:28 UTC |
| Data Freshness | Live |
| Signal Types | 20 |
| Total Observations | 21 |
Full dossier details are available via our API.