IPDebrief

185.113.139.51

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

Date: 2026-06-17

---

**1. Core Profile**

- Open ports: 443/HTTPS, 22/SSH (SSH banner: OpenSSH 8.9p1).

- TLS certificate: Self-signed, issued to `invalid2.invalid` (likely misconfigured).

- HTTP server: Google Workspace (gws) redirecting to 301.

---

**2. Threat Indicators**

- Listed in 3/8 DNSBLs (high/medium severity).

- Potential misconfigured DNS (PTR hostname: `undefined.hostname.localhost`).

- Recent network classification as "clean" with no persistent malicious activity.

- No observed port scanning or abnormal traffic patterns.

---

**3. Network Relationships**

- 1 sibling IP (185.113.139.84) with risk score 65 (same provider).

- Subnet abuse density: 0% (clean).

---

**4. Actionable Insights**

Conclusion: This IP appears to be a legitimate hosting node with moderate risk, primarily due to misconfigured DNS and potential oversight in TLS practices. No immediate mitigation is required, but ongoing monitoring is advised.

---

*Generated by IPDebrief for SOC analysts. All data sourced from IPDebrief intelligence feeds.*

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

๐ŸŒ Geolocation

Country๐Ÿ‡ท๐Ÿ‡บ Russia
RegionPA
CityPhiladelphia
Timezoneโ€”
Latitude56.95
Longitude24.10

๐Ÿข Ownership & Registration

Organizationhip-hosting
ASNAS41745
Network Nameโ€”
CIDR Blockโ€”
RIRRIPE
Countryโ€”
Abuse ContactAvailable via RDAP

๐ŸŒ DNS Intelligence

PTRundefined.hostname.localhost
Forward ConfirmedNo โ€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesundefined.hostname.localhost

๐Ÿ” DNS Hygiene

Hygiene Score20% (Poor)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAANot configured

โ˜๏ธ Network Classification

InfrastructureUnknown
Service PurposeWeb Server
Network TierUnknown โ€” Insufficient routing data to classify
No specific classification

๐Ÿ”Œ Services & Open Ports

PortServiceProtocolBanner
443httpstcpโ€”
22sshtcp
Closed Ports25, 80, 3389, 8080, 8443 (2 open / 7 scanned)
Servergws
HTTP Titleโ€”
SSH VersionSSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.14

๐Ÿ” 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
SANsNone
Valid From2015-01-01T00:00:00+00:00
Valid Until2030-01-01T00:00:00+00:00
TLS ProtocolTls13
Cipher SuiteTLS_AES_256_GCM_SHA384
Signature Algorithmsha256RSA
Validity Period5479 days
Serial Number0090768918E93393A0
Thumbprint4259517CD4E48A289D332AB3F0AB52A366322824

๐ŸŽฏ Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
35%
23
routing
13%
11
services
30%
23
ownership
26%
23
reputation
28%
13
geolocation
21%
22
Overall26%1015
Coverage: 6/6 dimensions ยท Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

๐Ÿ“… Observation Timeline ๐Ÿ”„ Fresh

First Seen2026-05-07 23:04:00 UTC
Last Seen2026-06-26 18:10:53 UTC
Profile Built2026-06-25 23:38:06 UTC
Data FreshnessFresh
Signal Types22
Total Observations22
๐Ÿ” 22 signal types ยท 22 observations collected
This report is generated from 22+ 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.