Sh4mefulIP Address: 15.204.234.4
IP address 15.204.234.4 is registered to OVH US LLC and geolocates to Reston, United States. It first appeared in sh4meful's dataset on July 1, 2026 and was most recently observed on July 7, 2026. Over the observation window, it has failed DMARC alignment 2 times across 2 distinct sender domains. Its reverse DNS resolves to vps-8de709b8.vps.ovh.us. Network context: this address sits within OUL-16 (OVH US LLC), a network sh4meful has observed producing 20 failures across 12 distinct IPs during the same window.
Failure Activity Over Time
Peak activity was observed in the week of June 29, 2026 with 3 failures recorded. Activity in the most recent 30-day window increased sharply compared with the prior period (6 vs 0 failures).
This IP has claimed to send from 2 sender domains monitored by sh4meful. The narrow domain set is consistent with a targeted spoofing pattern.
This page shows DMARC authentication failure data for this IP address. Learn more about this data.
Geolocation Information
- Country:
- US United States
- Region:
- Virginia
- City:
- Reston
- Coordinates:
- 38.9609, -77.3429
WHOIS Information
- Network Name:
- OUL-16
- CIDR:
15.204.0.0/16- Owner:
- OVH US LLC
- Org ID:
OUL-16- Address:
- 11950 Democracy Drive, Reston, VA 20190
- Reverse DNS:
-
vps-8de709b8.vps.ovh.us
Last updated: 7/2/2026
Analysis
This IP generated DMARC authentication failures across 6 messages in a short window between July 1, 2026 and July 7, 2026. Every message observed from this source failed both SPF and DKIM verification. Receiving mail providers applied a reject disposition, refusing delivery outright.
The reverse DNS record resolves to vps-8de709b8.vps.ovh.us. Whether this represents legitimate mail infrastructure depends on whether the hostname aligns with the domains this address is claiming to send on behalf of.
Geolocation places the host in Reston, United States, on infrastructure operated by OVH US LLC. Abuse-reporting channels in this jurisdiction are generally responsive, and reports to the network operator can result in timely remediation.
The address is hosted on OVH US LLC (OUL-16), a major cloud provider. Authentication failures are spread across multiple IP ranges on this network, which is consistent with the scale of a large provider's customer base.
Across the wider OUL-16 network, 12 distinct IPs have been associated with 20 authentication failures over 33 observed messages, spanning 1 country. The failure pattern suggests a mix of abuse sources on this network.
If your domain appears in the From header of mail from this address, treat it as probable spoofing. Verify that your SPF record does not authorize this host, directly or through nested include mechanisms, and that no DKIM selector you publish has been issued to it. If both checks come back clean, the receiver's reject action is doing its job.
Your DMARC policy posture matters more than any IP-level response here. The enforcement action applied to this mail indicates your policy is already providing protection. Maintaining p=reject across all your domains closes the gap for attackers who manage partial alignment. Domains that remain at p=none long-term tend to be impersonated repeatedly, because the cost to the attacker of attempting is effectively zero.
Blocking this individual address has limited durability: an attacker can rotate to another address in the same /24 subnet at effectively zero cost. More durable responses include monitoring aggregate DMARC reports so new sources are visible as they emerge, tightening SPF to remove overly permissive include chains or +all mechanisms, and ensuring DKIM is signing every legitimate outbound stream so alignment failures are unambiguous. The formal abuse contact for OVH US LLC is listed in ARIN WHOIS records, and timely remediation is achievable through that channel.
External Reputation Lookups
Look up this IP in external threat intelligence and reputation databases (opens in new tab):
Recommended Action
If this IP appears in your own DMARC reports, treat it as an unauthorized sender unless you have specifically verified it as a legitimate service you use. Ensure your DMARC policy is at p=quarantine or p=reject to prevent delivery of messages this IP claims to send from your domain. If you're new to DMARC, our complete guide walks through the mechanics.