# Rules

> Redirect rules answered at the edge, and per-name settings that give one name of a zone its own WAF, origin, limits or AI policy.

Rules change what the edge does for some requests or some names, without touching your origin:

- **Redirect rules** answer a redirect at the edge for a name and a path prefix, for example `old.example.com` → `https://example.com/`.
- **Per-name settings** give one name of a zone its own values (WAF level, origin port, access gate, rate limits, AI Crawl Control…) while it keeps inheriting everything else from the zone.
- **Effective configuration** shows exactly what the edge nodes receive for a name, after merging both.

- [Create your first redirect](https://developers.openwaf.dev/rules/get-started/): send a retired name to your main domain in a few minutes.
- [Redirect rules](https://developers.openwaf.dev/rules/redirects/): how rules match, build the destination and interact with HTTPS and `www`.
- [Per-name settings](https://developers.openwaf.dev/rules/per-name-settings/): override zone settings for one name and go back to inheriting.
- [Effective configuration](https://developers.openwaf.dev/rules/effective-config/): the merged site a name gets at the edge.
- [Redirect rule reference](https://developers.openwaf.dev/rules/redirect-reference/): fields, defaults and limits.


Edge rules for security (IP, country, WAF exceptions and rate limits) are documented in [WAF](https://developers.openwaf.dev/waf/rule-reference/). Every change is versioned; see [Change control](https://developers.openwaf.dev/change-control/).