Your IP: 216.73.216.123
π€ Witness AIThis summary was generated by AI and may contain inaccuracies. Verify critical details independently.
IP Intelligence Briefing: 198.244.168.147
Date: 2026-06-15
---
**1. Risk Profile**
- Risk Score: 40 (Moderate Risk)
- Provider: OVH (Cloud infrastructure)
- Ownership: Ahrefs Pte Ltd (legitimate entity, no abuse reports).
- Geolocation: London, England (plausible, no geo anomalies).
- Network Classification: High abuse subnet (198.244.168.0/24), with 55% abuse density.
---
**2. Threat Indicators**
- No direct malicious activity: No indicators of spam, attacks, or blacklists.
- Subnet Risk: 81/100 neighboring IPs in the subnet are medium/high risk, suggesting potential coordinated activity or compromised hosts.
- DNS Associations: Linked to `proxy-uk001-san147.ahrefs.net` (Ahrefsβ legitimate infrastructure).
---
**3. Network Behavior**
- Services: No open ports or TLS certificates detected.
- Routing: BGP prefix `198.244.128.0/17` (OVH-managed, stable).
- Subnet Activity: 141 active IPs in the /24 subnet, with 141 flagged as threats.
---
**4. Recommended Actions**
- Block the IP: Implement firewall rules to restrict traffic from 198.244.168.147.
- Example: `iptables -A INPUT -s 198.244.168.147 -j DROP`
- Monitor Subnet: Investigate high-risk neighbors in the 198.244.168.0/24 range.
- Verify Ahrefs Context: Confirm if the IP is part of a legitimate cloud setup or compromised infrastructure.
---
**5. Summary**
The IP is associated with Ahrefs but resides in a high-abuse subnet. While the IP itself shows no direct malicious activity, the surrounding networkβs risk profile warrants closer scrutiny. SOC teams should monitor traffic patterns and validate the legitimacy of the subnetβs usage.
Next Steps: Correlate with internal logs, check for anomalous behavior in the subnet, and validate Ahrefsβ network security posture.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
π’ Ownership & Registration
| Organization | Ahrefs Pte Ltd Dmytro |
| ASN | AS16276 |
| Network Name | β |
| CIDR Block | β |
| RIR | ARIN |
| Country | β |
| Abuse Contact | Available via RDAP |
π DNS Intelligence
| PTR | proxy-uk001-san147.ahrefs.net |
| Forward Confirmed | No β PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | proxy-uk001-san147.ahrefs.net |
π DNS Hygiene
| Hygiene Score | 40% (Fair) |
| SPF | Not configured |
| DMARC | Not configured |
| FCrDNS | Not verified |
| DNSSEC | Valid |
| CAA | Present |
βοΈ Network Classification
| Infrastructure | Infrastructure / Datacenter |
| Service Purpose | Firewalled / No Services |
| Network Tier | Hosting β Infrastructure provider without advanced routing |
π Services & Open Ports
| Port | Service | Protocol | Banner |
|---|---|---|---|
| No open ports detected | |||
| Closed Ports | 22, 25, 80, 443, 3389, 8080, 8443 (0 open / 7 scanned) | ||
| Server | β |
| HTTP Title | β |
π TLS Certificate
No certificate
Issued by β
N/A
| SANs | None |
| Valid From | β |
| Valid Until | β |
π― Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 31% | 2 | 4 |
| routing | 13% | 1 | 1 |
| services | 15% | 2 | 2 |
| ownership | 24% | 2 | 3 |
| reputation | 31% | 1 | 3 |
| geolocation | 39% | 2 | 3 |
| Overall | 26% | 10 | 16 |
Coverage: 6/6 dimensions Β· Data sufficiency: sufficient
| Data Coherence | Consistent (100%) |
| Attribution | Moderate (50%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
π Observation Timeline π Live
| First Seen | 2026-05-18 09:24:09 UTC |
| Last Seen | 2026-06-28 06:55:41 UTC |
| Profile Built | 2026-06-29 01:01:27 UTC |
| Data Freshness | Live |
| Signal Types | 21 |
| Total Observations | 25 |
π 21 signal types Β· 25 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.
Full dossier details are available via our API.
βΉοΈ 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.