IPDebrief

139.162.185.35

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: 139.162.185.35

Date: 2026-06-06

---

**1. Profile Summary**

---

**2. Observation History**

- BGP prefix: `139.162.160.0/19` (Akamai/Linode).

- DNSSEC valid, no CAA records.

- No DNSBL listings detected.

- No malicious campaigns, spam, or attacker activity.

- No TLS certificates or HTTP security headers (HSTS, CSP).

---

**3. Relationships**

---

**4. Neighborhood Analysis**

---

**5. Recommendations**

---

Conclusion:

139.162.185.35 is a legitimate Linode cloud host with no detected threats. It hosts a basic HTTP service and aligns with Linode’s infrastructure. No immediate action is required, but ongoing monitoring is advised for anomalies.

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

🌍 Geolocation

CountryπŸ‡ΊπŸ‡Έ United States
RegionHesse
CityFrankfurt am Main
Timezoneβ€”
Latitude50.12
Longitude8.68

🏒 Ownership & Registration

Organizationlinode-mnt
ASNAS63949
Network Nameβ€”
CIDR Block139.162.160.0/19
RIRARIN
Countryβ€”
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR139-162-185-35.ip.linodeusercontent.com
Forward ConfirmedYes β€” FCrDNS verified
Forward Hostnames139-162-185-35.ip.linodeusercontent.com

πŸ” DNS Hygiene

Hygiene Score40% (Fair)
SPFNot configured
DMARCNot configured
FCrDNSVerified
DNSSECValid
CAANot configured

☁️ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeWeb Server
Network TierHosting β€” Infrastructure provider without advanced routing
CloudHosting

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
80httptcpβ€”
443httpstcpβ€”
22sshtcp
8080http-alttcpβ€”
8443https-alttcpβ€”
Closed Ports25, 3389 (5 open / 7 scanned)
Servergws
HTTP Titleβ€”
SSH VersionSSH-2.0-OpenSSH_8.9p1

πŸ” TLS Certificate

A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
⚠️
CN=invalid2.invalid, OU=No SNI provided - please fix your client.
Issued by CN=invalid2.invalid, OU=No SNI provided - please fix your client.
Self-signed: Yes
SANsinvalid2.invalid
Valid From2026-06-08T09:42:35+00:00
Valid Until2026-08-31T09:42:34+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_128_GCM_SHA256
Signature Algorithmsha256RSA
Validity Period83 days
Serial Number1A8AF808235843B55FF6CFDBE2D8E032
ThumbprintDB303E723408FD4455382EBFE1F7C765E57B0133

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
20%
24
routing
27%
23
services
26%
23
ownership
35%
36
reputation
24%
13
geolocation
23%
22
Overall26%1221
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (70%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-13 00:02:55 UTC
Last Seen2026-06-27 22:17:15 UTC
Profile Built2026-06-28 22:22:34 UTC
Data FreshnessLive
Signal Types24
Total Observations31
πŸ” 24 signal types Β· 31 observations collected
This report is generated from 24+ 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.