Shame on you, stupid spammers.. DMARC Spoof Detection

DMARC Spoof Detection, Brazil

Clear Clear Filter

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

Brazil accounts for 178 DMARC authentication failures observed by sh4meful over the observation window, sourced from 164 distinct IP addresses across 104 networks. This represents approximately 3.4% of total failure volume observed. Activity from Brazil has increased over the last 30 days compared with the prior 30-day period. The most active source is Claro NXT Telecomunicacoes Ltda with 20 failures across 19 IP addresses.

Failures (Filtered)

178

IPs (Filtered)

164

Networks (Filtered)

104

Messages (Filtered)

538

Top Networks in Brazil

Ten most active networks sourcing DMARC failures from Brazil:

Network Organization Failures Distinct IPs Top City
Claro NXT Telecomunicacoes Ltda 20 19 Rio de Janeiro
TELEFÔNICA BRASIL S.A 3 3 Regente Feijó
BRISANET SERVICOS DE TELECOMUNICACOES S.A 4 4 Sobral
ACESSOLINE TELECOMUNICA??ES LTDA 6 5 Agudos do Sul
VERO S.A 4 3 Cláudio
MUNDIVOX DO BRASIL LTDA 5 4 Rio de Janeiro
Alares Cabo Servicos de Telecomunicacoes S.A. 4 4 São João da Boa Vista
figueiredo provedores eireli 3 2 Montes Claros
TELEF?NICA BRASIL S.A 4 4 São Paulo
A & G Serviços em TI 1 1 Brasília

Claro NXT Telecomunicacoes Ltda and TELEFÔNICA BRASIL S.A together account for 21% 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 38 failures recorded. Activity in the most recent 30-day window increased compared with the prior period (79 vs 54 failures).

Regional Context

Compared with peer geographies in South America, Brazil's failure volume is above the regional median. Countries in this region collectively contributed 7% of failures observed.

What This Means

Country-level patterns don't imply that mail from Brazil 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.