Sh4mefulIP Address: 185.243.99.53
IP address 185.243.99.53 is registered to ORG-RPOE1-RIPE and geolocates to Kyiv, Ukraine. It first appeared in sh4meful's dataset on June 26, 2026 and was most recently observed on July 6, 2026. Over the observation window, it has failed DMARC alignment 3 times, targeting one sender domain. Its reverse DNS resolves to mta.email.rifia.shop. Network context: this address sits within NTS-04 (ORG-RPOE1-RIPE), a network sh4meful has observed producing 7 failures across 3 distinct IPs during the same window.
Failure Activity Over Time
Peak activity was observed in the week of June 22, 2026 with 2 failures recorded. Activity in the most recent 30-day window increased sharply compared with the prior period (3 vs 0 failures).
This IP has claimed to send from 1 sender domain monitored by sh4meful. The single targeted domain suggests either a compromised sending source or a spoofing attempt focused on a specific brand.
This page shows DMARC authentication failure data for this IP address. Learn more about this data.
Geolocation Information
- Country:
- UA Ukraine
- Region:
- Kyiv City
- City:
- Kyiv
- Coordinates:
- 50.458, 30.5303
WHOIS Information
- Network Name:
- NTS-04
- CIDR:
185.243.99.0/24- Owner:
- ORG-RPOE1-RIPE
- Reverse DNS:
-
mta.email.rifia.shop
Last updated: 6/27/2026
Analysis
This IP generated DMARC authentication failures across 3 messages between June 26, 2026 and July 6, 2026, showing low but persistent activity. 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 (mta.email.rifia.shop) suggests the host is configured as mail infrastructure. In the context of authentication failures, this most often indicates either a misconfigured legitimate sender or a compromised mail server being used to relay abuse.
Geolocation places the host in Kyiv, Ukraine, on infrastructure operated by ORG-RPOE1-RIPE. Abuse-reporting channels in this jurisdiction are generally responsive, and reports to the network operator can result in timely remediation.
The address is registered to ORG-RPOE1-RIPE (NTS-04), an enterprise network operator. Concentrated authentication failures on enterprise address space can indicate either a compromised internal host being used as an unauthorized sending relay, or an organization knowingly or unknowingly operating as a spam source.
Across the wider NTS-04 network, 3 distinct IPs have been associated with 7 authentication failures over 7 observed messages, spanning 1 country. Most observed IPs on this network contribute to the failure count, suggesting the range as a whole warrants elevated scrutiny.
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 ORG-RPOE1-RIPE is listed in RIPE WHOIS records, and timely remediation is achievable through that channel.
Network Topology
This address is part of NTS-04 (ORG-RPOE1-RIPE), announced from Ukraine. 3 IPs in this network have been observed in sh4meful's dataset.
External Reputation Lookups
Look up this IP in external threat intelligence and reputation databases (opens in new tab):
Nearby IPs
The following IP addresses share the same /24 subnet as 185.243.99.53 and have appeared in sh4meful's dataset. Related activity in nearby addresses often indicates infrastructure operated by a single actor or provider.
- 185.243.99.43 — 2 failures, first seen 11 days ago, 9 days after this address.
- 185.243.99.74 — 2 failures, first seen 11 months ago, 339 days before this address.
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.