IPDebrief

54.39.89.196

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.89.196

Date: 2026-06-05

---

**Risk Profile**

---

**Threat Indicators**

---

**Network & Hosting**

---

**Observation History**

---

**Actionable Recommendations**

1. Monitor Subnet: High abuse density in 54.39.89.0/24 suggests potential for lateral movement or compromised hosts.

2. Block IP: Implement firewall rules to block traffic from 54.39.89.196 if not required.

- Example:

```bash

iptables -A INPUT -s 54.39.89.196 -j DROP

nft add rule inet filter input ip saddr 54.39.89.196 drop

```

3. Verify DNS: Investigate `proxy-ca012-san196.ahrefs.net` for potential misconfigurations or abuse.

4. Check Hosting Provider: Confirm Ahrefs’ security practices for cloud instances.

---

Conclusion: While the IP itself shows no direct threats, its location in a high-abuse subnet warrants closer scrutiny. Monitor for unusual activity and validate the necessity of connectivity to this IP.

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-281059691
CIDR Block54.39.89.0/24
RIRARIN
CountrySingapore
Abuse Contactβ€”

🌐 DNS Intelligence

PTRproxy-ca012-san196.ahrefs.net
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesproxy-ca012-san196.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
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%
23
routing
13%
11
services
8%
11
ownership
19%
22
reputation
30%
13
geolocation
23%
22
Overall20%912
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
Data CoherenceConsistent (100%)
AttributionModerate (50%)
OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid

πŸ“… Observation Timeline πŸ”„ Live

First Seen2026-05-09 22:11:23 UTC
Last Seen2026-06-27 16:46:16 UTC
Profile Built2026-06-28 10:51:08 UTC
Data FreshnessLive
Signal Types18
Total Observations23
πŸ” 18 signal types Β· 23 observations collected
This report is generated from 18+ 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.