Install a Website Certificate in Plesk with the Right Name Coverage

Plesk can manage a website’s certificate through its SSL/TLS tools and, where available, the SSL It! extension. Request only the names you intend to serve; a wildcard is an option with validation requirements, not a mandatory step for every domain.

Confirm access and prerequisites

Open the trusted Plesk link for your actual hosting subscription, then Websites & Domains > the intended domain > SSL/TLS Certificates. The old ASP.NET-specific portal route does not apply to every account. Confirm DNS, the existing certificate and the extension/features available on this server.

Issue or install

1. Choose the available free-issuance or existing-certificate route. Review the issuer terms before accepting them.
2. Select the main domain and any needed www, aliases or webmail names. Do not include unrelated names or assume website coverage secures the mail service.
3. If requesting a wildcard, complete the required DNS validation. External DNS can require a supported provider integration or manual record handling, with renewal implications.
4. Complete the request or upload the issued certificate and matching key/chain. Verify that the certificate is assigned to the intended hosting endpoint.

Verify the whole connection

Check the actual public hostname and certificate without bypassing warnings. Confirm its names, chain and validity, then test redirects, resources and forms. Verify separate mail assignments when applicable. A queued request, success banner or uploaded repository entry is not a substitute for checking the endpoint.

Confirm automatic renewal and monitor failures. Keep a backup before changing redirect or HSTS options; do not enable long-lived browser policy simply to complete a checklist.

Reference: Plesk SSL It! workflow.

Reviewed October 15, 2026. No Plesk subscription or certificate issuance was tested live.