IP Intelligence Briefing: 185.113.139.51
Date: 2026-06-17
---
**1. Core Profile**
- Risk Score: Moderate (65/100)
- Ownership: Hosted by hip-hosting (ASN 41745, RIPE) in Riga, Latvia (RU).
- Network Role: Colocation hosting infrastructure.
- Services:
- 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**
- No direct malicious activity: No known attacker, spam, or Tor exit node associations.
- DNS Listings:
- Listed in 3/8 DNSBLs (high/medium severity).
- Potential misconfigured DNS (PTR hostname: `undefined.hostname.localhost`).
- Historical Observations:
- Recent network classification as "clean" with no persistent malicious activity.
- No observed port scanning or abnormal traffic patterns.
---
**3. Network Relationships**
- Subnet: 185.113.139.0/24 (colocation hosting network).
- Neighbors:
- 1 sibling IP (185.113.139.84) with risk score 65 (same provider).
- Subnet abuse density: 0% (clean).
- Provider: No direct BGP anomalies; route stability flagged as "unstable."
---
**4. Actionable Insights**
- Monitor DNS Listings: Investigate DNSBL entries (e.g., Spamhaus, Barracuda) for potential abuse.
- Verify TLS Configuration: Validate the self-signed certificate and ensure proper SNI handling.
- Check Hosting Compliance: Confirm hip-hosting adheres to security best practices for colocation services.
- Network Segmentation: Consider isolating this subnet if it hosts sensitive assets.
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.
๐ข Ownership & Registration
| Organization | hip-hosting |
| ASN | AS41745 |
| Network Name | โ |
| CIDR Block | โ |
| RIR | RIPE |
| Country | โ |
| Abuse Contact | Available via RDAP |
๐ DNS Intelligence
| PTR | undefined.hostname.localhost |
| Forward Confirmed | No โ PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | undefined.hostname.localhost |
๐ 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 | Web Server |
| Network Tier | Unknown โ Insufficient routing data to classify |
๐ Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 443 | https | tcp | โ |
| 22 | ssh | tcp | |
| Closed Ports | 25, 80, 3389, 8080, 8443 (2 open / 7 scanned) | ||
| Server | gws |
| HTTP Title | โ |
| SSH Version | SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.14 |
๐ TLS Certificate
| SANs | None |
| Valid From | 2015-01-01T00:00:00+00:00 |
| Valid Until | 2030-01-01T00:00:00+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_256_GCM_SHA384 |
| Signature Algorithm | sha256RSA |
| Validity Period | 5479 days |
| Serial Number | 0090768918E93393A0 |
| Thumbprint | 4259517CD4E48A289D332AB3F0AB52A366322824 |
๐ฏ Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 35% | 2 | 3 |
| routing | 13% | 1 | 1 |
| services | 30% | 2 | 3 |
| ownership | 26% | 2 | 3 |
| reputation | 28% | 1 | 3 |
| geolocation | 21% | 2 | 2 |
| Overall | 26% | 10 | 15 |
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
๐ Observation Timeline ๐ Fresh
| First Seen | 2026-05-07 23:04:00 UTC |
| Last Seen | 2026-06-26 18:10:53 UTC |
| Profile Built | 2026-06-25 23:38:06 UTC |
| Data Freshness | Fresh |
| Signal Types | 22 |
| Total Observations | 22 |
Full dossier details are available via our API.