SSL / TLS
RapidSSL Wildcard
1 Year₵2,335.75/yr
2 Years₵2,155.47/yr
3 Years₵2,058.80/yr
Your shop, your portal, your mail service. Give matching subdomains an encrypted home with a wildcard certificate designed to grow with your domain.
Keep your services connected under one domain while choosing the certificate scope that fits your architecture.
A wildcard such as *.yourdomain.com covers matching subdomains at that level, including shop.yourdomain.com and portal.yourdomain.com.
Deeper names such as team.portal.yourdomain.com need the appropriate additional coverage. Check the selected certificate’s exact scope.
If a certificate is deployed across several services, manage its private key, installation and renewal carefully on each server.
A wildcard matches subdomains at its specified level. When your services share that naming pattern, the certificate can give them a common scope without listing every matching subdomain individually.
For a wildcard name of *.example.com, the asterisk replaces one label. Check any additional names included in the product and issued certificate.
A certificate used across services deserves a clear installation record. Know where each copy is deployed and how its private key is protected, so a replacement reaches every endpoint that needs it.
Think through your domain structure before you buy. Wildcard coverage fits a naming strategy, not every possible domain arrangement.
A shop, portal and help centre can sit at the same level under your domain. Match the certificate to the actual public names you use.
Document which hostnames are covered and which use another certificate. Shared scope becomes easier to manage when ownership is clear.
A new matching name can use the wildcard certificate after correct installation. Deeper names and different domains need a separate coverage decision.
Understand validation, coverage and what happens after you choose your certificate.
SSL Certificates enable data encryption on the internet and allow data to be transmitted securely from a web server to a browser. With SSL, your website can use the https protocol and will display a padlock in end users web browsers to indicate the connection is secure.
SSL Certificates are an essential part of the internet. They not only encrypt communication between your computer and the server where a website is located, but they also provide verification that a site is what it claims to be.
There are 3 different levels of vetting that SSL Certificates are based upon. Domain Validated (DV) , Organization Validated (OV), and Extended Validation (EV). The major difference between the types of certificate relates to the information the Certificate Authority, RapidSSL, GeoTrust and DigiCert, requires and validates in order to issue a certificate. The higher levels of certificate require more information, and often is displayed in the browser bar. EV SSL for example turns the browser bar green and displays the organization name to visitors to generate more trust.
A Wildcard SSL certificate provides the same encryption and authentication features as other SSL certificates but can also be applied to an unlimited number of subdomains of a website. A Wildcard SSL certificate supports the root domain (example.com) as well as its subdomains.
EV or Extended Validation certificates are the highest class of SSL available and give the most credibility and trust to your website. EV assures consumers that their personal and financial information is protected at the highest levels of authentication. Additional verifications are performed, such as corporate agency record checks, applicant contact info, and whether the business has existed for a minimum of 3 years. EV certificates are best suited for business-critical webpages.
It matches a single subdomain label under example.com, such as shop.example.com or portal.example.com. The wildcard must match the hostname at that level.
The wildcard name *.example.com does not itself match example.com. Some products include the base domain as an additional certificate name. Check the exact product and issued certificate before relying on that coverage.
Not with *.example.com alone. That is a deeper hostname. It needs the appropriate additional coverage, such as a matching wildcard at the deeper level or a separately included name.
A wildcard applies to its specified domain pattern. Covering a different domain requires a certificate product that explicitly includes the other name or another suitable certificate.
Yes, a new hostname matching the wildcard can use the certificate when installed correctly and permitted by the product. You still need to configure DNS and the service that will handle HTTPS for that hostname.
Use a method supported for the wildcard order. DNS-based validation is a common option. HTTP file validation cannot validate wildcard coverage, so follow the method and instructions supplied for the certificate.
Review the product’s deployment terms and your server configuration. Each installation needs the correct certificate, chain and matching private key. Keep a record of every deployment and protect access to key material.
Contact our team promptly and follow the issuing authority’s revocation and replacement process. Generate replacement key material as required and coordinate updates across every affected installation.
Inventory the endpoints using the certificate, complete any required validation and obtain the replacement. Install and verify it on every affected endpoint before the current certificate expires.
No matching questions. Try another word.
Choose wildcard coverage that fits the way your online services grow.