Shame on you, stupid spammers.. DMARC Spoof Detection

DMARC Spoof Detection, Kenya

Clear Clear Filter

This page shows DMARC authentication failures originating from Kenya. Learn more about this data.

Kenya accounts for 18 DMARC authentication failures observed by sh4meful over the observation window, sourced from 18 distinct IP addresses across 5 networks. This represents approximately 0.0% of total failure volume observed. Activity from Kenya has increased over the last 30 days compared with the prior 30-day period. The most active source is SFC-GPRS-EDGE-3G-SERVICE-POOL2 with 3 failures across 3 IP addresses.

Failures (Filtered)

18

IPs (Filtered)

18

Networks (Filtered)

5

Messages (Filtered)

45

Top Networks in Kenya

Ten most active networks sourcing DMARC failures from Kenya:

Network Organization Failures Distinct IPs Top City
SFC-GPRS-EDGE-3G-SERVICE-POOL2 โ€” 3 3 Nairobi
Flink โ€” 1 1 Nairobi
SFC-GPRS-EDGE-3G โ€” 1 1 Nairobi
SPRINKVILLE-NETWORKS โ€” 1 1 Nairobi
Mobile_Data_3G_LTE_8 โ€” 2 2 Nairobi

SFC-GPRS-EDGE-3G-SERVICE-POOL2 and Flink together account for 29% of failure volume from this country. Distribution across many networks is consistent with commodity spoofing infrastructure operating from this geography.

Failure Activity Over Time

Peak activity was observed in the week of June 15, 2026 with 8 failures recorded. Activity in the most recent 30-day window increased compared with the prior period (9 vs 8 failures).

Regional Context

Compared with peer geographies in Eastern Africa, Kenya's failure volume is above the regional median. Countries in this region collectively contributed 0% of failures observed.

What This Means

Country-level patterns don't imply that mail from Kenya is inherently malicious. Many failures reflect misconfigured legitimate senders, forwarded messages that break authentication, or automated infrastructure operating without authorization. Domain owners investigating a specific failure should look at the source IP and network details rather than the country alone. Our DMARC guide explains how to interpret these signals in your own reports.