Domain validation (DV)

SDH Multi-Domain SSL

Bring three eligible domain or subdomain names into one domain-validated certificate. This is a practical fit for a defined group of websites or services that share a certificate lifecycle without needing verified business details.

VALIDATION
Domain validation (DV)
COVERAGE
Three domain or subdomain names; extra SANs require a quotation.
ISSUING CA
SSL.com

Know the names you are securing

Three names, chosen deliberately.

SDH Multi-Domain SSL uses Subject Alternative Names (SANs) to cover three eligible domain or subdomain names. Each requested name needs to be listed and validated.

Certificate naming illustration for SDH Multi-Domain SSL: example.com.

example.com

One name for the main website.

Certificate naming illustration for SDH Multi-Domain SSL: example.org.

example.org

A second, different domain.

Certificate naming illustration for SDH Multi-Domain SSL: portal.example.net.

portal.example.net

A third name for a specific subdomain or service.

Coverage boundary

Three names are included. A www alias or another subdomain may consume a SAN according to the product rules. Extra SANs need a separate quotation; no unverified maximum or wildcard coverage is promised.

Ask about extra certificate names

Match the requirement

Where SDH Multi-Domain SSL fits.

Start with the addresses you need to protect and the identity checks your organization requires.

Illustration for SDH Multi-Domain SSL: Several related websites.

Several related websites

A small set of domains operated together, with someone responsible for validation and replacement across every endpoint.

Illustration for SDH Multi-Domain SSL: A named set of services.

A named set of services

A website, a portal and another eligible hostname that need one certificate with explicit name coverage.

Illustration for SDH Multi-Domain SSL: Multiple addresses without business validation.

Multiple addresses without business validation

An environment where domain-control verification is sufficient and organization identity does not need to appear in the certificate.

HTTPS encrypts data in transit between supported clients and a correctly configured server. It does not guarantee that a website is malware-free or replace secure application and server administration.

Before you begin

Have the right access and information ready.

Make a complete list of the three names, including any www aliases you need. Confirm that the servers can use the same certificate and that you can complete validation for every requested name.

Certificate request preparation for SDH Multi-Domain SSL.
  • Domain control. Access to an available CA-approved validation method for the requested names.
  • Compatible hosting. A server or hosting service that accepts a separately supplied certificate, with an administrator available to install it.
  • A certificate signing request (CSR). Your administrator generates it and keeps the corresponding private key secure.
  • A replacement plan. Someone responsible for later reissues, installation and manual renewal.

A CSR is request data, not a private key. Keep private keys, passwords, payment-card details and identity documents out of ordinary website enquiry forms.

A manual process, with clear responsibilities

How ordering works.

SDH coordinates your certificate order. The CA performs validation and issuance; your administrator handles installation.

  1. Choose coverage and term for SDH Multi-Domain SSL.

    Choose coverage and term

    Select the prepaid period for SDH Multi-Domain SSL. Review the full upfront total and confirm the names and validation requirements with SDH before proceeding.

  2. Prepare the certificate request for SDH Multi-Domain SSL.

    Prepare the certificate request

    Supply the CSR and a precise list of all three requested names. Ask SDH to check SAN use before assuming an alias is free or adding an extra name.

  3. Complete the CA's validation for SDH Multi-Domain SSL.

    Complete the CA's validation

    Each included name must pass the issuer's domain-control checks. A missing DNS or email approval for one name can hold up the combined certificate, so prepare all names before submission.

  4. Install and check HTTPS for SDH Multi-Domain SSL.

    Install and check HTTPS

    Your administrator installs the issued certificate and chain, configures HTTPS and checks the secured names. Later reissuance can require this step again.

A prepaid term is different from certificate validity.

Your selected 1 year prepaid period is paid in full upfront. It does not produce one certificate valid for an unrestricted period. CA and browser rules determine individual certificate validity. Later reissuance, validation and installation may be required within the prepaid subscription.

Understand the purchase

The certificate and the work around it.

Choose the right certificate coverage and agree any additional technical assistance separately.

Issued certificate materials for SDH Multi-Domain SSL.

Included with the selected certificate

  • Three agreed eligible domain or subdomain names in one certificate.
  • Domain validation for the named coverage, certificate files and the applicable chain.
  • Issuer-supported reissuance, with name changes checked against the product rules.

Browser and device trust depends on valid issuance, supported clients and correct server configuration. A site seal is available only where the issuer supplies and licenses one for the product.

Separate certificate administration work for SDH Multi-Domain SSL.

Not included in this purchase

  • Certificate installation or deployment to your servers.
  • Server repair, application fixes or mixed-content remediation.
  • Continuous certificate management or automatic expiry reminders.
  • Automatic renewal or a guaranteed future renewal price.
  • Extra SANs beyond the three included names; these need a separate quotation.

Plan for reissuance and renewal.

Changing the named set can require a reissue and new validation. Coordinate the replacement across all servers using this certificate; extra-name charges and any assistance are agreed separately.

Renewal is arranged manually; pricing will be confirmed before renewal. Reissuance is subject to the issuer's rules and does not include SDH installation labor or promise that every name change is free.

Frequently asked questions

More about SDH Multi-Domain SSL.

Prism Wings Dot counting three eligible certificate names.
Count every certificate name

List all three names before ordering. A www alias or subdomain can use a SAN; ask SDH about any extra names.

Are three domains plus their www names included?

Do not assume six names are included. A www alias can use a SAN depending on the certificate's rules. Send the exact hostname list so SDH can confirm coverage before issuance.

Can I request more than three names?

Ask SDH for an extra-SAN quotation. Additional-name pricing and the permitted maximum must be checked for this specific product before the request is accepted.

Does one approval validate every domain?

No. You must be able to satisfy the issuer's domain-control requirements for every requested name. Organization verification is not included with this DV product.

Is installation included with SDH Multi-Domain SSL?

No. The certificate purchase does not include installation, server repair, mixed-content fixes or continuous certificate management. Your hosting administrator installs and verifies the certificate; ask SDH about separately agreed assistance if needed.

Does a five-year purchase mean one certificate lasts five years?

No. The prepaid term is the purchased subscription period. Individual certificate validity is subject to CA and browser requirements, so you may need reissuance, validation and replacement installation during that period.

How will renewal be handled?

Renewal is arranged manually; pricing will be confirmed before renewal. New validation and issuance steps may be needed. The current prepaid price is not a promise of future renewal pricing or automatic renewal.

Compare the alternatives

Need to check your names or validation requirements?

Tell SDH what you need to secure. Include public hostnames and a short overview of the requirement.

Ask SDH for guidance