Skip to main content

Secure Socket Layer (SSL) Certificates for Stanford.edu

Important: Replace emSign certificates before November 16, 2026.

Microsoft is removing trust in the emSign roots (emSign Root CA - G1 and emSign Root TLS CA - G1) from Windows, Edge and WebView2 starting November 16, 2026. Stanford's current InCommon (emSign) certificates chain to these roots, so they will stop being trusted on Windows devices and in Edge as the update reaches them, regardless of expiration date. Apple and other platforms are expected to follow; Linux, Java and .NET trust stores update after the Mozilla release.

What to do now: SSL.com is the default for all new requests (live since Nov 12); emSign is no longer offered. Request a replacement the usual way and install it with the full chain. Web form: submit your CSR at certificate.stanford.edu. ACME: same directory URL and EAB credentials, run a forced renewal (if certbot times out, run it again in a few minutes). Certificate API: submit a new request; credentials don't change. Update any system that pins or bundles the old emSign chain. Let's Encrypt (90-day) is available as an option.

Certificate owners are being contacted directly with their affected certificates. Questions: ssl-team@lists.stanford.edu.

See Action required: Replace your Stanford SSL/TLS certificates by Nov. 16, 2026 for more information.

An SSL certificate is a signed electronic guarantee that verifies the authenticity of a particular server. It's primarily used for providing web pages through an encrypted connection. Any service accessible by SSL must have a certificate, including any web server with encrypted or "secure" content.

Sometimes a self-signed certificate is sufficient for test and development servers, and it works with SSL encryption. See the instructions for creating a self-signed certificate for more information. However, self-signed certificates don't help confirm the server's authenticity, and they could be open to some attacks. Most clients display a warning when they connect to a server with a self-signed certificate before proceeding (and some won't work at all).

You should use an SSL certificate signed by a trusted certificate authority on servers that require an encrypted connection. Stanford provides SSL/TLS certificates for eligible Stanford domains through the InCommon certificate service. There is no longer a cost to Stanford users. Certificates are issued by SSL.com. Let's Encrypt is available as an option.

Designed for

Current faculty and staff; system administrators in academic and administrative departments.

Requirements

To request a certificate for a given hostname:

  • The name must exist in NetDB.
  • The requester must be listed as an administrator or administrative group member in the host name's NetDB record.

Note: If you do not have a NetDB account, you can check if the name exists using StanfordWhat.

Data security

SSL certificates are required for all web servers with encrypted or High Risk Data. Please review the information on Moderate and High Risk Data, as defined by the Information Security Office.

Rates

Free of charge.

Get started

To obtain an SSL certificate, you must first generate a CSR (Certificate Signing Request). This file contains the required technical information to generate an SSL certificate.

Be sure to use fully qualified names only (e.g., host.stanford.edu). Short names and OU/email fields are not accepted. RSA and ECC keys are both supported.

To request a certificate, follow these steps:

  1. Generate a CSR. You can generate a CSR in multiple ways. Your server software may have a built-in function that creates the private key and CSR for you, but in most cases, you should use the OpenSSL command-line utility to create them (see instructions). For more information, review
    1.  How Do I Generate an SSL/TLS Certificate Signing Request (CSR) on My Server?
    2. Manually Generate a Certificate Signing Request (CSR) Using OpenSSL
    3. Note that all the hosts listed in your CSR must be registered in the NetDB system.
  2. Note: The service supports 2048/3072/4096-bit keys. 3072-bit keys is recommended as of November 2023.
  3. Store your key in a safe and secure location. 
  4. Complete the online request form.
  5. You should receive your certificate within minutes; you'll receive an email when it's ready..

After SSL.com issues your certificate, you'll receive an an email from the certificate service with links to the certificate and its chain (certificate + intermediate; the root is not included). The message contains several links to the certificate in different file formats (the first link contains the most common format) along with a link to a file that contains the root and chaining certificates (combined in one file) used to sign your certificate.

Renewals

The process for certificate renewal is exactly the same as for ordering a new certificate. You must create a CSR and submit the request form.

Get help

For assistance, please submit a Help request.

Learn more

See also

Last modified