Terms for Using the Generated Rules

What You Agree to When You Use This Tool

Using the rule generator means accepting these terms. Even a small free tool needs its expectations written down, particularly one that produces server configuration.

No warranty on the output

The rules are generated from your selections and provided as is. Apache behaviour depends on the version, the loaded modules, the main server configuration, and whatever else already sits in your file. This tool sees none of that. A block that works perfectly on one host can loop, 403 or 500 on another.

So test on staging, keep a backup of the file you replace, and check the live result yourself. The operator of this site is not liable for downtime, lost traffic, lost revenue or any other loss that follows from using the output.

Security rules are a floor, not a ceiling

Blocking sensitive filenames, disabling directory listing and adding response headers all raise the cost of an attack. None of them make a site secure. They do not replace patching, sensible file permissions, or keeping secrets out of the web root in the first place, and a generated Content-Security-Policy is a starting point that has to be tested against every template you serve before it means anything. Apache's own security tips are the right next read.

Your responsibilities

Use the tool lawfully. Apply the output to servers you own or administer, and do not point the access control or hotlink rules at a service you have no authority over. Beyond that the generated file is yours: use it, change it, ship it in commercial work, no attribution needed.

Changes and contact

These terms may change as the tool grows, and the effective date above moves when they do. Questions go to the contact page. Data handling is set out in the privacy policy, and the about page explains the client-side design that both of those depend on.