ArchivedNo longer active, data collection ran March 2024 to September 2026|9,442 records|3,409 source IPs|138 countriesAbout this archive
Shame on you, stupid spammers..DMARC Spoof Detection

DMARC Spoof Detection, Croatia

ClearClear Filter

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

Croatia accounts for 8 DMARC authentication failures observed by sh4meful over the observation window, sourced from 6 distinct IP addresses across 4 networks. This represents approximately 0.1% of total failure volume observed. Activity from Croatia has held roughly steady over the last 30 days. The most active source is T-HT with 2 failures across 2 IP addresses.

Failures (Filtered)

8

IPs (Filtered)

6

Networks (Filtered)

4

Messages (Filtered)

14

Top Networks in Croatia

Ten most active networks sourcing DMARC failures from Croatia:

NetworkOrganizationFailuresDistinct IPsTop City
T-HT22Mali Lošinj
HR-TELEMACH-2005041511Zagreb
MTNET31Varaždin
XNET-CABLE11Zagreb

T-HT and HR-TELEMACH-20050415 together account for 64% of failure volume from this country. Concentration in a small number of networks suggests targeted infrastructure rather than diffuse compromise.

Failure Activity Over Time

Regional Context

Compared with peer geographies in Southern Europe, Croatia's failure volume is below the regional median. Countries in this region collectively contributed 2% of failures observed.

Failures

Showing 1-8 of 8 failures, affecting 14 messages
Date ▼ Source IP Country City Network Messages
4/7/2026 92.242.224.36 HR CroatiaVaraždin MTNET 1
4/7/2026 92.242.224.36 HR CroatiaVaraždin MTNET 1
4/7/2026 86.33.30.223 HR CroatiaZagreb HR-TELEMACH-20050415 4
4/7/2026 92.242.224.36 HR CroatiaVaraždin MTNET 1
3/29/2026 195.29.109.121 HR CroatiaMali Lošinj T-HT 1
7/21/2025 46.188.179.247 HR CroatiaZagrebN/A1
7/6/2025 188.252.197.79 HR CroatiaZagreb XNET-CABLE 1
7/1/2025 83.131.178.152 HR CroatiaZagreb T-HT 4

What This Means

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