The SSL Manager is where you attach an existing certificate to each domain (and see what hostnames it covers). If you need to create or import a certificate, use SSL Certificates first, then return here to select it.

Who can use this

The signed-in account owner. Resellers/admins can manage SSL for your account as well.

Before you start

• Make sure your domain’s DNS A/AAAA records point to this server (for example.com, www.example.com, etc.).
• Issue or import a certificate in SSL Certificates (AutoSSL or custom).
• Wildcard certs (e.g., *.example.com) cover all first-level subdomains, but not the bare/root (example.com) unless the cert also lists it.

What you see on this page

• A table of your domains (main, addon, parked, subdomains).
• SSL Coverage shows a quick check of common hostnames for that row:
  — covered by a valid CA-issued certificate
  — covered by a self-signed certificate
  — not covered by the selected certificate
• Active SSL Certificate is a dropdown listing certificates that appear to match the domain (including SANs/wildcards).

How to attach a certificate (step-by-step)

1) In SSL Certificates, create/renew/import the certificate you plan to use.
2) Come back to SSL Manager and find your domain in the table.
3) Open Active SSL Certificate and pick the right one (look at the Common Name / wildcard and issuer).
4) Check SSL Coverage icons. Green locks mean the selected cert matches those hostnames for this domain.

What “coverage” includes

• For main/addon/parked domains: example.com, www.example.com, mail., webmail., shm., ftp..
• For a subdomain row (e.g., blog.example.com): the check focuses on that subdomain and its www. alias.

Tips for choosing the right cert

• If you serve multiple subdomains, a wildcard (e.g., *.example.com) is convenient.
• To cover the root domain (example.com), the cert must explicitly include it (wildcards don’t cover the root).
• If your mail or webmail points to another server/provider, coverage here may show red for those hostnames—that’s normal unless mail is hosted here.

Troubleshooting

• Red lock after selection: the SAN/wildcard doesn’t match that hostname. Reissue with the correct names or choose a different cert.
• Certificate not listed: add/import it in SSL Certificates, or wait a moment after issuing AutoSSL.
• Still not secure in browser: clear CDN/proxy cache, confirm DNS points here, and ensure you picked the cert on this page for the exact domain.
• CAA errors during issuance: add a CAA record that allows your CA (e.g., letsencrypt.org) in DNS Manager.

Good practice

Renew before expiry, keep DNS stable during issuance, and prefer a single certificate that cleanly covers all names you actually serve from this server.