Shared SSL and Website HTTPS
Understand certificate coverage before using a shared hostname.
Understand certificate coverage before using a shared hostname.
Shared SSL is an older hosting arrangement in which a site may be accessed through a provider-managed secure hostname. It is different from a certificate covering your own domain. Before using any shared address, confirm that your current hosting service supports it and that the certificate matches the hostname.

HTTPS protects the connection to the hostname shown in the browser. A certificate for a server hostname does not automatically cover your business domain. Sharing a server IP address does not require every website to share one certificate.
For a public website, use HTTPS on the domain visitors expect to see. Treat a shared SSL address as a provider-specific option rather than a universal substitute for your own domain certificate.
Ask support whether shared SSL or a secure preview address is available for your account. Use the exact hostname and path supplied. Do not invent a secure hostname by replacing words in a server name or copying another provider’s example.
A legacy /~username/ address may be disabled or unsuitable for an application that expects its own domain. Your hosting welcome details and support team are more reliable than a guessed address.
In cPanel, look for SSL/TLS Status or the status tab within SSL/TLS Certificates. Check the required domain and www variant, certificate expiry and coverage. Available tools depend on the server and account features.
If AutoSSL is available, use the provided controls or ask support about issuance. The official status documentation explains how to inspect certificate details. Avoid assuming that every account has the same certificate provider.
Confirm that DNS points to the intended server and that required validation requests can reach it. Incorrect IPv6 records, restrictive CAA records or a proxy configuration can affect issuance and should be reviewed with the provider.
Use our DNS zone guide when checking records. Preserve existing mail settings and other services while correcting website records.
Visit the intended HTTPS address directly and inspect the certificate name and expiry. Test the homepage, login, forms and important application pages before adding a redirect from HTTP.
If the browser warns about certificate validity, stop and correct the cause. A shared SSL link is not ready for normal use merely because a warning can be dismissed. HTTPS also does not prove that the application itself is secure.
Review images, scripts and styles still requested over HTTP. Update the relevant application settings and stored URLs using tools appropriate for that application, with a backup before bulk changes.
If redirects loop, check the interaction between the application, server and any CDN. Decide which layer manages the redirect and make sure the application recognises the original connection scheme behind a trusted proxy.
Set a check for certificate expiry and confirm that automatic renewal works. Test again after a hosting move, DNS change or proxy change. Keep your public links and sitemap consistent with the preferred HTTPS domain.
Shared SSL can also change cookies, paths or redirects because the hostname differs. For production sites, ask DigitalBerg to help establish a domain-based certificate and a tested redirect plan.
Only if the certificate and server configuration actually support that address. Most domain certificates are intended for named hosts, so use the confirmed hostname instead.
Modern hosting commonly supports multiple domain certificates on a shared IP through SNI. Ask support about any special client compatibility requirements. If you are moving a site, include HTTPS checks in the migration plan.
For help with shared SSL, contact DigitalBerg with the affected domain, the step you tried and a redacted error message. Never include passwords, private keys or complete configuration files containing secrets.

