Watch protection
happen.
Real web traffic. Native ban confirmations.
An open window into fail2zig at work.
Explore incoming requests, inspect an address, and see the protection the daemon actually reports.
Enter the observation consoleLoading capture metadata…
Observations show what arrived.
Confirmations show native decisions.
Incoming activity
Requests appear as the observer sees them.
A quiet feed can still be healthy.
Confirmed protection
Authoritative current snapshot · checking…
Confirmation and enforcement are reported independently.
Every observation has context.
Select an address in either panel to bring its requests, native confirmations and current protection together.
Same address; request-to-decision attribution is not exported. Only retained activity is shown.
Observed requests
Native confirmations
Current protection LIVE
Awaiting current snapshot
Protection has a health signal.
Live native samples, independent of the activity view.
Status and readiness are
sampled separately.
Checking native status and readiness…
Technical details Runtime, component states & worker diagnostics
A real surface.
An inert target.
Web probes reach static decoys. Authentication attempts meet an empty password file. fail2zig reads the service logs and confirms enforcement through the kernel.
How confirmation workssshd nginx-botsearch nginx-http-auth nginx-limit-req recidive Deployed policy Documented September 16, 2026
| Jail | Threshold / window | Initial ban | Repeat behavior |
|---|---|---|---|
sshd | 3 / 10 min | 15 min | Increases up to 24 hours |
nginx-botsearch | 2 / 5 min | 15 min | Contributes to recidive |
nginx-http-auth | 3 / 5 min | 15 min | Contributes to recidive |
nginx-limit-req | 2 / 1 min | 15 min | Contributes to recidive |
recidive | 3 / 24 hours | 1 hour | Separate repeat-offender policy |