You may have seen news that the certificate authority emSign, which issues Stanford's SSL/TLS certificates through InCommon, is ending its public certificate service. InCommon is moving all members to a new certificate authority, SSL.com, and Stanford is moving with it.
Note: Certificates issued prior to July 10, 2026, were issued through Sectigo and are not affected.
Key dates
- Thursday, Nov. 12, 4 p.m. PT: Stanford certificates start being issued by SSL.com.
- Monday, Nov. 16: emSign stops issuing new certificates.
- Monday, Nov. 16: Microsoft starts to remove the remaining eMudhra root certificates across its products and services.
- Monday, Nov. 30: Apple devices and Safari stop trusting emSign certificates.
What this means
- We strongly recommend that everyone replace their current emSign certificates with new ones from SSL.com before Nov. 16, 2026. Apple removes trust in all emSign certificates on Nov. 30, regardless of when they were issued, and some recent macOS versions (27.2.1) already reject them.
- The certificate request process doesn't change: same form at certificate.stanford.edu, same NetDB requirements. ACME and Certificate API users keep their credentials; ACME users should run a forced renewal after Nov. 12 to get an SSL.com certificate.
- New certificates are Domain Validated (DV), not Organization Validated (OV). They prove control of the domain name but don't include "Stanford University" in the certificate. Browsers show no difference, and most services are unaffected. New certificates chain to a different intermediate and root: "SSL.com TLS Issuing RSA CA R1" and "SSL.com TLS RSA Root CA 2022" (replacing "InCommon Intermediate CA - OVG2C" and "emSign Root TLS CA - G1"). They are valid for about 198 days. If your service requires OV, contact ssl-team@lists.stanford.edu.
- Browsers need no changes: they already trust SSL.com. Chrome and Firefox keep trusting existing emSign certificates until they expire.
- Other systems may also need updates. Before your certificate is replaced, identify any systems that bundle or pin certificate chains—such as Java keystores, load balancers, Wi-Fi/RADIUS profiles, and appliances—and plan to update them with the new SSL.com chain.
What happens next
- We'll post a public announcement with step-by-step instructions as soon as SSL.com issuance is available to Stanford, the night of Thursday, Nov. 12.
- Owners of domains outside stanford.edu (for example stanfordmed.org or hoover.org) will be asked to re-validate their domains for SSL.com.
- Stay informed at Secure Socket Layer (SSL) Certificates for Stanford.edu.
Questions? Contact ssl-team@lists.stanford.edu or submit a Help request.

