OV Wildcard SSL - SSL certificate for your website
If a company runs several services on one domain and it matters to customers that they can verify the owner, OV Wildcard SSL is the right fit. It protects first-level subdomains of the form *.example.com, and the organization's details are confirmed by the certificate authority before issuance. Leneex takes your order, tells you which details to prepare, and helps install the certificate on your server. Timelines depend mainly on organization validation, so it's best to place your order in advance.
- Trusted by browsers: 99%+ compatibility
- HTTPS supports your search rankings
- Customer data sealed with encryption
- Free installation
Three Reasons to Choose OV Wildcard SSL
Order OV Wildcard SSL for website
A vetted organization and every first-level subdomain at once.
Specifications
- Price, per year
- €185.99
- Renewal, per year
- €199.99
- Secures
- 1 website + all one level subdomains
- Domains
- Wildcard
- Validation
- OV
- Assurance level
- High
- Available to
- Companies
- Paperwork
- Needs paperwork
- Domain examples
- mysite.com, www.mysite.com, login.mysite.com, mail.mysite.com
- Local domains
- Not supported
- Mobile browsers
- Supported
- Money-back, days
- 15
- Warranty
- €250 000
- Browser support, %
- 99.9
- Reissues
- Free, unlimited
- RSA key length, bit
- from 2048
- Encryption, bit
- up to 256
Four steps to your OV Wildcard SSL for website
Make sure all the addresses you need are first-level subdomains. If you need different domains, look at Multi-Domain.
Enter the domain, organization name, address, and registration details. Check them against the registry to avoid unnecessary requests.
Add the DNS record shown in your dashboard and wait for the certificate authority to validate the company. If documents are needed, a manager will let you know.
Installing an OV Wildcard SSL certificate is done on every server with subdomains, after which you check that all addresses open over HTTPS. Leneex support will help with the setup.
SSL questions, answered
Short and to the point: certificate types, CA warranty and installation. Can't find your answer? Write to us in chat.
Standard Wildcard confirms only domain ownership and doesn't show organization details. OV Wildcard additionally validates the company: its name appears in the certificate details, and issuance takes longer.
A certificate for *.example.com protects all first-level subdomains, for example shop.example.com and mail.example.com. It does not cover second-level subdomains (a.b.example.com). Check the product description to see whether the main domain is included.
The domain is validated through DNS: add the record shown in your Leneex dashboard to the zone. File-based validation on the site doesn't work for wildcard names. The certificate authority validates the organization using public registries.
From one to several business days. Most of the time goes to organization validation, while the DNS record is confirmed faster. To avoid delaying your launch, prepare your company details in advance.
As a rule, data from public registries is enough, but sometimes the authority asks for incorporation documents or phone confirmation. A Leneex manager will let you know if anything else is needed.
Yes, if all the servers serve subdomains of the same domain: the certificate and key are installed on each of them. After a reissue, the files will have to be updated everywhere. Transfer the private key only over a secure channel: if it leaks, you'll need to reissue the certificate and revoke the old one. Limits on the number of servers depend on the license; see the product page.
Yes, Leneex issues an invoice to legal entities and provides closing accounting documents. Visa and Mastercard cards are also accepted. Renewal is handled in your account dashboard, and if the organization's details haven't changed, revalidation often goes faster.
Question 01
How does an OV Wildcard SSL certificate differ from Standard Wildcard?
Standard Wildcard confirms only domain ownership and doesn't show organization details. OV Wildcard additionally validates the company: its name appears in the certificate details, and issuance takes longer.
OV Wildcard SSL combines two properties that are usually chosen separately: protecting all subdomains with one certificate and validating the owning organization. In an entry like *.example.com, the asterisk stands for any first-level subdomain, so shop.example.com, account.example.com, and api.example.com are all covered by one file.
Features of an OV Wildcard SSL Certificate
Before issuing the certificate, the certificate authority checks that the company exists and that the applicant has the right to act on its behalf, as well as control of the domain. The organization's name is then listed in the certificate details. Because of this validation, you should allow from one to several business days to get the certificate.
An OV Wildcard SSL certificate for a website is convenient as a project grows: a new first-level subdomain is covered by the certificate without a reissue. All that's left is to configure the host itself on the server. Keep the flip side in mind too: HTTPS won't turn on by itself on your servers; the certificate has to be installed everywhere subdomains run.
OV Wildcard or Standard Wildcard: What's the Difference?
Both certificates protect first-level subdomains and encrypt the connection equally. The only difference is validation. Standard Wildcard is a DV type: the authority only has to confirm domain ownership, so issuance takes minutes and the certificate contains no organization details.
OV Wildcard adds company validation and shows the company's name in the certificate. If speed matters and you don't need documents, choose Standard Wildcard. If customers and partners need to verify the owner, OV Wildcard is the right fit.
Don't confuse Wildcard with Multi-Domain: the first covers subdomains of one domain, the second covers several different domains. EV isn't available in this format: certificate authority rules don't allow wildcard names in EV, so for subdomains with organization validation, OV is what's left.
To keep your order from being delayed, prepare the following:
What to prepare | Why it's needed | Notes |
|---|---|---|
Organization details: name, address, registration number | For validation by the certificate authority | Check the spelling against the registry; discrepancies trigger additional requests |
Access to the domain's DNS zone | To confirm domain ownership | File-based validation on the site doesn't work for wildcard names |
List of subdomains | To make sure they are all first-level | The certificate doesn't cover addresses like a.b.example.com |
Contact details of an authorized employee | To confirm the applicant's authority | The authority may request confirmation by phone |
Access to servers | To install the certificate | It has to be installed on every server with subdomains |
Who Is OV Wildcard SSL For
Companies choose this certificate when several services run on one domain and a verified owner matters for customer trust. It's suitable for:
online stores whose catalog, customer account area, and API are on separate subdomains;
corporate portals with internal services such as mail.example.com and crm.example.com;
B2B platforms where customers log in to their accounts on their own subdomains;
companies with test and production environments on different subdomains;
financial and professional organizations that need to show the real owner of the site.
If your project runs on one domain with no subdomains, there's no need to pay extra: DV or OV will do. If you need different independent domains, look at Multi-Domain. The choice depends not on the size of the site but on the structure of your domain names and the validation level you need.
Before you buy an OV Wildcard SSL certificate, list all your subdomains and make sure they are first-level. The certificate doesn't cover addresses like a.b.example.com; you'll need a different option for those.
Make Leneex Your Choice
The current price of an OV Wildcard SSL certificate is listed on the product page. To get one, you need to validate the domain with a DNS record and give the certificate authority your organization's details: name, address, and registration information.
At Leneex, you get:
help choosing a certificate and preparing your organization's details;
help from engineers with installation on Nginx or Apache for several virtual hosts;
payment by Visa and Mastercard cards and, for legal entities, an invoice and closing accounting documents;
an account dashboard for renewing and reissuing your certificate;
one certificate instead of a separate purchase for each subdomain.
Still have questions? Write to us through any convenient channel. We'll help you choose and install the certificate that's right for your project.