Sh4mefulIP Address: 178.204.84.30
IP address 178.204.84.30 is registered to route object for TATTELECOM and geolocates to Kazan', Russia. It was observed in sh4meful's dataset on June 24, 2026. Over the observation window, it has failed DMARC alignment once, targeting one sender domain. It has no reverse DNS record. Network context: this address sits within TATARBROADBANDNETS (route object for TATTELECOM), a network sh4meful has observed producing 1 failures across 1 distinct IP during the same window.
Failure Activity Over Time
Peak activity was observed in the week of June 22, 2026 with 1 failures recorded. Activity in the most recent 30-day window increased sharply compared with the prior period (1 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:
- RU Russia
- Region:
- Tatarstan Republic
- City:
- Kazan'
- Coordinates:
- 55.785, 49.1178
WHOIS Information
- Network Name:
- TATARBROADBANDNETS
- CIDR:
178.204.64.0/19- Owner:
- route object for TATTELECOM
Analysis
This IP was observed generating a single DMARC authentication failure on June 24, 2026. With only one data point, the event is better read as a single suspicious observation than a sustained campaign. Every message observed from this source failed both SPF and DKIM verification. Receiving mail providers applied a reject disposition, refusing delivery outright.
The address has no reverse DNS record. Legitimate mail infrastructure almost always publishes a PTR record, because major receivers (Gmail, Microsoft 365, Yahoo) penalize or reject mail without one, and because it is a baseline operational hygiene expectation. Its absence, combined with authentication failure, is consistent with a host being used to originate spoofed mail rather than one misconfigured by a legitimate operator.
Geolocation places the host in Kazan', Russia, within infrastructure operated by route object for TATTELECOM. Sanctions, regional routing policies, and limited abuse-response channels in this jurisdiction mean upstream takedown through the provider is typically slow or unavailable. Receiver-side filtering is the most reliable mitigation.
The address is registered to route object for TATTELECOM (TATARBROADBANDNETS). Enterprise-registered addresses that appear in DMARC failure data are typically either compromised hosts on the organization's network or outbound mail relays that are not properly authorized in the domain's SPF record.
Across the wider TATARBROADBANDNETS network, 1 distinct IP has been associated with 1 authentication failures over 1 observed messages, spanning 1 country. Activity on this network is sparse in this dataset, suggesting isolated rather than systematic abuse.
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 route object for TATTELECOM is listed in RIPE WHOIS records, though response from this jurisdiction is typically slow or unavailable due to regional routing policies.
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.