Secure a UKC website
The right SSL route depends on where the website is hosted
Current UKC shared hosting includes free Let’s Encrypt certificates managed through Plesk. A parked domain can use the optional Domain Parking SSL add-on to secure its parked website and protect web forwarding. External platforms issue certificates under their own process.
Which SSL certificate route should I use?
| Website location | Recommended route |
|---|---|
| UKC shared hosting | Issue a free Let’s Encrypt certificate in Plesk and secure the domain, www and any required service names |
| UKC parked domain | Order Domain Parking SSL from the domain service when the parked page or forwarding source needs HTTPS |
| External website platform | Follow that platform’s domain connection and certificate process |
| Special certificate requirement | Ask Support before ordering so the validation and installation route is confirmed |
How do I enable SSL on shared hosting?
- 1Point the domain correctly
The names being secured must resolve to the hosting service so certificate validation can reach it.
- 2Open SSL/TLS Certificates
Sign in to Plesk, open the domain and choose the Let’s Encrypt option.
- 3Select the required names
Include the bare domain, www and supported mail or webmail names only when their DNS is correct.
- 4Test and redirect
Confirm HTTPS loads without a warning before forcing all visitors from HTTP to HTTPS.
How does Domain Parking SSL work?
It secures the parked address
The add-on allows visitors to connect securely to the UKC parked website before viewing the page or receiving a redirect.
It is automatically provisioned
After purchase, provisioning normally completes within a few minutes. DNS must still point to the UKC parking service.
It protects forwarding
HTTPS must connect to the source domain securely before the browser can follow its forwarding response.
It does not secure another server
The final website or mail service needs its own valid certificate at the platform where that service runs.
Why is the browser still warning?
The certificate does not match the name
Check the exact hostname in the browser. The certificate must include that name, such as the bare domain or www version.
The certificate was issued but HTTP still loads
Certificate installation and HTTP-to-HTTPS redirection are separate. Test HTTPS first, then enable the appropriate redirect.
Validation failed
Confirm DNS points to the service performing validation, remove conflicting records and temporarily review restrictive proxy or security settings.
Email shows a certificate warning
Website SSL does not automatically cover every mail hostname. Use the server name supplied for the mailbox service.
Secure the correct service
Confirm where the site runs before ordering or issuing SSL
That avoids buying the wrong product or validating against the wrong server.