159.203.136.205
IP Intelligence Dossier
Your IP: 216.73.216.123
🤖 Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 159.203.136.205
Date: 2026-06-12
---
**1. Profile Summary**
- Risk Score: Moderate (50/100)
- Provider: DigitalOcean (ASN 14061)
- Geolocation: Clifton, NJ, US
- Network Role: Cloud Compute (Virtual Machine)
- Services: HTTP/HTTPS (port 80/443) with a TLS certificate issued to "TRAEFIK DEFAULT CERT."
- Threat Indicators: No malicious activity detected; no blacklists, spam, or known attacker associations.
---
**2. Observation History**
- Recent Activity:
- HTTP/HTTPS traffic observed with TLSv1.3 (AES-128-GCM).
- 404 HTTP status code returned, suggesting a misconfigured or non-responsive service.
- DNSSEC validation passed, but no email authentication (SPF/DKIM) detected.
- Trend: No significant changes in risk or threat signals over the past 30 days.
---
**3. Relationships & Network Context**
- Network: Part of DigitalOcean’s 159.203.0.0/20 subnet.
- Subnet Abuse Density: 0% (clean).
- Neighbors: No sibling IPs listed in the /24 subnet (159.203.136.0/24).
- Certificates: TLS certificate includes SANs linked to containerized services (e.g., Traefik).
---
**4. Threat & Risk Analysis**
- No Direct Threats: No malware, C2 activity, or IOC matches.
- Moderate Risk Factors:
- Self-signed certificate with potential misconfigurations.
- HTTP 404 responses may indicate a compromised or abandoned service.
- Recommendation: Validate the TLS certificate’s legitimacy and ensure the service is properly configured.
---
**5. Actionable Steps**
- Monitor: Track HTTP/HTTPS traffic for unexpected behavior or new threats.
- Validate: Verify the TLS certificate’s validity and SANs to confirm it’s not impersonating a legitimate service.
- Check Subnet: Ensure no other IPs in the 159.203.136.0/24 subnet show suspicious activity.
---
Source: IPDebrief Threat Intelligence Platform
Note: This IP is associated with a legitimate cloud provider but requires further validation of its service configuration.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | DigitalOcean, LLC |
| ASN | AS14061 |
| Network Name | — |
| CIDR Block | — |
| RIR | ARIN |
| Country | — |
| Abuse Contact | Available via RDAP |
🌐 DNS Intelligence
| PTR Record | No PTR |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
🔐 DNS Hygiene
| Hygiene Score | 20% (Poor) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Not configured |
☁️ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Web Server |
| Network Tier | Hosting — Infrastructure provider without advanced routing |
🔌 Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| 80 | http | tcp | — |
| 443 | https | tcp | — |
| 22 | ssh | tcp | |
| Closed Ports | 25, 3389, 8080, 8443 (3 open / 7 scanned) | ||
| Server | — |
| HTTP Title | — |
| SSH Version | SSH-2.0-OpenSSH_10.0p2 Ubuntu-5ubuntu5.4 |
🔐 TLS Certificate
A self-signed certificate was detected. This is common for development servers, internal services, or IoT devices.
CN=TRAEFIK DEFAULT CERT
Issued by CN=TRAEFIK DEFAULT CERT
Self-signed: Yes
| SANs | f094d816c685c6537367904e80e368df.d6f6f26fc872b3f678339c2418c094ce.traefik.default |
| Valid From | 2026-06-12T10:59:53+00:00 |
| Valid Until | 2027-06-12T10:59:53+00:00 |
| TLS Protocol | Tls13 |
| Cipher Suite | TLS_AES_128_GCM_SHA256 |
| Signature Algorithm | sha256RSA |
| Validity Period | 365 days |
| Serial Number | 0C2798BBB7172D63944288430EECA814 |
| Thumbprint | DE40BA6DB0C8A5EE54216F72D0E4B78F915C70EE |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 27% | 2 | 4 |
| routing | 8% | 1 | 1 |
| services | 28% | 2 | 3 |
| ownership | 20% | 2 | 3 |
| reputation | 26% | 1 | 3 |
| geolocation | 35% | 2 | 3 |
| Overall | 24% | 10 | 17 |
Coverage: 6/6 dimensions · Data sufficiency: sufficient
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
⚠ Claimed geolocation contradicts RTT physics measurement
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-07 23:03:49 UTC |
| Last Seen | 2026-06-27 00:54:26 UTC |
| Profile Built | 2026-06-27 21:07:19 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 26 |
🔍 21 signal types · 26 observations collected
This report is generated from 21+ 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.
Full dossier details are available via our API.
ℹ️ 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.