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, Japan

ClearClear Filter

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

Japan accounts for 42 DMARC authentication failures observed by sh4meful over the observation window, sourced from 18 distinct IP addresses across 13 networks. This represents approximately 0.3% of total failure volume observed. Activity from Japan has held roughly steady over the last 30 days. The most active source is KIR with 10 failures across 2 IP addresses.

Failures (Filtered)

42

IPs (Filtered)

18

Networks (Filtered)

13

Messages (Filtered)

50

Top Networks in Japan

Ten most active networks sourcing DMARC failures from Japan:

NetworkOrganizationFailuresDistinct IPsTop City
KIRโ€”102โ€”
SAKURA-NETโ€”123Hiyoshi
RIPE-ERX-147-44-0-0โ€”53Tokyo
DIX-CLโ€”51โ€”
ASAHI-NETโ€”21Tokorozawa
CSF-NET-CIDR-BLK-JPโ€”11โ€”
NIACโ€”11Nagoya
YAHOO-APโ€”11โ€”
OCNโ€”11โ€”
GOOGLE-CLOUDGoogle11Tokyo

KIR and SAKURA-NET together account for 54% 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 July 20, 2026 with 2 failures recorded. Activity in the most recent 30-day window held roughly steady compared with the prior period (0 vs 0 failures).

Regional Context

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

Failures

Showing 1-10 of 42 failures, affecting 50 messages
Date โ–ผ Source IP Country City Network Messages
7/22/2026 180.131.140.6 JP Japan GMOHS-CL-CIDR-BLK-JP 1
7/21/2026 122.17.164.107 JP Japan OCN 1
7/9/2026 153.120.93.9 JP Japan SAKURA-NET 1
6/24/2026 153.125.138.166 JP Japan SAKURA-NET 1
6/23/2026 153.125.138.166 JP Japan SAKURA-NET 1
6/23/2026 153.125.138.166 JP Japan SAKURA-NET 1
6/16/2026 153.125.138.166 JP Japan SAKURA-NET 1
6/4/2026 153.125.138.166 JP Japan SAKURA-NET 1
6/2/2026 153.125.138.166 JP Japan SAKURA-NET 1
5/29/2026 153.125.138.166 JP Japan SAKURA-NET 1
5/29/2026 153.125.138.166 JP Japan SAKURA-NET 1
5/26/2026 153.125.138.166 JP Japan SAKURA-NET 1
5/26/2026 153.125.138.166 JP Japan SAKURA-NET 1
5/26/2026 49.212.142.209 JP JapanHiyoshi SAKURA-NET 1
4/24/2026 159.28.108.2 JP JapanNagoya NIAC 2
3/12/2026 157.107.128.169 JP JapanTokorozawa ASAHI-NET 1
3/12/2026 157.107.128.169 JP JapanTokorozawa ASAHI-NET 1
3/3/2026 147.45.220.117 JP JapanTokyo RIPE-ERX-147-44-0-0 1
11/25/2025 147.45.220.83 JP JapanTokyo RIPE-ERX-147-44-0-0 1
11/19/2025 147.45.220.83 JP JapanTokyo RIPE-ERX-147-44-0-0 2
10/7/2025 147.45.220.68 JP JapanTokyo RIPE-ERX-147-44-0-0 1
10/5/2025 162.43.57.215 JP Japan XVPS 1
9/17/2025 147.45.220.68 JP JapanTokyo RIPE-ERX-147-44-0-0 1
9/1/2025 35.194.98.235 JP JapanTokyo GOOGLE-CLOUD 1
7/31/2025 133.18.225.36 JP Japan KIR 1
7/31/2025 133.18.225.36 JP Japan KIR 1
7/30/2025 133.18.225.36 JP Japan KIR 1
7/24/2025 133.18.225.36 JP Japan KIR 1
7/23/2025 133.18.225.36 JP Japan KIR 1
7/22/2025 133.18.225.36 JP Japan KIR 4
7/15/2025 133.18.225.36 JP Japan KIR 1
7/14/2025 133.18.225.36 JP Japan KIR 1
6/15/2025 210.134.51.184 JP Japan KAGOYA 1
6/9/2025 133.18.94.79 JP Japan KIR 1
6/5/2025 133.18.94.79 JP Japan KIR 3
4/21/2025 123.242.209.237 JP Japan CSF-NET-CIDR-BLK-JP 2
12/5/2024 153.122.75.80 JP Japan DIX-CL 1
11/21/2024 153.122.75.80 JP Japan DIX-CL 1
11/14/2024 153.122.75.80 JP Japan DIX-CL 1
11/10/2024 183.79.55.13 JP Japan YAHOO-AP 1
7/1/2024 153.122.75.80 JP Japan DIX-CL 1
6/26/2024 153.122.75.80 JP Japan DIX-CL 1
Top Owners in Japan

What This Means

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