Recent Attacks Submitted:

Client IP: 172.29.133.63 ()
Payload: %3Cscript%3Ealert(21)%3C/script%3E
Client IP: 172.29.133.63 ()
Payload: dsadas
Client IP: 172.29.133.63 ()
Payload: <scr\x00ipt>confirm(0);</scr\x00ipt>
Client IP: 172.29.133.63 ()
Payload: <scr\x00ipt>confirm(0);</scr\x00ipt>
Client IP: 172.29.133.63 ()
Payload: echo
Client IP: 172.29.133.63 ()
Payload: YourPayloadHere
Client IP: 172.29.133.63 ()
Payload: YourPayloadHere
Client IP: 172.29.133.63 ()
Payload: YourPayloadHere
Client IP: 172.29.133.63 ()
Payload: http://endive.in/projects/invoice_codeigniter/
Client IP: 172.29.133.63 ()
Payload: YourPayloadHere//
Client IP: 172.29.133.63 ()
Payload: YourPayloadHere
Client IP: 172.29.133.63 ()
Payload: YourPayloadHere
Client IP: 172.29.133.63 ()
Payload: YourPayloadHere
Client IP: 172.29.133.63 ()
Payload: YourPayloadHere

ModSecurity Core Rule Set (CRS)

Current CRS Version - 3.0.0-dev

Please feel free to inject malicious input to stress test the ModSecurity Core Rule Set (CRS). Requests should be directed to www.modsecurity.org/demo/demo-deny.html with attacks being placed within the "test" parameter. The form accepts both GET and POST request methods. You can either do this via the form below or manually.

The data submitted in the page will be sent to a ModSecurity CRS install for inspection and processing. The response page will report any CRS events that triggered.

If you send an attack payload that is not detected by the CRS, please notify us at any of the following places:

- @ModSecurity on Twitter

- OWASP ModSecurity Core Rule Set Mail-list

- Submit bug report to GitHub

 method=GET enctype=application/x-www-form-urlencoded

Results (txn: (none))

(none)

All Matched Rules Shown Below

Return to demo page

Submit an Evasion Report to GitHub