
example.com
The base domain associated with the wildcard certificate.
Domain validation (DV)
Use domain validation for one base domain and its eligible first-level subdomains. This wildcard option fits a growing set of services under the same domain when you do not need organization identity checks in the certificate.
Know the names you are securing
SDH Standard Wildcard SSL is for eligible names directly beneath one base domain. Plan the hierarchy before choosing it: wildcard coverage has a specific depth.

The base domain associated with the wildcard certificate.

An eligible first-level subdomain, like mail.example.com.

A deeper name; it is not automatically covered by *.example.com.
A wildcard for example.com does not cover another domain such as example.org or every deeper level of subdomains. Confirm the exact base-domain coverage and server requirements before ordering.
Match the requirement
Start with the addresses you need to protect and the identity checks your organization requires.

A website with shop, mail or portal hostnames directly beneath the same base domain.

A service structure where eligible first-level subdomains are added over time and a shared certificate process is appropriate.

A team that can complete the issuer's accepted wildcard validation method and coordinate deployment across its servers.
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
Check the whole hostname hierarchy and confirm that your administrator can complete the CA-approved wildcard validation method, often involving DNS. Do not assume every domain-validation method is available for wildcard requests.

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
SDH coordinates your certificate order. The CA performs validation and issuance; your administrator handles installation.

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

Have your administrator generate the appropriate wildcard CSR, confirm the base domain, and check which first-level services will receive the certificate.

Prove control of the wildcard's base domain through an issuer-approved method available for this request. The validation method and a correctly prepared request affect progress; no issuance time is guaranteed.

Your administrator installs the issued certificate and chain, configures HTTPS and checks the secured names. Later reissuance can require this step again.
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
Choose the right certificate coverage and agree any additional technical assistance separately.

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.

A wildcard certificate can be used across several services, so certificate or key replacement needs coordinated deployment. Protect private keys and confirm your server setup before reusing or replacing a certificate.
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

A wildcard covers eligible first-level subdomains of one base domain. Deeper names and other domains need a different plan.
No. A wildcard for *.example.com can cover eligible names such as shop.example.com. It does not automatically cover app.shop.example.com, and it does not cover an unrelated base domain.
This is a DV wildcard certificate. SDH OV Wildcard SSL is the listed alternative when you need organization verification with eligible first-level wildcard coverage.
No. Each relevant server must be configured correctly. Certificate installation, deployment coordination and remediation are not included in the certificate purchase.
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.
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.
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
Tell SDH what you need to secure. Include public hostnames and a short overview of the requirement.