Preparing and Validating a purchased SSL certificate

Step 1: Confirm the Required Domain Coverage

Before configuring your certificate, check the exact names you need to secure.

A certificate must cover the hostname visitors use. Do not assume that one certificate automatically includes every subdomain.

Step 2: Generate a Certificate Signing Request

A Certificate Signing Request (CSR) is generated through your hosting environment or certificate management system.

Generating a CSR also creates, or uses, a corresponding private key.

• Submit the CSR when requested during certificate configuration.

• Keep the private key secure.

• Do not send your private key in an email or support ticket.

If you are unsure where to generate the CSR, contact our support team before proceeding.

Step 3: Complete Domain and Organisation Validation

The certificate authority must verify your control of the requested domain names. For OV and EV certificates, it must also verify information about your organisation.

Domain Validation — Required for All Certificate Types

Depending on the product and certificate authority, domain validation may use:

• DNS validation: Add the specified verification record to your domain’s authoritative DNS zone.

• File validation: Upload the supplied verification file to the specified location on your website.

• Email validation: Approve the request through an eligible email address offered by the certificate authority.

Follow the instructions supplied for your order exactly. DNS record names, values, and verification-file contents must not be guessed or altered.

Organisation Validation — OV Certificates

In addition to domain validation, the certificate authority will typically:

1. Verify your organisation’s legal existence. Your registered business name and registration details are checked against official or other accepted sources.

2. Verify your business address and telephone number. These details must be supported by sources accepted by the certificate authority.

3. Confirm the applicant’s authority. An authorised representative may need to confirm that the organisation requested the certificate.

4. Complete a verification call or other approved confirmation. The certificate authority may contact your organisation using an independently verified telephone number.

You may be asked to provide business registration documents or other evidence if the required information cannot be verified independently.

Extended Validation — EV Certificates

EV certificates require more extensive organisation checks. The certificate authority will typically:

1. Verify the organisation’s legal identity and registration status.

2. Verify its physical address and operational existence. Additional evidence may be requested where public records are insufficient.

3. Verify the authority of the people involved in the application. This may include the person requesting the certificate and the person approving the certificate agreement.

4. Obtain approval of the certificate request and agreement from an authorised representative.

5. Complete a final verification call or other approved confirmation using independently verified contact information.

How to Avoid Validation Delays

• Use your organisation’s full registered legal name.

• Ensure the business information on your application matches your supporting records.

• Make sure the authorised contact is available to respond to verification requests.

• Submit documents only through the method specified by the certificate authority.

Important: Exact requirements vary by certificate authority and product. Issuance takes place only after all required checks have been completed successfully.

Step 4: Install the Issued Certificate

After issuance, install the certificate in the hosting environment that serves your website, together with the matching private key and any required intermediate certificates.

A certificate purchase alone does not enable HTTPS; installation and website configuration must also be completed.

Step 5: Test Your Website

Confirm that:

• The certificate covers the correct hostname.

• The browser shows no certificate warnings.

• HTTPS pages load correctly.

• HTTP redirects to HTTPS where intended.

• Forms, logins, and checkout functions still work.

Renewal reminder: Unless your service explicitly includes automated renewal and deployment, check whether renewal requires fresh validation and installation of a replacement certificate.