A SAN license enables you to purchase a number of unique SANs that can be used for as many unique certificates as you may need. This is an ideal fit for organizations that may issue many unique certificates for development purposes or IOT devices. You are permitted to have up to the quoted number of unique SANs on active (not expired or revoked) certificates.

Some important things to keep in mind regarding your SAN license are:

• Each unique SAN counts as 1 SAN of your SAN license.

• Once a certificate expires or is revoked, SANs in that certificate will be returned to your SAN license.

• Wildcard SANs typically count as 5 SANs, but this is configurable per quote.

• You may have more than 1 product taking advantage of one license.

• The greater the number of SANs in the SAN license, the larger the discount, so bundling products may be cost-effective and permit the maximum flexibility.

• Your license quota may be increased during the active license period if you find you need more SANs.

• The price for a greater SAN license is prorated to align with the active license pricing.

• The SAN license may be renewed up to 30 days before (or, in some exceptions, after) the initial license expires.

• A SAN license may increase or decrease its limit upon renewal.

• As customer requirements change or as new TLS products are launched, new products may be added to an existing license (assuming they are of the same or lower tier or price).

• TLS customers want to issue multiple Certificates to the same FQDN for load balancing, reissuing, and other applications, but they only want to be billed for a single SAN.
  • We will permit multiple TLS products (services) to be included in one SAN license.
• This model is good for customers that have a high turnover of SANs within their dev environment or for customer demos or trial purposes (stand up servers, tear them down, and do it again with the same or different SANs).

A SAN license is similar to a Product Pack. They both have a price, a quota, and a list of Products (services) that are included. Product usage data will be fed from the Atlas backend to the Usage Database throughout the day, where it will be allocated to its parent SAN License and SANS counted appropriately. 

We count the total number of unique SANs in non-expired and non-revoked Certificates across all of the services that are specified by the SAN license. Specifically, we will count unique values from:

• SAN:DnsName
• SAN:IpAddress
• SAN:RFC822 (email addresses)
• SAN:OtherName:UPN - These are typically found just in client authentication Certificates.

Wildcard SANs will be counted as separate SANs. Typically, they count as 5, but this can be customized as part of your SAN license quote.

example.com and www.example.com count as two unique SANs. We will do case-insensitive matching when computing the number of unique SANs (e.g. WWW.example.com and www.example.com will count as one SAN).

The CN will always have a corresponding SAN value, so we don't need to count CNs.

As in the case of revocation, once a certificate expires, all of the certificate’s SANs will automatically be returned to your SAN license count.