Security

This site is a small target for automated scanners. They probe for WordPress admin pages, environment files, git configs, and other paths that do not exist here. I block them with fail2ban and report them to abuse databases.

fail2ban

fail2ban watches the web server access log. When an address requests a known probe path and gets a 404 or 403, it counts as a failure. Three failures in ten minutes gets the address banned for one hour.

fail2ban jail settings
Jailnginx-wp
Log/var/log/nginx/access.log
Max retries3
Find time600 seconds (10 minutes)
Ban time3600 seconds (1 hour)
ActionBlock on HTTP and HTTPS, report to AbuseIPDB and Blocklist.de

What gets banned

The filter matches requests for paths that are only ever probed by scanners. Legitimate visitors and search engines never request them, so they never match.

Probe paths that trigger a ban
WordPresswp-admin, wp-login.php, xmlrpc.php, wp-content, wp-includes, wp-json, any .php on 404/403
Secrets and configs.env, .git/, .svn/, .aws/, config.php, config.json, phpinfo.php
Admin panelsphpmyadmin, pma, adminer, actuator, server-status, server-info
Dev and API probes.idea/, .vscode/, .DS_Store, cgi-bin, backup, api, graphql, telescope, v2/_catalog, @vite

Paths that are never banned: /.well-known/ (the agent discovery files live there), /robots.txt, /favicon.ico, and /apple-touch-icon-precomposed.png. Those are legitimate requests.

Abuse reporting

Every ban is also reported to two abuse databases, so other operators can block the same addresses.

AbuseIPDB

Reports go to AbuseIPDB as category 21, Web App Attack. The domain gnpk.zip is verified there. Reports are automatic, sent by the fail2ban action on every ban.

Blocklist.de

Reports go to Blocklist.de as service badbot. The server is registered there as gnpk-as. The HTTP reporting endpoint rejects the log parameter, so historical reports were sent by email instead. The automatic fail2ban action uses the HTTP endpoint and may fail on new bans; the local block still applies either way.

Addresses banned on 20 November 2026

These six addresses were banned on 20 November 2026 after probing for WordPress admin pages, environment files, and git configs. They were reported to AbuseIPDB and Blocklist.de.

Addresses banned on 20 November 2026
167.71.175.236Probed wp-admin and .env
167.99.210.137Probed wp-admin and .env
23.132.164.201Probed wp-admin and .git/config
34.19.127.191Probed wp-admin and .env
34.78.174.4791 probe requests, the most active scanner that day
88.151.33.188Probed wp-admin and .env

What I do not run

There is no SSH or Telnet server on this VPS, nothing listens on ports 22 or 23, so there is nothing to brute-force and no fail2ban jail for them. There is no rate limiting on the web server either; the fail2ban jail catches the scanners, and legitimate traffic is never affected.

Questions about the security setup: me@gnpk.zip.