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

IP Address: 108.36.196.62

IP address 108.36.196.62 is registered to Verizon Business and geolocates to Conshohocken, United States. It was observed in sh4meful's dataset on July 2, 2026. Over the observation window, it has failed DMARC alignment once, targeting one sender domain. Its reverse DNS resolves to pool-108-36-196-62.phlapa.fios.verizon.net. Network context: this address sits within VIS-BLOCK (Verizon Business), 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 29, 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:
US United States
Region:
Pennsylvania
City:
Conshohocken
Coordinates:
40.0825, -75.3044
WHOIS Information
Network Name:
VIS-BLOCK
CIDR:
108.32.0.0/12, 108.0.0.0/11, 108.56.0.0/15, 108.48.0.0/13
Owner:
Verizon Business
Org ID:
MCICS
Address:
22001 Loudoun County Pkwy, Ashburn, VA 20147
Reverse DNS:
pool-108-36-196-62.phlapa.fios.verizon.net
Last updated: 7/3/2026

Analysis

This IP was observed generating a single DMARC authentication failure on July 2, 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 reverse DNS record (pool-108-36-196-62.phlapa.fios.verizon.net) matches a generic ISP address pattern, typical of consumer or small-business connections rather than dedicated mail infrastructure. Mail originating from addresses like this is frequently associated with compromised endpoints, such as home routers, IoT devices, or infected personal computers being used as part of a botnet.

Geolocation places the host in Conshohocken, United States, on infrastructure operated by Verizon Business. Abuse-reporting channels in this jurisdiction are generally responsive, and reports to the network operator can result in timely remediation.

The address belongs to Verizon Business, a residential ISP. Mail originating directly from residential IP space is almost never legitimate: ISPs block outbound port 25 for consumer customers, and residential addresses that do emit SMTP traffic are typically compromised devices in a botnet, including home routers, IoT devices, or infected personal computers.

Across the wider VIS-BLOCK network, 3 distinct IPs have been associated with 7 authentication failures over 19 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 Verizon Business is listed in ARIN WHOIS records, and timely remediation is achievable through that channel.

Failures Detected from this IP
Showing 1-1 of 1 failures, affecting 1 message
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.