ModSecurity

ModSecurity WAF
Cache: 22:36:12 Refresh
ModSecurity Active
Today
2018
Blocked
169
Total in sample
2018
Unique IPs
10
Rule list unavailable — update the monitor-modsec wrapper and add the ---RULES--- section (see FAQ).
Attack types
XSS
12
SQL Injection
10
Scanner
7
Protocol Attack
7
RCE
7
LFI/Path Traversal
5
Top attacking IPs
IPEvents
198.51.100.215
198.51.100.194
198.51.100.344
198.51.100.233
198.51.100.353
198.51.100.113
198.51.100.313
198.51.100.183
198.51.100.143
198.51.100.132
Top target URLs
URIEvents
/.env9
/api/v1/login8
/index.php?id=18
/wp-login.php7
/xmlrpc.php7
/admin/5
/?q=../../etc/passwd4
Top triggered rules
Rule IDHits
930100
Path Traversal (/../)
14
942100
SQL Injection via libinjection
12
913100
Security scanner — User-Agent
8
941100
XSS via libinjection
8
932100
RCE — Unix commands
6
Recent events 48 entries
TimeIPURITypeRuleAction
2026-10-12 22:36:12 198.51.100.23 /wp-login.php Scanner 930100
Path Traversal (/../)
Detected
2026-10-12 22:28:58 198.51.100.35 /xmlrpc.php XSS 930100
Path Traversal (/../)
Detected
2026-10-12 21:45:42 198.51.100.11 /.env Protocol Attack 913100
Security scanner — User-Agent
Detected
2026-10-12 22:23:39 198.51.100.19 /?q=../../etc/passwd Protocol Attack 930100
Path Traversal (/../)
Detected
2026-10-12 21:12:12 198.51.100.34 /api/v1/login RCE 942100
SQL Injection via libinjection
Detected
2026-10-12 20:08:37 198.51.100.13 /wp-login.php SQL Injection 942100
SQL Injection via libinjection
Blocked
2026-10-12 20:15:36 198.51.100.31 /index.php?id=1 XSS 941100
XSS via libinjection
Detected
2026-10-12 20:02:26 198.51.100.23 /.env XSS 913100
Security scanner — User-Agent
Detected
2026-10-12 19:29:32 198.51.100.21 /xmlrpc.php SQL Injection 942100
SQL Injection via libinjection
Detected
2026-10-12 21:38:18 198.51.100.11 /admin/ LFI/Path Traversal 941100
XSS via libinjection
Blocked
2026-10-12 19:05:52 198.51.100.11 /.env Scanner 930100
Path Traversal (/../)
Blocked
2026-10-12 18:19:21 198.51.100.34 /wp-login.php XSS 942100
SQL Injection via libinjection
Detected
2026-10-12 20:33:48 198.51.100.19 /index.php?id=1 RCE 913100
Security scanner — User-Agent
Blocked
2026-10-12 16:55:23 198.51.100.34 /api/v1/login SQL Injection 930100
Path Traversal (/../)
Detected
2026-10-12 20:47:28 198.51.100.21 /admin/ Scanner 941100
XSS via libinjection
Detected
2026-10-12 15:43:12 198.51.100.13 /.env LFI/Path Traversal 930100
Path Traversal (/../)
Detected
2026-10-12 14:11:56 198.51.100.18 /index.php?id=1 XSS 930100
Path Traversal (/../)
Detected
2026-10-12 21:20:50 198.51.100.33 /index.php?id=1 XSS 930100
Path Traversal (/../)
Blocked
2026-10-12 16:05:00 198.51.100.25 /.env Protocol Attack 942100
SQL Injection via libinjection
Detected
2026-10-12 17:17:00 198.51.100.35 /index.php?id=1 SQL Injection 932100
RCE — Unix commands
Blocked
2026-10-12 20:47:32 198.51.100.21 /api/v1/login XSS 913100
Security scanner — User-Agent
Detected
2026-10-12 11:37:09 198.51.100.19 /wp-login.php SQL Injection 932100
RCE — Unix commands
Detected
2026-10-12 16:26:58 198.51.100.16 /api/v1/login Protocol Attack 942100
SQL Injection via libinjection
Detected
2026-10-12 10:55:28 198.51.100.17 /xmlrpc.php RCE 930100
Path Traversal (/../)
Detected
2026-10-12 21:08:12 198.51.100.32 /api/v1/login XSS 941100
XSS via libinjection
Blocked
2026-10-12 14:00:47 198.51.100.21 /?q=../../etc/passwd SQL Injection 942100
SQL Injection via libinjection
Blocked
2026-10-12 20:43:58 198.51.100.19 /xmlrpc.php Protocol Attack 913100
Security scanner — User-Agent
Blocked
2026-10-12 15:35:00 198.51.100.29 /.env Scanner 913100
Security scanner — User-Agent
Detected
2026-10-12 16:14:00 198.51.100.21 /xmlrpc.php LFI/Path Traversal 941100
XSS via libinjection
Detected
2026-10-12 20:55:40 198.51.100.22 /admin/ XSS 942100
SQL Injection via libinjection
Blocked
2026-10-12 07:16:42 198.51.100.18 /.env SQL Injection 941100
XSS via libinjection
Detected
2026-10-12 09:46:53 198.51.100.31 /index.php?id=1 SQL Injection 932100
RCE — Unix commands
Detected
2026-10-12 17:11:56 198.51.100.34 /wp-login.php RCE 942100
SQL Injection via libinjection
Detected
2026-10-12 16:12:51 198.51.100.15 /xmlrpc.php RCE 941100
XSS via libinjection
Detected
2026-10-12 17:25:06 198.51.100.35 /index.php?id=1 LFI/Path Traversal 930100
Path Traversal (/../)
Detected
2026-10-12 04:20:07 198.51.100.12 /xmlrpc.php Protocol Attack 930100
Path Traversal (/../)
Blocked
2026-10-12 12:27:48 198.51.100.23 /api/v1/login SQL Injection 942100
SQL Injection via libinjection
Detected
2026-10-12 07:55:36 198.51.100.14 /wp-login.php RCE 930100
Path Traversal (/../)
Detected
2026-10-12 02:48:04 198.51.100.25 /?q=../../etc/passwd Protocol Attack 942100
SQL Injection via libinjection
Blocked
2026-10-12 17:08:36 198.51.100.27 /index.php?id=1 SQL Injection 932100
RCE — Unix commands
Detected
2026-10-12 00:36:52 198.51.100.15 /api/v1/login Scanner 930100
Path Traversal (/../)
Blocked
2026-10-12 03:06:20 198.51.100.27 /?q=../../etc/passwd XSS 913100
Security scanner — User-Agent
Detected
2026-10-12 18:03:12 198.51.100.14 /admin/ XSS 942100
SQL Injection via libinjection
Detected
2026-10-12 12:19:52 198.51.100.18 /wp-login.php LFI/Path Traversal 941100
XSS via libinjection
Blocked
2026-10-12 00:03:56 198.51.100.17 /.env Scanner 930100
Path Traversal (/../)
Blocked
2026-10-12 07:21:12 198.51.100.14 /admin/ RCE 913100
Security scanner — User-Agent
Blocked
2026-10-12 07:32:18 198.51.100.16 /.env XSS 932100
RCE — Unix commands
Blocked
2026-10-12 00:26:06 198.51.100.31 /api/v1/login Scanner 932100
RCE — Unix commands
Blocked

A ModSecurity log viewer for the audit log

ModSecurity with the OWASP Core Rule Set blocks a great deal, and writes about all of it to an audit log in a format built for machines. This page turns that log into something readable: which requests were blocked, which rule fired, what the anomaly score was, and where the request came from.

The reason to look at this regularly is false positives. The Core Rule Set is deliberately strict, and at the default paranoia level it will block legitimate traffic in most real applications — file uploads, rich text editors, and anything that posts markup or SQL-like strings are the usual casualties. The pattern to look for is the same rule ID firing repeatedly against the same endpoint from many different addresses. That is not an attack, that is your own application being caught.

Whitelist narrowly when you find one: exclude the specific rule for the specific parameter on the specific path, not the whole rule and never the whole category. The page also lists the active rule set so you can confirm what is actually loaded after a change.