This feature is well established and works across many devices and browser versions. It’s been available across browsers since January 2020.
* Some parts of this feature may have varying levels of support.
The RTCCertificate interface of the WebRTC API provides an object representing a certificate that an RTCPeerConnection uses to authenticate.
RTCCertificate is a serializable object, so it can be cloned with structuredClone() or copied between Workers using postMessage().
RTCCertificate.expires Read only
Returns the expiration date of the certificate.
RTCCertificate.getFingerprints()Returns an array of certificate fingerprints, calculated using the different algorithms supported by the browser.
| Desktop | Mobile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Chrome | Edge | Firefox | Opera | Safari | Chrome Android | Firefox for Android | Opera Android | Safari on IOS | Samsung Internet | WebView Android | WebView on iOS | |
RTCCertificate |
49 | 79 | 42 | 36 | 12.1 | 49 | 42 | 36 | 12.2 | 5.0 | 49 | 12.2 |
expires |
49 | 79 | 42 | 36 | 12.1 | 49 | 42 | 36 | 12.2 | 5.0 | 49 | 12.2 |
getFingerprints |
61 | 79 | 138 | 48 | 12.1 | 61 | 138 | 45 | 12.2 | 8.0 | 61 | 12.2 |
RTCPeerConnection.RTCPeerConnection() argument configuration.certificatesRTCPeerConnection.generateCertificate()
© 2005–2025 MDN contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/API/RTCCertificate