IPDebrief

54.39.136.183

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

Date: 2026-06-14

---

**1. Core Profile**

---

**2. Observation History**

- Single observation (low confidence) indicating potential geolocation in Canada.

- RTT anomalies (27ms vs. expected 112.6ms for 5629km distance), suggesting possible misattribution or synthetic data.

---

**3. Relationships**

- DNS: Resolves to `proxy-ca002-san183.ahrefs.net` (owned by Ahrefs).

- TLS/HTTP: No open ports or active services detected.

---

**4. Subnet Analysis**

- 100 active IPs in subnet (2 medium-risk, 98 low-risk).

- 115 IPs flagged for abuse (potential lateral movement or compromised hosts).

---

**5. Actionable Insights**

---

Conclusion: 54.39.136.183 is a legitimate OVH-hosted cloud instance with no direct malicious activity. However, its subnet’s elevated abuse density warrants closer monitoring for potential关联 risks.

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

🌍 Geolocation

CountryπŸ‡¨πŸ‡¦ Canada
RegionQC
CityBeauharnois
Timezoneβ€”
Latitude45.32
Longitude-73.87

🏒 Ownership & Registration

OrganizationDmytro, Ahrefs Pte Ltd
ASNAS16276
Network NameOVH-CUST-281059681
CIDR Block54.39.136.0/24
RIRARIN
CountrySingapore
Abuse Contactβ€”

🌐 DNS Intelligence

PTRproxy-ca002-san183.ahrefs.net
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesproxy-ca002-san183.ahrefs.net

πŸ” DNS Hygiene

Hygiene Score40% (Fair)
SPFNot configured
DMARCNot configured
FCrDNSNot verified
DNSSECValid
CAAPresent

☁️ 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
31%
24
routing
13%
11
services
15%
22
ownership
15%
22
reputation
28%
13
geolocation
32%
23
Overall22%1015
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceMostly Consistent (80%) β€” 1 contradiction(s)
AttributionLow (35%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid
⚠ Claimed geolocation contradicts RTT physics measurement

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-07 23:04:28 UTC
Last Seen2026-06-27 08:09:15 UTC
Profile Built2026-06-28 02:15:49 UTC
Data FreshnessLive
Signal Types21
Total Observations26
πŸ” 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.
{ } 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.