I got annoyed tweaking Cloudflare WAF rules—too many typos, wrong fields, and accidentally blocking legit traffic while chasing bots. So I threw together a tool over a weekend to make it brain-dead simple: the Cloudflare WAF Rule Generator (https://alivecheck.io/waf-generator).
It’s got two modes:
AI-driven: Type “block requests from Russia” or “stop SQL injection attempts,” and it spits out a clean rule. No docs diving required.
Manual builder: Dropdowns for fields (ip.src.country, http.request.method), operators (regex, equals, etc.), and values. Real-time rule generation.
You can copy rules with one click or save them with metadata. It’s free, no login nonsense. I’ve been using it to lock down endpoints and kill bot traffic without the usual trial-and-error pain.
Thoughts? Anyone else wrestle with WAF syntax enough to build their own fix? Open to feature ideas—I’m still iterating.
It’s got two modes:
AI-driven: Type “block requests from Russia” or “stop SQL injection attempts,” and it spits out a clean rule. No docs diving required. Manual builder: Dropdowns for fields (ip.src.country, http.request.method), operators (regex, equals, etc.), and values. Real-time rule generation. You can copy rules with one click or save them with metadata. It’s free, no login nonsense. I’ve been using it to lock down endpoints and kill bot traffic without the usual trial-and-error pain.
Thoughts? Anyone else wrestle with WAF syntax enough to build their own fix? Open to feature ideas—I’m still iterating.