# Best way to disable crowdsec for specific domain?

**URL:** <https://discourse.crowdsec.net/t/best-way-to-disable-crowdsec-for-specific-domain/2817>\
**Category:** crowdsec\
**Created:** [May 26, 2026, 1:59am UTC](https://discourse.crowdsec.net/t/best-way-to-disable-crowdsec-for-specific-domain/2817 "2026-05-26T01:59:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![lexuzieel](https://dub1.discourse-cdn.com/flex013/user_avatar/discourse.crowdsec.net/lexuzieel/32/1411_2.png) [@lexuzieel](https://discourse.crowdsec.net/u/lexuzieel)\
**Post date:** [May 26, 2026, 1:59am UTC](https://discourse.crowdsec.net/t/best-way-to-disable-crowdsec-for-specific-domain/2817/1 "2026-05-26T01:59:02Z")

</div>

I have Crowdsec setup with Caddy and I am considering being able to enable/disable it for particular hosts (similar to how you can disable WAF in Cloudflare). I have stumbled upon this: [Allowlisting and Rule Overrides | CrowdSec](https://docs.crowdsec.net/docs/next/appsec/configuration_rule_management/#disable-appsec-for-a-specific-fqdn) but I suppose this would require to restart crowdsec (agent?)

Another option would be to split Caddy config into multiple sections and dynamically reload it with or without crowdsec, but I haven’t explored that further yet.

I was wondering, maybe you could share best practice of sort on how to achieve this?

Thanks for the great software, cheers!