IPDebrief

167.114.139.21

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.21/32

Date: 2026-06-13

---

**1. Risk Profile**

---

**2. Observation History**

- Subnet abuse density: 0.7344 (High Abuse).

- Inherited risk: 29 (from subnet).

- Threat siblings: 188/256 IPs in the /24 subnet are flagged as threats.

---

**3. Relationships & Network Context**

- DNS: `proxy-ca000-san21.ahrefs.net` (Ahrefs Pte Ltd).

- Subnet: `167.114.139.0/24` (OVH customer network).

- Abuse Density: 73.44% (High Abuse).

- Active Siblings: 204 IPs (188 flagged as threats).

- Risk Inheritance: 29% risk score from subnet.

---

**4. Neighborhood Data**

- High Risk: 0 IPs

- Medium Risk: 99 IPs

- Low Risk: 1 IP

- `167.114.139.0` (Risk Score 40)

- `167.114.139.1` (Risk Score 40)

- `167.114.139.2` (Risk Score 40)

---

**5. Recommended Actions**

- iptables: `iptables -A INPUT -s 167.114.139.21 -j DROP`

- Cloudflare WAF: Block IP with rule `ip.src eq 167.114.139.21`

- AWS WAF: Add `167.114.139.21/32` to a rule with description "IPDebrief risk 40".

- Monitor the `167.114.139.0/24` subnet for increased threat activity.

- Validate DNS records (`proxy-ca000-san21.ahrefs.net`) for potential spoofing.

---

Conclusion:

The IP is part of a high-abuse subnet linked to OVH and Ahrefs. While no direct malicious activity is detected, the subnet’s high threat density warrants cautious monitoring and network segmentation. Implement firewall rules to restrict traffic from this IP and investigate potential lateral movement risks.

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-san21.ahrefs.net
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesproxy-ca000-san21.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
28%
24
routing
13%
11
services
12%
22
ownership
19%
22
reputation
30%
13
geolocation
35%
23
Overall23%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:03:51 UTC
Last Seen2026-06-27 01:27:49 UTC
Profile Built2026-06-28 00:40:02 UTC
Data FreshnessLive
Signal Types22
Total Observations29
πŸ” 22 signal types Β· 29 observations collected
This report is generated from 22+ 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.