Manage ModSecurity Domain Protection in UAPP
Review protected and disabled websites, filter the account list and confirm per-domain ModSecurity status changes in UAPP.
Open ModSecurity → Domain Protection.
Review websites
The summary shows Total Websites, Protected and Disabled. It counts the returned account website list rather than only rows matching the current table filter.
The table includes:
| Column | Meaning |
|---|---|
| Website | Hosted website name, with a link to the site. |
| Document Root | Website directory displayed relative to the account home where applicable. |
| Domain Type | Primary, Addon, Alias or Subdomain. |
| Web Application | Configured application description or identifier. |
| Protection Status | Protected/Disabled badge and its change switch. |
Use search and sorting to find a website. Choose All statuses, Protected or Disabled to filter, and use the row-count control for 25, 50, 100 or all rows.
The data endpoint treats a missing recorded ModSecurity value as enabled. The badge therefore reports configured state, not a runtime inspection test.
Enable protection
- Locate the website and select its protection switch.
- Verify the website in Enable ModSecurity.
- Select Enable Protection, or cancel.
- Read the result, refresh and test normal application requests.
The confirmation explains that ModSecurity will inspect requests using the server's configured integration and rules.
Disable protection
- Identify why disabling is needed and record the current state.
- Select the website's switch.
- Verify the website and read the warning in Disable ModSecurity.
- Select Disable Protection, or cancel.
- Test the affected operation and restore protection when troubleshooting is complete.
Selecting a switch opens confirmation and restores its current visual state while confirmation is pending. It does not apply the change until confirmed.
Check the website before confirming
The change affects the selected website's ModSecurity setting. Disabling removes its ModSecurity rule protection; it does not correct the underlying application or rule-compatibility issue.
Fields and validation
The submitted website is required, validated as a domain and checked against the signed-in account's ownership. The requested status is required and accepts on or off. There is no free-text rule, rule-ID or exclusion field.
Results and troubleshooting
The backend records the new website setting, then requests a virtual-host rebuild. A successful panel message is not a complete application/security test. Test representative requests after a change.
If rebuilding fails, the newly recorded setting can remain. Refresh before retrying and ask the provider to inspect effective configuration; do not assume automatic rollback.
For blocked legitimate requests, give the provider the website, timestamp, URL path and operation needed to reproduce the problem without disclosing private content. This page does not expose rule logs or selective exclusions. Prefer a provider-reviewed correction over leaving protection disabled indefinitely.