Script NoScannerZone – Collective IP Blocking for Server Security

[a2-soft]

Stop Scanners, VPNs & Abusive IPs – Join the Collective Defense​

Why block known IPs (VPNs, scanners, abusive networks)?​

Many IPs used by VPN services, automated scanners, or suspicious users originate from data centers or cloud providers. Although these IPs may appear residential, they're often used for:

• Port scanning
• 🛡 Firewall evasion
• Abuse and intrusion attempts
• Proxy / VPN / TOR cloaking

VPN services often reuse legitimate-looking IPs that are no longer safe.​

Collective Protection = Better Security​

When multiple servers and projects share the same block lists, attackers lose power:

• Known scanners are blocked instantly
• Abusive IPs are shut down globally
• Fewer login attempts, lower server load, better uptime

Conclusion​

The more we share and apply trusted IP blocklists, the harder it becomes for bots and attackers to even reach our services.​

Scripts to Block Automatically​

You can use these one-liner scripts to stay protected:

1. IPSET Auto-Block:

wget -qO- https://raw.githubusercontent.com/Akademik120706/ipset/main/update-ipset.sh | bash

✔ Uses ipset for fast performance
✔ Pulls fresh blocklist from GitHub
✔ Creates or updates "bad_ips" list
✔ Adds iptables rules to block them

2. IPTABLES Auto-Block:

wget -qO- https://raw.githubusercontent.com/Akademik120706/iptables/main/update-ip.sh | bash

✔ Uses classic iptables directly
✔ Works with existing firewall setups
✔ Loads predefined block rules instantly

GitHub Repositories​

• IPSet Blocklist & Scripts
• IPTables Rules & Tools

Join Our Telegram Group​

We’ve created a group to share bad IPs, scanners, and abuse reports:

https://t.me/Noscannerzone

Together we can reduce attacks before they happen!​

 

[a2-soft]

Stop Scanners, VPNs & Abusive IPs – Join the Collective Defense​

Why block known IPs (VPNs, scanners, abusive networks)?​

Many IPs used by VPN services, automated scanners, or suspicious users originate from data centers or cloud providers. Although these IPs may appear residential, they're often used for:

• Port scanning
• 🛡 Firewall evasion
• Abuse and intrusion attempts
• Proxy / VPN / TOR cloaking

VPN services often reuse legitimate-looking IPs that are no longer safe.​

Collective Protection = Better Security​

When multiple servers and projects share the same block lists, attackers lose power:

• Known scanners are blocked instantly
• Abusive IPs are shut down globally
• Fewer login attempts, lower server load, better uptime

Conclusion​

The more we share and apply trusted IP blocklists, the harder it becomes for bots and attackers to even reach our services.​

Scripts to Block Automatically​

You can use these one-liner scripts to stay protected:

1. IPSET Auto-Block:

wget -qO- https://raw.githubusercontent.com/Akademik120706/ipset/main/update-ipset.sh | bash

✔ Uses ipset for fast performance
✔ Pulls fresh blocklist from GitHub
✔ Creates or updates "bad_ips" list
✔ Adds iptables rules to block them

2. IPTABLES Auto-Block:

wget -qO- https://raw.githubusercontent.com/Akademik120706/iptables/main/update-ip.sh | bash

✔ Uses classic iptables directly
✔ Works with existing firewall setups
✔ Loads predefined block rules instantly

GitHub Repositories​

• IPSet Blocklist & Scripts
• IPTables Rules & Tools

Join Our Telegram Group​

We’ve created a group to share bad IPs, scanners, and abuse reports:

https://t.me/Noscannerzone

Together we can reduce attacks before they happen!​

update 9.6.2025 - 2308 ip