Distributed Threat Intelligence

Stop 404 scanners across every server you run

When one server in the network detects a scanner, every server blocks it automatically. Real-time shared intelligence at firewall level.

No agents to install
Any web server
Firewall-level blocking
threat404 — network status
Network statusLIVE
IPs blocked (total)1,419
Member servers4 nodes
Last sync2 min ago
Central nodeSingapore, SG
Sync intervalEvery 15 min
1,419Attacker IPs blocked
4Member servers
15mSync interval
2Countries covered
How it works

Three steps to network-wide protection

A lightweight script on each server does all the work — no dashboards to monitor, no rules to write manually.

STEP 01

Detect

A lightweight script monitors your access logs for 404 scanning patterns — probes targeting wp-admin, .env files, phpMyAdmin, and known exploit paths.

STEP 02

Share

The attacker IP is reported to the Threat404 central node via authenticated API. The master blocklist updates within seconds and is available to all members.

STEP 03

Block

Every 15 minutes all member servers pull the updated blocklist and load it into ipset. Attackers are dropped at kernel level — before reaching your app.

Features

Built for real server operators

No SaaS overhead, no agents, no vendor lock-in. Shell scripts and a shared blocklist.

Firewall-level blocking

Uses ipset and iptables to block at the kernel level. Attackers never reach nginx, Apache, or your application — zero processing overhead.

IPv4 + IPv6 dual-stack

Separate blocklists and ipset rules for both address families. Modern attackers use both — so does Threat404.

Any web server

Works with Apache, Nginx, OpenLiteSpeed, or any server writing standard combined log format. No server-specific plugins required.

15-minute sync cycle

Cron-driven pull every 15 minutes keeps all member servers current. New threats propagate to the entire network within one cycle.

WordPress MU plugin

Optional must-use plugin adds a threat dashboard to your WP admin — view blocked IPs, recent detections, and network stats without leaving WordPress.

Authenticated API

Each member server has a unique API key. All submissions are verified. Private and loopback addresses are automatically rejected server-side.

Who it's for

If you run servers, you need this

Any server exposed to the internet is being scanned constantly. Threat404 turns your network into a collective defence.

WordPress hosting operators

Block wp-login brute force and xmlrpc attacks before they reach PHP. Includes a WP admin dashboard plugin.

Web agencies with multiple clients

One detection on any client server protects all client servers. Collective intelligence across your entire portfolio.

SaaS and application servers

Stop credential stuffing and exploit scanning from reaching your application layer entirely. Zero performance impact.

Technical overview

Minimal footprint. No dependencies beyond bash, curl, and ipset.

/usr/local/bin/threat404-sync.sh
# Pull master blocklist every 15 min
curl https://api.threat404.cloud/blocklist.txt \
  -o /tmp/blocklist_new.txt

# Load into ipset (kernel firewall)
while read ip; do
  ipset add threat404_v4 "$ip" 2>/dev/null
done < /tmp/blocklist_new.txt

# Attackers dropped before reaching app
# ✓ 1,419 IPs currently blocked
Early access

Join the network

Currently a private network. Enter your email to be notified when public access opens and receive early member pricing.

No spam. Early members get free tier access for 12 months.