Skip to Content
Browse documentation

Purge a UAPP Domain or URL Cache

Request account-scoped cache invalidation for a whole domain or an HTTP/HTTPS URL and understand the limits of server cache purging.

Open Hosting → Domains → Cache Purge.

Purge a URL

Website URL is required. Enter the intended HTTP or HTTPS address, including the path to refresh. The server assumes HTTPS if omitted, validates the scheme, checks that the hostname exists on the server and verifies account ownership. Its lookup removes a leading www. when identifying the owned domain.

Review the selected URL in the confirmation and submit. Check the result and reload the intended resource.

Purge a domain

The table shows Domain, Document Root and an action. Choose the domain's purge action, inspect the selected domain and confirm. The server verifies that the domain belongs to the signed-in hosting account.

Use the narrowest purge that meets the requirement. A whole-domain purge can temporarily increase origin work while content is regenerated.

Verify scope and outcome

Purging requests cache invalidation; it does not delete website source files, deploy new content or change DNS. It does not guarantee clearing a visitor's browser cache, an external CDN or an application's independent cache. Check the relevant layer when content remains stale.

The current Cache Purge view does not emit an explicit domain audit event. A missing activity row is therefore not proof that no purge was attempted.

See Domains overview for operational/demo caveats. Review errors before repeating a purge and test the exact resource after completion.