Shame on you, stupid spammers.. Sh4meful  DMARC Spoof Detection

IP Address: 64.26.60.153

Dormant. IP address 64.26.60.153 is registered to Ntirety, Inc and geolocates to United States. It first appeared in sh4meful's dataset on December 9, 2024 and was most recently observed on December 17, 2024. Over the observation window, it has failed DMARC alignment 2 times across 2 distinct sender domains. Its reverse DNS resolves to mx0.mfg.onr.siteprotect.com. Network context: this address sits within HOSTWAY-02 (Ntirety, Inc), 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 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
Coordinates:
37.751, -97.822
WHOIS Information
Network Name:
HOSTWAY-02
CIDR:
64.26.48.0/20
Owner:
Ntirety, Inc.
Org ID:
WCP32
Address:
2901 Via Fortuna, Suite 175, Austin, TX 78746
Reverse DNS:
mx0.mfg.onr.siteprotect.com
Last updated: 2/5/2026

Analysis

This IP generated DMARC authentication failures across 2 messages between December 9, 2024 and December 17, 2024, 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 resolves to mx0.mfg.onr.siteprotect.com. 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 United States, on infrastructure operated by Ntirety, Inc. 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 Ntirety, Inc (HOSTWAY-02). 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 HOSTWAY-02 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 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 Ntirety, Inc is listed in ARIN WHOIS records, and timely remediation is achievable through that channel.

Failures Detected from this IP
Showing 1-2 of 2 failures, affecting 2 messages
Date โ–ผ Messages
12/17/2024 1
12/9/2024 1
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.