IPDebrief

54.39.203.58

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

Classification: Moderate Risk | Provider: OVH | Date: 2026-06-20

## Executive Summary

IP 54.39.203.58 is an OVH-hosted cloud infrastructure address associated with Ahrefs Pte Ltd organization. While the IP shows no direct threat indicators, it resides within a high-abuse subnet (54.39.203.0/24) with elevated neighborhood risk. The IP demonstrates cloud compute infrastructure characteristics with firewalled services and should be monitored but does not require immediate blocking without additional contextual signals.

## Ownership and Network Context

## Risk Assessment

MetricValueAssessment
Overall Risk Score40Moderate Risk
Provider Score0Neutral
Authority Score0Neutral
Operator Score0.2174Minimal
Abuse ConfidenceN/ANo direct abuse signal
Blacklist Count0Clean
DNSBL Listings1 of 8Minor listing present

## Neighborhood Analysis (54.39.203.0/24)

The IP operates within a subnet exhibiting significant abuse patterns:

This environment suggests the subnet is actively utilized for hosting services, with a notable portion showing malicious activity patterns.

## Technical Observations

## Historical Trend

Analysis of 21 signal observations reveals consistent infrastructure classification with no escalation in threat posture. The IP has not demonstrated increasing risk characteristics over the observation period.

## Recommended Security Actions

Based on current risk profile (score 40), the following controls are recommended:

Immediate Mitigation:

```bash

# iptables

iptables -A INPUT -s 54.39.203.58 -j DROP

# nftables

nft add rule inet filter input ip saddr 54.39.203.58 drop

# Cloudflare WAF

Filter: ip.src eq 54.39.203.58

Action: block

```

Operational Guidance:

## Intelligence Assessment

The IP represents moderate risk primarily due to neighborhood context rather than intrinsic malicious behavior. The absence of open services, clean blacklist status, and lack of persistent threat activity supports a monitoring approach over immediate blocking. Organizations with strict security postures may implement the recommended firewall rules, while others may opt to observe the IP's activity patterns before taking action.

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

🌐 DNS Intelligence

PTRproxy-ca008-san58.ahrefs.net
Forward ConfirmedNo β€” PTR hostname does not resolve back to this IP (weak signal)
Forward Hostnamesproxy-ca008-san58.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
19%
22
reputation
31%
13
geolocation
33%
23
Overall24%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-22 03:10:33 UTC
Last Seen2026-06-28 18:02:22 UTC
Profile Built2026-06-29 06:05:37 UTC
Data FreshnessLive
Signal Types22
Total Observations24
πŸ” 22 signal types Β· 24 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.