GICT knowledge base
Ordering an SSL/TLS Certificate for an InterServer Service
Published
Before ordering a paid SSL/TLS certificate for an InterServer service, confirm the certificate features you need and the options available for your actual hosting account. The prices and panel limitations previously listed in this article were dated February 2014 and are not current offers.
Check whether a paid order is necessary
Look in your hosting control panel for certificate status and available automatic issuance. Availability depends on the service and its configuration; this guide does not promise free automatic certificates on every plan. Use a paid certificate when its identity validation, provider support or other documented features meet a requirement that your available alternative does not.
List all required names
Write down the exact hostnames, such as example.com, www.example.com and mail.example.com. Read the proposed certificate’s subject alternative names rather than assuming a product name covers them all. A wildcard such as *.example.com does not automatically cover example.com or a.b.example.com; those need appropriate additional coverage.
Confirm the quote and validation route
- Sign in to the InterServer customer portal. If no suitable certificate-order option is available, open a support ticket before paying elsewhere or generating a new key.
- Confirm product availability, current price, term, renewal terms, validation level and exact hostname coverage. Do not rely on the retired AlphaSSL/DomainSSL prices in the old article.
- Follow the issuer’s current domain-control validation instructions. Possible routes include DNS, HTTP or approved email addresses, depending on the product. Do not assume that a WHOIS email or a 30-minute approval guarantee applies.
- Generate or retain the required private key securely through your actual panel or certificate workflow. A CSR is intended for the issuer; the matching private key is not. Never paste the private key into an ordinary support message or public page.
Installation and follow-up
Confirm who will install the certificate and chain on the endpoint and how renewal will be handled. Modern shared web hosting with Server Name Indication can serve different certificates on one IP; a dedicated IP is not a universal website requirement. Legacy clients and non-web services can have different constraints.
After installation, verify every required hostname without bypassing warnings, check redirects and mixed content, and monitor expiry. Purchasing a certificate alone does not configure HTTPS, redirect HTTP or prove recovery from a failed renewal.
References: cPanel SSL/TLS management; SNI and wildcard coverage; domain-control validation examples.
Reviewed October 14, 2026. Current portal prices and product availability were not independently verified; obtain a current quote.
Related guides
How to Manage Let’s Encrypt SSL Certificates with Certbot Commands
Learn to manage Let's Encrypt SSL certificates using Certbot commands for installation, renewal, and configuration to keep your site secure.
SSLSSL/TLS Certificates: Coverage, Hosting Setup and HTTPS Checks
Choose SSL/TLS certificate coverage and check hosting setup, private keys, HTTPS redirects and renewal without unsupported plan-wide promises.
SSLHow to Fix the NET::ERR_CERT_AUTHORITY_INVALID Error
The NET::ERR_CERT_AUTHORITY_INVALID error can be caused at the client side as well as the server side. Learn how to solve this error using our in-depth guide.
SSLUse Really Simple Security for a Controlled WordPress HTTPS Change
Review Really Simple Security HTTPS tools, existing certificate ownership and redirect methods, then test WordPress without blanket security promises.
