142.44.228.233
IP Intelligence Briefing for 142.44.228.233
Date: June 13, 2026
---
**1. Core Profile**
- Risk Score: 40 (Moderate Risk)
- Ownership: Registered to Ahrefs Pte Ltd (OVH ASN 16276), CIDR block 142.44.228.0/24.
- Geolocation:
- Country: Canada (CA)
- City: Singapore (conflicting data; RTT analysis suggests ~5,598km distance, but latency of 26ms, which is implausible for that distance).
- Network Role:
- Hosting provider (OVH), classified as CloudCompute.
- No open ports or TLS services detected.
- Threat Indicators:
- No malicious activity, spam, or known attacker associations.
---
**2. Historical Observations**
- Recent Activity:
- Observed 26 signals over 30 days, with consistent high abuse density (0.6016) in its subnet.
- Geo validation flagged as plausible? No. RTT analysis shows 26ms latency for ~5,598km, which is inconsistent (minimum plausible RTT: 112ms).
- No persistent malicious behavior (threat persistence: 0 days).
---
**3. Network Relationships**
- Subnet: 142.44.228.0/24
- Neighbors:
- 256 total IPs in subnet; 185 active, 154 flagged as threats.
- Abuse density: 60.16% (high risk).
- Shared Network:
- Linked to OVH-CUST-281059695 (same ASN 16276).
---
**4. DNS & Hosting**
- PTR Record: `proxy-ca016-san233.ahrefs.net` (points to ahrefs.net).
- Domain: ahrefs.net (no email authentication records).
- Hosting: Likely part of a cloud infrastructure (OVH Hosting).
---
**5. Actionable Recommendations**
- Firewall Rules:
- Block via iptables: `iptables -A INPUT -s 142.44.228.233 -j DROP`
- AWS WAF: Add `142.44.228.233/32` to a rule with description "IPDebrief risk 40".
- Monitoring:
- Investigate geolocation discrepancy (Singapore vs. Canada).
- Monitor subnet (142.44.228.0/24) for increased threat activity.
---
**6. Summary**
The IP is part of a high-abuse subnet (60% abuse density) under OVH, registered to a legitimate hosting provider. While the IP itself shows no direct malicious indicators, its network environment raises concerns. The geolocation data inconsistency warrants further verification. SOC teams should consider blocking this IP and monitoring its subnet for potential lateral movement or compromised hosts.
This summary was generated by AI and may contain inaccuracies. Verify critical details independently.
🏢 Ownership & Registration
| Organization | Dmytro, Ahrefs Pte Ltd |
| ASN | AS16276 |
| Network Name | OVH-CUST-281059695 |
| CIDR Block | 142.44.228.0/24 |
| RIR | ARIN |
| Country | Singapore |
| Abuse Contact | — |
🌐 DNS Intelligence
| PTR | proxy-ca016-san233.ahrefs.net |
| Forward Confirmed | No — PTR hostname does not resolve back to this IP (weak signal) |
| Forward Hostnames | proxy-ca016-san233.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 | Tier 3 — Basic operator with some routing infrastructure |
🔌 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
| SANs | None |
| Valid From | — |
| Valid Until | — |
🎯 Confidence Breakdown
Per-dimension confidence scores based on source diversity and data freshness
| Dimension | Score | Sources | Observations |
|---|---|---|---|
| threat | 30% | 2 | 4 |
| routing | 20% | 2 | 3 |
| services | 12% | 2 | 2 |
| ownership | 22% | 3 | 3 |
| reputation | 28% | 1 | 3 |
| geolocation | 35% | 2 | 3 |
| Overall | 25% | 12 | 18 |
| Data Coherence | Mostly Consistent (80%) — 1 contradiction(s) |
| Attribution | Low (35%) |
| OwnershipFCrDNSGeo ConsensusGeo PlausibleIRR MatchRPKI Valid |
📅 Observation Timeline 🔄 Live
| First Seen | 2026-05-07 23:03:43 UTC |
| Last Seen | 2026-06-26 23:10:19 UTC |
| Profile Built | 2026-06-27 19:23:10 UTC |
| Data Freshness | Live |
| Signal Types | 25 |
| Total Observations | 33 |
Full dossier details are available via our API.