IPDebrief

167.114.139.54

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

Date: 2026-06-14

---

**1. Core Profile**

- ASN: 16276 (OVH)

- Organization: Dmytro, Ahrefs Pte Ltd

- Subnet: 167.114.139.0/24

- Country: Canada (QC, Montreal)

- Geo Plausibility: False (RTT anomalies suggest geolocation inconsistency)

- Hosting provider (OVH)

- Subnet classified as high_abuse (abuse density: 0.7422)

- No open ports, no TLS certificates, no HTTP services

---

**2. Threat Indicators**

---

**3. Observation History**

- DNS resolution for `ahrefs.net` (CAA records validated).

- Subnet abuse density increased to 0.7422 (from 0.6403 in June 2026).

- Network classified as "high_abuse" with 190 threat siblings.

---

**4. Relationships**

- Subnet: `167.114.139.0/24` (OVH-CUST-281059679)

- Organization: Ahrefs Pte Ltd (OVH customer)

---

**5. Neighborhood Analysis**

- Total IPs: 256 (167.114.139.0/24)

- Active IPs: 207

- Threat IPs: 190 (74.22% abuse density)

- High-risk subnet with significant inherited risk.

- Siblings show mixed activity, but no direct malicious signals.

---

**6. Recommendations**

1. Monitor Subnet Traffic:

- Focus on 167.114.139.0/24 for unusual outbound connections or data exfiltration patterns.

2. Validate Geolocation:

- Investigate RTT anomalies (26ms vs. expected 112ms for 5,597km) to confirm IP legitimacy.

3. Check Ahrefs Infrastructure:

- Confirm if Ahrefs is using OVH infrastructure for legitimate services or potential abuse.

4. Implement Network Segmentation:

- Isolate high-risk subnets to limit lateral movement if compromised.

---

Conclusion:

167.114.139.54 is part of a high-abuse subnet managed by OVH, associated with Ahrefs. While no direct malicious activity is observed, the subnet’s risk profile warrants closer scrutiny. SOC teams should prioritize monitoring this subnet for anomalous behavior and validate geolocation inconsistencies.

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

🌍 Geolocation

CountryπŸ‡¨πŸ‡¦ Canada
RegionQC
CityMontreal
Timezoneβ€”
Latitude45.51
Longitude-73.58

🏒 Ownership & Registration

OrganizationDmytro, Ahrefs Pte Ltd
ASNAS16276
Network NameOVH-CUST-281059679
CIDR Block167.114.139.0/24
RIRARIN
CountrySingapore
Abuse Contactβ€”

🌐 DNS Intelligence

PTRproxy-ca000-san54.ahrefs.net
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesproxy-ca000-san54.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
29%
24
routing
13%
11
services
15%
22
ownership
15%
22
reputation
28%
13
geolocation
33%
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-12 21:54:10 UTC
Last Seen2026-06-27 22:01:58 UTC
Profile Built2026-06-28 16:07:29 UTC
Data FreshnessLive
Signal Types21
Total Observations24
πŸ” 21 signal types Β· 24 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.