AS38074 Ayao Takata

Abuse reported against IP addresses announced by autonomous system 38074. If you run this network, the addresses below are a good place to start an abuse investigation.

In the last 30 days, 4 IP addresses in AS38074 Ayao Takata were reported for abuse, in 11 reports altogether. None of them has a confidence score high enough for the default blocklist yet. The most common reasons were Bad Web Bot, SSH and DNS Poisoning. Most of them are in Japan.

4addresses reported, 30 days

0on the default blocklist (75+)

11reports against them

1 hsince the latest report

Most reported addresses

Address	Score	Reports	Categories	Last seen
🇯🇵103.152.178.90	37	4	DNS Poisoning Web Spam Port Scan SQL Injection Bad Web Bot Exploited Host SSH Vulnerability Scan Malware Distribution Command & Control API Abuse Fake Accounts Telnet Abuse	1 h
🇯🇵103.152.178.94	27	3	DNS Poisoning Web Spam Port Scan SQL Injection Bad Web Bot Exploited Host SSH Vulnerability Scan Malware Distribution Command & Control API Abuse Fake Accounts Telnet Abuse	1 h
🇯🇵2001:df4:1780:110f::2222	27	2	DNS Poisoning SQL Injection Bad Web Bot Exploited Host SSH Vulnerability Scan Malware Distribution Command & Control API Abuse Fake Accounts Telnet Abuse	13 h
🇯🇵103.152.178.119	15	2	Web Spam Port Scan Bad Web Bot	1 h

What they were reported for

Where they are

🇯🇵 Japan4

Block them

The blocklist holds every address with a confidence of 75 or more, in nine formats for firewalls, web servers and SIEMs. Download it with a free API key:

curl -s "https://isipsafe.com/api/v1/blocklist?key=$ISIPSAFE_KEY&format=txt"

See the integration guides for nginx, fail2ban, pfSense, MikroTik and more, or the API reference.

Figures cover the last 30 days and are refreshed hourly; last updated 52 minutes ago.