SAN/UC technology

SAN (Subject Alternative Name) technology was created to extend SSL certificate functionality by securing more subjects/domains in one certificate. SSL certificates with SAN support enable you to secure more domains and cut the costs of buying separate certificates. Saving IP addresses for encrypted communication is another advantage and last, but not least, they save administrators time spent by installing separate certificates on their server. SAN SSL certificates are also used to secure Microsoft Exchange Server, Microsoft Office Communication Server or Unified Communications (UC) services.
You can find a wide range of SAN/UC certificates in SSLmarket offer.

Securing multiple domains and server names

You can add multiple domains and names to the SAN certificate. All possible names you can use as SAN are described in RFC 3280 standard - Internet X.509 Public Key Infrastructure.

Examples of use

  • (FQDN - a fully qualified domain name)
  • (FQDN - a fully qualified domain name)
  • server.local (Internal domain name)
  • (subdomain)
  • (subdomain)
  • (public IP adress)
  • msexchange1 (netbios name)
  • (private IP adress)
  • mail01 (not valid domain or name)

For fully qualified domain names (FQDNs), the certificate requestor must be allowed to use the name by the domain owner. If you do not own the domain, but want to list it as a SAN, you will need the domain owner's consent.

You cannot use unqualified names (non-FQDN) for SAN.