Remove a subdomain only after its application or staging environment is no longer required. The action can delete the subdomain hosting configuration and related content, while external DNS, certificates and application references may need separate cleanup.
IN THIS ARTICLE
Prepare for the change
Confirm the exact full hostname and document root. Check whether that directory is shared with another site and whether databases, scheduled tasks or integrations still depend on the subdomain. Keep a verified backup of anything that may be needed later.
01 Remove an unused subdomain from Plesk
- Open Websites & Domains and locate the subdomain under the correct parent domain.
- Review its hosting settings and record the directory and dependencies. Retire application jobs and move required data before removing the endpoint.
- Use the subdomain removal action and read the confirmation scope. Stop if it would affect content shared with a site that must remain live.
- Confirm removal of the exact subdomain. Do not select the parent domain or neighbouring subdomains in a bulk action.
- Review external DNS, application links, monitoring checks and obsolete credentials. Remove unused records and secrets only after confirming they are no longer part of another service.
How do I check the result of subdomain removal?
Confirm the subdomain is absent from Plesk and the parent site still works. Check that an old hostname no longer points to an unintended hosting destination. A cached DNS response can persist for its earlier TTL.
If the change does not work
If another site loses content, restore the approved recovery copy and review the shared-directory relationship before attempting further cleanup. If the old site still appears, inspect DNS and browser or proxy caches. Recreating the subdomain name does not by itself restore deleted files, databases or previous configuration.