Innovate | Connect | Transform
ContactService statusUSD $

GICT knowledge base

Exclude Domains from AutoSSL Without Removing Working Certificates

Published

WHMcPanelSSL

Excluding a domain from AutoSSL stops that automation from managing the excluded name. It is not the same as uninstalling its current certificate, and removing a working certificate first is not required just to set an exclusion.

Plan the replacement coverage

Use an exclusion when another deliberate certificate-management route owns the name, not as a way to ignore a failing renewal. Check all names on a shared certificate, the alternative renewal process and affected website/mail services before changing coverage. An excluded name can become unusable after its existing certificate expires.

Exclude only the intended names

  1. Sign in to the correct cPanel account and find SSL/TLS Status, or the Status area in the newer unified SSL/TLS Certificates interface.
  2. Identify the exact names and current coverage. Where available, select those names and use the Exclude from AutoSSL action.
  3. If the action is missing, consult your host. Availability differs by version and configuration; do not run a server upgrade or edit global panel settings solely to reproduce an old screenshot.
  4. Reopen the status screen and confirm the exclusion. Verify the still-active certificate and your alternative renewal monitoring.

If certificate removal is actually intended

The older addon-domain uninstall guide is consolidated here because it described the same exclusion-then-removal task. Uninstallation is a separate, potentially disruptive operation in the certificate-management interface. Do it only after confirming the affected names/services and arranging replacement coverage or deliberately retiring the endpoint. Do not remove a shared certificate thinking it affects only one addon domain.

Restore AutoSSL management

Use the available Include during AutoSSL action for the intended names, or ask the administrator for the supported version-specific route. Confirm account eligibility and validation, run a scoped check, and verify the resulting coverage. Inclusion alone is not proof that a certificate was issued.

References: include/exclude workflow; version-dependent availability; separate certificate management.

Reviewed October 14, 2026. No exclusions, certificate removals or server upgrades were performed.

Related guides

Account services are unavailable until the production backend is configured.