Command-line options
whatwaf supports several options to customize scan behavior:URL argument
Target URL to check for WAF detection. Must include the protocol (http:// or https://).
Options
Per-request timeout in seconds. Controls how long to wait for each HTTP request before timing out.Use a higher timeout for slow servers or networks. Use a lower timeout for faster scans when you know the server is responsive.
Follow HTTP redirects. When enabled, whatwaf will follow 301/302 redirects to the final destination.This is useful when the target URL redirects to a different domain or path where the WAF is actually deployed.
Route requests via this proxy. Supports HTTP and SOCKS proxies.Common use cases:
- Route traffic through Burp Suite or other intercepting proxies
- Use a VPN or anonymization proxy
- Debug requests by capturing them in a proxy tool
List recognized WAFs. When this flag is set, whatwaf displays all WAF signatures it can detect and exits without scanning.When using this flag, you do not need to provide a URL.
Option combinations
You can combine multiple options in a single command:- Use a 30-second timeout per request
- Follow HTTP redirects
- Route all traffic through a local proxy
- Scan https://example.com