A multi-domain SAN certificate secures up to 250 hostnames with a single file and a single renewal date. The base price already covers 3 hostnames; add more SANs whenever you need them.
Prices are the full cost for the chosen term and include the primary hostname plus 2 SANs.
Pick a billing period
No products match your filter.
Prices without VAT; Latvian VAT is 21% where it applies. Prices follow the certificate authorities daily.
From 24 February 2026 a public SSL certificate is issued for up to 199 days, so the file is shorter lived than before. It is a security win: short-lived certificates are much harder to abuse if a key ever leaks. Your multi-year price here does not change and there is no extra cost. At each interval you reissue the certificate yourself in the client panel, which shows how many days are left.
example.com, example.net and example.lv on one certificate with one renewal instead of three.
Cover mail.example.com, autodiscover, webmail and API hosts together: ideal for Exchange and Zimbra.
Country domains for each market stay secured under one file your load balancer can actually manage.
Order with the primary hostname and up to 2 included SANs; add extra SANs in the same order.
DV checks run per domain via DNS or email; EV adds the company vetting once for the whole certificate.
A single bundle goes on your servers. Adding a SAN later reissues the certificate at no downtime.
New CA/Browser Forum rules cut the maximum validity of a public SSL certificate step by step, down to just 47 days by 2029.
A 47-day certificate means 8 or more renewals every year, so automation becomes the only practical way to stay secure. On our multi-year plans the price never changes. Today you reissue the certificate yourself in the client panel at each interval; if you want it hands-off, our ACME certificate renews automatically.
Up to 250 SAN entries fit on a single certificate, which is enough for large brand portfolios and complex service infrastructures. Each certificate has one primary hostname, and 2 further SANs are already included, so you start with 3 protected hostnames. Beyond that, every hostname takes one SAN slot, and a wildcard entry also occupies a single slot even though it covers many subdomains. You do not need to fill the list at purchase time: begin with the hostnames you actually use and extend the certificate later as projects appear. If you are planning something close to the 250 limit, write to support first and we will help you structure the order sensibly.
Yes, this is one of the main reasons to pick a SAN certificate. You order the extra SAN, we add the hostname to the certificate, and the new domain goes through validation just like the original ones. Once it passes, the certificate is reissued and you install the updated file on your servers. The old certificate keeps working until you swap it, so there is no downtime for the sites already covered. The expiry date does not move: the added hostname simply runs on the remaining term, and everything still renews on a single date. Plan the validation step in advance, since you need DNS or mailbox access for the new domain.
Yes, on certificates that support it a SAN entry can be a wildcard such as *.example.com. One such entry covers every subdomain of that domain, so shop.example.com, mail.example.com and any names you create later are protected without changing the certificate. Keep in mind that a wildcard covers one subdomain level, and the bare domain is technically a separate name, so plan your entry list accordingly. The practical value is the combination: inside one multi-domain certificate you can mix ordinary hostnames from several different domains with wildcard entries for the domains where subdomains appear and disappear often. Wildcard SANs have their own per-SAN price, shown in the extra SAN table on this page.
No. The certificate authority checks that each domain passes validation, and that check is completed by whoever actually controls the domain, but the registrants can all be different companies or people. This makes SAN certificates practical for agencies, resellers and IT teams that manage sites for many clients and want one certificate with one renewal. Two honest caveats: every domain owner has to cooperate during validation, and all hostnames share one private key and one file, so whoever installs the certificate can serve any of the listed names. If clients need strict separation from each other, separate certificates are the cleaner choice; write to support if you are unsure.
Start from what you actually need to protect. If your list contains several different domains, for example a .com, a .net and country domains, a SAN certificate is the right tool, because a plain wildcard only ever covers one domain. If everything lives under a single domain and you keep creating subdomains, a wildcard is simpler, since new subdomains are covered automatically. Many real setups need both at once: a few separate domains plus fast-changing subdomains under one of them. In that case take a multi-domain certificate and add a wildcard SAN for the busy domain. Count your hostnames for the next year or two before ordering, that usually makes the choice obvious.
Sectigo multi-domain certificates at CloudHosting start from 19.27 EUR a year, and that base price already includes the primary hostname plus 2 SANs, so 3 hostnames in total. Every additional hostname is billed at a fixed per-SAN price for the same term as the certificate, so the total grows predictably as your list grows. The table on this page shows the full cost for each term, and multi-year terms are delivered as consecutive certificates reissued at each interval under CA/B Forum rules, with payment covering the whole chosen period. Compared with buying a separate certificate for every domain, you also save the administrative overhead of tracking many renewals and juggling several files.
SAN stands for Subject Alternative Name, a field inside an SSL certificate that lists every hostname the certificate is valid for. When a browser or mail client connects, it checks whether the name it requested appears in that list, so one certificate can serve many sites. On our Sectigo multi-domain certificates the list holds up to 250 entries. UCC, short for Unified Communications Certificate, is the older Microsoft term for exactly the same construction, coined for Exchange deployments that need names like autodiscover and webmail on one certificate. So when Exchange or Zimbra documentation asks for a UCC certificate, any multi-domain SAN certificate from this page satisfies the requirement.
DV, domain validation, only proves control of each hostname through a DNS record or a confirmation email, so issuance is quick and prices start from 19.27 EUR a year. For most websites, mail servers and internal services that level is entirely sufficient, because the encryption itself is identical. EV, extended validation, adds a one-time vetting of your company for the whole certificate: documents are checked and the verified legal entity is written into the certificate, where corporate and banking clients can see it. Expect the EV process to take longer, since a real organisation check is involved. Choose EV when your customers or partners require proof of who operates the service; otherwise DV keeps things simple.
Deploy in minutes or talk to an engineer about what fits your project.