Shame on you, stupid spammers.. DMARC Spoof Detection

DMARC Spoof Detection, Hong Kong

Clear Clear Filter

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

Hong Kong accounts for 17 DMARC authentication failures observed by sh4meful over the observation window, sourced from 14 distinct IP addresses across 8 networks. This represents approximately 0.0% of total failure volume observed. Activity from Hong Kong has declined over the last 30 days compared with the prior 30-day period. The most active source is Microsoft with 4 failures across 2 IP addresses.

Failures (Filtered)

17

IPs (Filtered)

14

Networks (Filtered)

8

Messages (Filtered)

21

Top Networks in Hong Kong

Ten most active networks sourcing DMARC failures from Hong Kong:

Network Organization Failures Distinct IPs Top City
UK-MICROSOFT-20060601 Microsoft 4 2 Hong Kong
MSFT Microsoft 4 4 Hong Kong
Huawei-HK-CLOUDS โ€” 1 1 Hong Kong
UNICOM-HK โ€” 2 2 โ€”
M365GROUPLLC-AP โ€” 2 1 Hong Kong
HKT-BIA โ€” 2 2 โ€”
FXCREATION-HK โ€” 1 1 โ€”
HUTCHISON-MOBILE-IP โ€” 1 1 โ€”

Microsoft and Microsoft together account for 38% 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 8, 2026 with 2 failures recorded. Activity in the most recent 30-day window declined sharply compared with the prior period (0 vs 4 failures).

Regional Context

Compared with peer geographies in Eastern Asia, Hong Kong's failure volume is below the regional median. Countries in this region collectively contributed 1% of failures observed.

Failures

Showing 1-10 of 17 failures, affecting 21 messages
Top Owners in Hong Kong

What This Means

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