AS17563 NEXLINX

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

In the last 30 days, 3 IP addresses in AS17563 NEXLINX were reported for abuse, in 9 reports altogether. None of them has a confidence score high enough for the default blocklist yet. The most common reasons were Bad Web Bot, Web Spam and Telnet Abuse. Most of them are in Pakistan.

3addresses reported, 30 days

0on the default blocklist (75+)

9reports against them

11 hsince the latest report

Most reported addresses

Address	Score	Reports	Categories	Last seen
🇵🇰116.58.53.195	47	5	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	11 h
🇵🇰116.58.22.219	46	3	DNS Poisoning FTP Brute-Force Phishing Open Proxy Web Spam SQL Injection Brute-Force Bad Web Bot Exploited Host Web App Attack SSH Vulnerability Scan Malware Distribution Command & Control API Abuse HTTP Flood Fake Accounts Telnet Abuse	11 h
🇵🇰202.59.76.146	14	1	Web Spam Port Scan Bad Web Bot	17 h

What they were reported for

Where they are

🇵🇰 Pakistan3

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 34 minutes ago.