Sh4mefulIP Address: 161.47.34.7
Dormant. IP address 161.47.34.7 is registered to Rackspace Hosting and geolocates to United States. It first appeared in sh4meful's dataset on July 2, 2025 and was most recently observed on July 9, 2025. Over the observation window, it has failed DMARC alignment 2 times, targeting one sender domain. Its reverse DNS resolves to gate.forward.smtp.ord1d.emailsrvr.com. Network context: this address sits within RACKS-8 (Rackspace Hosting), a network sh4meful has observed producing 2 failures across 1 distinct IP during the same window.
Failure Activity Over Time
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:
- US United States
- Coordinates:
- 37.751, -97.822
WHOIS Information
- Network Name:
- RACKS-8
- CIDR:
161.47.0.0/16- Owner:
- Rackspace Hosting
- Org ID:
RACKS-8- Address:
- 1718 Dry Creek Way Ste 115, San Antonio, TX 78259-1837
- Reverse DNS:
-
gate.forward.smtp.ord1d.emailsrvr.com
Last updated: 2/5/2026
Analysis
This IP generated DMARC authentication failures across 2 messages between July 2, 2025 and July 9, 2025, showing low but persistent activity. Every message observed from this source failed both SPF and DKIM verification. Receiving mail providers applied a quarantine disposition, routing messages to spam or junk folders.
The reverse DNS record (gate.forward.smtp.ord1d.emailsrvr.com) 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 United States, on infrastructure operated by Rackspace Hosting. 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 Rackspace Hosting (RACKS-8), a major cloud provider. Isolated abuse activity on established cloud platforms is common: attackers stand up short-lived virtual machines for individual campaigns, and does not indicate broader compromise of the provider's infrastructure.
Across the wider RACKS-8 network, 1 distinct IP has been associated with 2 authentication failures over 2 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 quarantine 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 Rackspace Hosting 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.