IPDebrief

134.122.99.217

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

Date: 2026-06-12

---

**1. Core Profile**

- Primary: United Kingdom (England, Slough)

- Conflicting Observations: US (39.83°N, -98.58°W) noted in historical data.

- Listed in 2/8 DNSBLs (low-severity spam risk).

- No malware campaigns, Tor exit nodes, or known attackers.

---

**2. Observation History**

- Geolocation inferred as UK (Slough) with 35% confidence.

- No active services or TLS certificates detected.

- Scanned for open ports (no exposed services).

- DNSBL listings increased to 2 (from prior records).

---

**3. Relationships & Network**

- Part of DigitalOcean’s 134.122.0.0/17 subnet.

- No direct links to malicious organizations or subnets.

- 134.122.99.217/24 subnet: 0 abuse density, 0 threat siblings.

- No neighboring IPs detected (empty neighbor list).

---

**4. Threat & Risk Assessment**

- Conflicting geolocation data (UK vs. US).

- DNSBL listings (potential spam source).

- Monitor for geolocation anomalies or new DNSBL listings.

- Validate DNS and TLS records for spoofing attempts.

- No immediate mitigation required, but continuous monitoring advised.

---

Conclusion:

134.122.99.217 is a DigitalOcean-hosted IP with no direct malicious indicators. While it shows minor DNSBL associations and geolocation inconsistencies, it does not currently pose a significant threat. SOC teams should prioritize verifying geolocation accuracy and monitoring for emerging risks.

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

🌍 Geolocation

CountryπŸ‡¬πŸ‡§ United Kingdom
RegionENG
CityLondon
TimezoneEurope/London
Latitude51.52
Longitude-0.62

🏒 Ownership & Registration

OrganizationDigitalOcean, LLC
ASNAS14061
Network NameDIGITALOCEAN-134-122-0-0
CIDR Block134.122.0.0/17
RIRARIN
CountryUnited States
Abuse ContactAvailable via RDAP

🌐 DNS Intelligence

PTR RecordNo PTR
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)

πŸ” DNS Hygiene

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

☁️ Network Classification

InfrastructureInfrastructure / Datacenter
Service PurposeFirewalled / No Services
Network TierHosting β€” Infrastructure provider without advanced routing
CloudHosting

πŸ”Œ Services & Open Ports

PortServiceProtocolBanner
No open ports detected
Closed Ports22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned)
Serverβ€”
HTTP Titleβ€”

πŸ” TLS Certificate

πŸ”’
No certificate
Issued by β€”
N/A
SANsNone
Valid Fromβ€”
Valid Untilβ€”

🎯 Confidence Breakdown

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

DimensionScoreSourcesObservations
threat
27%
24
routing
13%
11
services
19%
22
ownership
27%
23
reputation
22%
13
geolocation
27%
23
Overall22%1016
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-30 10:57:53 UTC
Last Seen2026-06-29 07:27:25 UTC
Profile Built2026-06-29 07:28:45 UTC
Data FreshnessLive
Signal Types19
Total Observations22
πŸ” 19 signal types Β· 22 observations collected
This report is generated from 19+ 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.