Choosing which cPanel hostnames AutoSSL should manage

AutoSSL inclusion determines which eligible hostnames participate in automatic certificate management. Excluding a hostname can stop future automated issuance or renewal for it, so use exclusions only as part of a deliberate certificate plan.

01 Information to have ready

List the hostnames actually served from the account and identify any managed by another certificate process. Check current certificate expiry before changing inclusion, especially for mail or application names that users still depend on.

02 Choose which cPanel hostnames AutoSSL should manage

  1. Open the available SSL/TLS Status interface and review the hostname list and certificate details.
  2. Where controls are exposed, select the intended hostnames and choose the include or exclude action. Do not exclude every failing name just to remove warnings without understanding why it fails.
  3. Be aware that current unified SSL/TLS Certificates Status hides AutoSSL actions. Ask support about the standalone or provider-managed controls if they are unavailable.
  4. For included names, ensure DNS and domain validation can reach the correct service. For excluded names, document the alternative renewal owner and process.
  5. After any issuance run, inspect coverage and expiry for all essential hostnames, not only the primary domain.

03 Confirm the expected result

The selected inclusion policy should match your certificate-management plan. Existing certificate coverage and future renewal responsibility must both be clear.

04 Example: diagnose one hostname that remains unsecured

If AutoSSL secures your primary domain but not an alias, compare the failing hostname with a working one. Check whether it is included in the selected certificate scope and whether its public DNS reaches the intended service.

Review the exact validation result before changing records. An outdated IPv6 record, a proxy route or a restriction on the validation path can require a different correction from a misspelled hostname. Do not delete all certificate settings or point unrelated mail records elsewhere as a shortcut.

What counts as a successful check?

After the issue is corrected and certificate issuance completes, open the specific failing hostname over HTTPS. Inspect the certificate served and confirm the name is covered. A green result for another hostname is not proof that this one is secured.

Keep track of names that are intentionally excluded or managed by a different certificate system. Send us the domain, affected hostname and exact AutoSSL diagnostic when you need help. Avoid repeatedly forcing new requests without resolving the reported problem. We can help review the validation route while preserving working certificates on the rest of the account.

Does excluding an AutoSSL hostname delete its website or certificate?

Exclusion does not itself remove DNS, delete the website or guarantee immediate certificate removal. If an excluded hostname is still active, arrange a valid replacement before its current certificate expires. Re-include an accidentally excluded name and correct validation prerequisites before requesting another run.

  • 0 Users Found This Useful
  • cpanel-whm, security-ssl
Was this answer helpful?

Related Articles

Getting a free HTTPS certificate for a cPanel website

An eligible cPanel website can use the server’s AutoSSL service to obtain and renew a...

Generating a certificate signing request in cPanel

A certificate signing request, or CSR, contains the public-key and identity information needed...

Finding and copying an existing CSR in cPanel

You can retrieve a previously generated certificate signing request from cPanel when a...

Deleting an unused CSR from cPanel

Deleting a stored CSR removes that request from cPanel’s request list. It does not revoke an...

Retrying AutoSSL after fixing a certificate-validation problem

An AutoSSL retry is useful after correcting the reason a hostname could not be validated....