Skip to content
AdminKit

SAN (Subject Alternative Name)

What is SAN (Subject Alternative Name)?

SAN (Subject Alternative Name), defined in RFC 5280, is the X.509 certificate extension listing every hostname a certificate actually covers -- the field browsers check for a match, not the legacy subject Common Name. AdminKit's SSL checker shows the exact SAN list a live certificate presents.

By AdminKit team, Netbase JSC · Updated

SAN (Subject Alternative Name) is an X.509 certificate extension, defined in RFC 5280 (current document status at its IETF Datatracker entry), that lists every hostname (and optionally IP address) a certificate is valid for, as one or more DNS name entries attached to the certificate alongside its subject field. OpenSSL’s x509v3_config documentation, which describes how its commands add this extension as subjectAltName, calls it a multi-valued extension that supports several types of name identifier, including DNS domain names, IP addresses, email addresses and URIs. Modern browsers and TLS libraries check the SAN list, not the certificate’s subject Common Name, to decide whether a certificate matches the hostname being connected to — the CN field is effectively legacy and ignored for this purpose in current clients, a change the CA/Browser Forum’s baseline requirements formalized industry-wide. A single certificate’s SAN list can cover multiple distinct hostnames, including a wildcard entry like *.example.com alongside the bare apex domain, which is how one certificate commonly serves both a site and its subdomains. A certificate presented for a hostname absent from its SAN list fails hostname verification even if every other part of the certificate chain is valid.

SAN (Subject Alternative Name) is part of AdminKit’s machine protocols cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

What does a certificate's SAN field list?

Every hostname, and optionally IP address, the certificate is valid for, as one or more entries defined in RFC 5280.

Do modern browsers check the subject CN or the SAN list for hostname matching?

The SAN list -- the CN field is effectively legacy and ignored for this purpose in current clients.

Can one certificate's SAN list cover multiple hostnames?

Yes, including a wildcard entry such as *.example.com alongside the bare apex domain.

What happens if a hostname is absent from a certificate's SAN list?

Hostname verification fails for that connection, even if every other part of the certificate chain is valid.