Skip to Content
Platform.Ontology

TLS client certificates

A site can ask the browser to present a certificate stored on the computer.

Works without askingSign in and identityLegacyWeb browsersWhen the page loads

In one line

Can ask your browser to show a certificate stored on your computer

A site can ask the browser to present a certificate stored on the computer.

Certificates identify a person or company. The browser asks which cert to send; used in banks and enterprise.

What it can and can't do

What the user does: You open a bank or company site and pick a certificate in the box that appears

It can

  • Ask you to choose one certificate from those on your device
  • Receive the certificate you choose to prove who you or your company are
  • Sign you in to a bank or work site without a password

It cannot

  • Pick a certificate for you without your choice, unless you set the browser to auto choose
  • Get the private key; it stays on your device or security card
  • See certificates you did not choose to send

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported1.02008-12-11None
EdgeSupported1.0Not listedNone
FirefoxSupported1.02004-11-09None
SafariSupported1.02003-06-23None
Safari on iPhoneSupported1.02007-06-29None
Chrome on AndroidSupported1.0Not listedNone
Samsung InternetSupported1.02013-04-27None

How a site asks for it

APITLS CertificateRequest during handshake; browser certificate chooser
How access is grantedprompt
What the user seesBrowser or OS certificate picker
Needs a secure context (HTTPS)Yes
Needs a user gestureNo
How long it lastsPer origin
How to take it backSite settings
Inside an iframeSame as top level; cross-origin iframes need a permissions policy where listed

Typical flow

  1. Call the API
  2. Browser applies its access rules
  3. Page receives the result

Data you get

What comes back: A site can ask the browser to present a certificate stored on the computer.
Shape: object
How often: on demand

FieldTypeUnitRangePrecision
subject DNstringNonecertificate definedNot listed
issuerstringNoneCA nameNot listed

Technical limits

  • Page cannot read cert store
  • Chooser shown at TLS layer
  • Auto select via enterprise policy

The story

What it is

The browser can offer a digital ID card stored on your computer when a site asks.

For you

A box may pop up asking which certificate to use, or it picks one for you. There is no password box. You mostly see this at work, school or a government service.

For makers

Makers use client certificates for very strong machine and person checks, such as a bank or an internal company tool. It proves the device is one the company issued before the site loads.

Where you see it

TypeExampleApps
enterpriseA company intranet only opens on laptops that carry a certificate from IT, so a stolen password alone does not get in.None named
bankingA business bank portal asks for a certificate stored on a smart card or token before it shows balances.None named
securityA government tax or health web service uses a national ID certificate to prove who is filing.None named
developerAn engineer reaches a staging server or code tool that only accepts browsers with the right certificate.Cloudflare Access
gamesAn online gaming tournament admin panel is limited to organizer laptops with certificates, so only staff can change brackets.None named
analyticsA security team logs which certificate connected to spot an unusual device.None named

Risks

  • Certificate reveals identity to site
  • Hard to set up and move

Good uses and abuse

Legitimate uses

  • Mutual TLS in enterprise

Known abuse

  • Identity linking across sites if the same cert is used

Scores

ScoreValueMeaning
Sensitivity4 of 5How revealing the data is
Utility2 of 5How useful it is to honest apps
Friction2 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 1999, Chrome 1: Client cert support from early TLS

Sources

How well checked: Inferred from related behavior.

On this page