IPDebrief

54.39.6.206

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

Date: 2026-06-11

---

**1. Core Profile**

---

**2. Threat & Behavior**

- Consistent geolocation and DNS records since June 2026.

- No spikes in threat activity or network anomalies.

---

**3. Relationships & Context**

- Same OVH network (`OVH-CUST-281059680`).

- DNS association with `proxy-ca001-san206.ahrefs.net` (Ahrefs proxy).

- 140 active IPs in the subnet, 126 flagged as high-risk.

- 21 low-risk, 79 medium-risk IPs.

---

**4. Actionable Insights**

- Monitor the subnet for lateral movement or increased risk.

- Consider blocking the IP if it starts showing open ports or suspicious DNS behavior.

- Use the provided firewall rules for immediate isolation.

---

**5. Security Actions**

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

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

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

---

Next Steps:

Threat Level: Low to Moderate (subnetwork risk > individual IP risk).

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

🌐 DNS Intelligence

PTRproxy-ca001-san206.ahrefs.net
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesproxy-ca001-san206.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
32%
24
routing
8%
11
services
15%
22
ownership
19%
22
reputation
32%
13
geolocation
27%
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-25 18:48:27 UTC
Last Seen2026-06-29 02:12:52 UTC
Profile Built2026-06-29 08:15:29 UTC
Data FreshnessLive
Signal Types21
Total Observations23
πŸ” 21 signal types Β· 23 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.