← Applications

PQC.KENMTEST.COM

Live TLS and certificate information reported by Apache for this page request.

Certificate public key
id-ecPublicKey
Classical certificate in use
Your browser connected using a standard certificate with a classical public key.
TLS protocol
TLSv1.3
Negotiated transport version

Connection

TLS version
TLSv1.3
Cipher suite
TLS_AES_256_GCM_SHA384
Symmetric cipher bits
256
HTTP protocol
HTTP/1.1
Requested server name (SNI)
pqc.kenmtest.com
Observed at (UTC)
2026-11-20T20:53:58+00:00

Server certificate

Subject
CN=pqc.kenmtest.com,O=DIGICERT SUB LLC,L=Lehi,ST=Utah,C=US
Issuer
CN=DigiCert G5 TLS ECC SHA384 2021 CA1,O=DigiCert\, Inc.,C=US
Public-key algorithm
id-ecPublicKey
Certificate signature algorithm
ecdsa-with-SHA384
Serial number
03377E08E70966608ED445281567A045
Valid from
Nov 20 00:00:00 2026 GMT
Valid until
May 7 23:59:59 2027 GMT
SHA-256 fingerprint
16:EB:EE:D2:91:7E:E3:30:1B:A0:0D:89:B1:7C:30:EF:2D:BD:FD:DE:02:58:FD:C0:96:7A:8E:48:16:3C:04:C8
Download certificate (PEM)
Public certificate (PEM)
-----BEGIN CERTIFICATE-----
MIIFTjCCBNOgAwIBAgIQAzd+COcJZmCO1EUoFWegRTAKBggqhkjOPQQDAzBUMQsw
CQYDVQQGEwJVUzEXMBUGA1UEChMORGlnaUNlcnQsIEluYy4xLDAqBgNVBAMTI0Rp
Z2lDZXJ0IEc1IFRMUyBFQ0MgU0hBMzg0IDIwMjEgQ0ExMB4XDTI2MTEyMDAwMDAw
MFoXDTI3MDUwNzIzNTk1OVowYTELMAkGA1UEBhMCVVMxDTALBgNVBAgTBFV0YWgx
DTALBgNVBAcTBExlaGkxGTAXBgNVBAoTEERJR0lDRVJUIFNVQiBMTEMxGTAXBgNV
BAMTEHBxYy5rZW5tdGVzdC5jb20wWTATBgcqhkjOPQIBBggqhkjOPQMBBwNCAAR7
QzEOWOkvU7DckE7WID5+tARfl0daTWffoCmlW414rFJnEzdf03J81C+GAeGzypxt
j4AvvjbhlCL4vXyDRai/o4IDeDCCA3QwHwYDVR0jBBgwFoAUm1jcjaZlmOe8Bv4a
pBWgb8vmqZAwHQYDVR0OBBYEFH9MvXHmPOh0MvFHl0PjyxLA+SF+MBsGA1UdEQQU
MBKCEHBxYy5rZW5tdGVzdC5jb20wPgYDVR0gBDcwNTAzBgZngQwBAgIwKTAnBggr
BgEFBQcCARYbaHR0cDovL3d3dy5kaWdpY2VydC5jb20vQ1BTMA4GA1UdDwEB/wQE
AwIDiDATBgNVHSUEDDAKBggrBgEFBQcDATCBkwYDVR0fBIGLMIGIMEKgQKA+hjxo
dHRwOi8vY3JsMy5kaWdpY2VydC5jb20vRGlnaUNlcnRHNVRMU0VDQ1NIQTM4NDIw
MjFDQTEtMS5jcmwwQqBAoD6GPGh0dHA6Ly9jcmw0LmRpZ2ljZXJ0LmNvbS9EaWdp
Q2VydEc1VExTRUNDU0hBMzg0MjAyMUNBMS0xLmNybDCBgQYIKwYBBQUHAQEEdTBz
MCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5kaWdpY2VydC5jb20wSwYIKwYBBQUH
MAKGP2h0dHA6Ly9jYWNlcnRzLmRpZ2ljZXJ0LmNvbS9EaWdpQ2VydEc1VExTRUND
U0hBMzg0MjAyMUNBMS0xLmNydDAMBgNVHRMBAf8EAjAAMIIBhgYKKwYBBAHWeQIE
AgSCAXYEggFyAXAAfwCigQAYc04Xbh1H4JVA84G6VGaXzWOoQ1BxbrgJTtrxDQAA
AaH6suVFAAgAAAUATTu65wQDAEgwRgIhAPWW3GoX17jIEunyqLVEsAfHzBv6ltnb
ISAPKDMseItaAiEA/DKEWbi9TUczHMZvfHtksgxiQ3LOeOTsPVyy13WFROIAdQAA
Gl0aHC2TdbZIVXj4L3Ghrm7vOX0pfIrjFXvK3uGgHgAAAaH6suROAAAEAwBGMEQC
IEw6kTDjX61Q/1OqlRH4uZ7m6i+vKgvjYuIqY3yK94/dAiBnCpK8W3wbdHIy+ySO
aWxfkliWfPcjWz+W050gDMZyRAB2AEaiOWfGDbZGh8ZvPfmZlHaTpqYRIIRX1VXn
49Ch2bZGAAABofqy5FYAAAQDAEcwRQIhALuwlQvAmlSCciDucCDH1AR15FHvvL+0
aw7cPLXYED/FAiAQlf6biGehDDy2SkKynq0Tv+gCQwC/Gj8niOlFs7eVgDAKBggq
hkjOPQQDAwNpADBmAjEAg6Jz/QOkEj90IetMA4WhUYcr50UNBhOpI2MJZUrNOpTU
HIvdgyhJl4EXH1SXH2E8AjEA0PsB1MCEOXKkmNEvbbKARnqEOskLpWdpwAz/jsvf
n8x9Xl34KmpYumEbfVh0KDft
-----END CERTIFICATE-----

Configured certificate chain

No matching chain bundle is available for this certificate, or this session is resumed.

How this connection was authenticated
  1. Your browser advertised supported signature algorithms.
  2. The server selected a certificate containing a id-ecPublicKey public key.
  3. In a full TLS 1.3 handshake, the server signs the handshake transcript in CertificateVerify to prove possession of the corresponding private key. Your browser checks that proof with the certificate’s public key.
  4. The browser evaluates the certificate chain and hostname under its trust settings.

The certificate’s ecdsa-with-SHA384 signature is the issuer’s signature on the certificate, separate from the server’s handshake signature.

Certificate authentication and key exchange are separate. A PQC certificate does not establish that the key exchange was PQC. The negotiated cipher suite TLS_AES_256_GCM_SHA384 describes symmetric encryption and the TLS hash.

This explains the TLS 1.3 protocol using reported certificate data. The exact CertificateVerify signature scheme and key-exchange group are not measured by this page.