SSL Report: cmu.med.ubc.ca (142.103.190.152)
Assessed on:  Mon, 16 Jun 2025 02:22:53 UTC | Clear cache

Due to a recently discovered bug in Apple's code, your browser is exposed to MITM attacks. Click here for more information.

Summary
Overall Rating
A-
0
20
40
60
80
100
Certificate
 
Protocol Support
 
Key Exchange
 
Cipher Strength
 

Visit our documentation page for more information, configuration guides, and books. Known issues are documented here.
This server does not support TLS 1.3.  MORE INFO »
HTTP Strict Transport Security (HSTS) with long duration deployed on this server.  MORE INFO »
Certificate #1: EC 256 bits (SHA384withECDSA)
Server Key and Certificate #1
Subject *.cmu.med.ubc.ca
Fingerprint SHA256: f4b438546bd030a81c9ffb435c7f176aa789d7bef0100380c71a5eabd817458a
Pin SHA256: rXOhI9fLQHzzMiv6UfMGwgkfQYUydxKz1ahkTDYIujM=
Common names *.cmu.med.ubc.ca
Alternative names *.cmu.med.ubc.ca cmu.med.ubc.ca
Serial Number 00d79283f5d62d41ee3cb35ddb409d3a
Valid from Mon, 27 Jan 2025 22:18:58 UTC
Valid until Mon, 23 Feb 2026 14:04:15 UTC (expires in 8 months and 7 days)
Key EC 256 bits
Weak key (Debian) No
Issuer Entrust OV TLS Issuing ECC CA 1
AIA: http://cert.ssl.com/Entrust-OVTLS-I-E1.cer
Signature algorithm SHA384withECDSA
Extended Validation No
Certificate Transparency Yes (certificate)
OCSP Must Staple No
Revocation information CRL, OCSP
CRL: http://crls.ssl.com/Entrust-OVTLS-I-E1.crl
OCSP: http://ocsps.ssl.com
Revocation status Good (not revoked)
DNS CAA No (more info)
Trusted Yes
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 2 (2051 bytes)
Chain issues None
#2
Subject Entrust OV TLS Issuing ECC CA 1
Fingerprint SHA256: 87026a05bc3ad085a8e447c2d2864e2ebec7d017dc488de255cf4e5eb0576271
Pin SHA256: RqnrFMJcpF5K3Rp4AFdL4LQQNfohCVS0RXjj/YcXmJ4=
Valid until Sun, 22 Aug 2027 17:53:06 UTC (expires in 2 years and 2 months)
Key EC 384 bits
Issuer SSL.com TLS ECC Root CA 2022
Signature algorithm SHA384withECDSA


Certification Paths
Path #1: Trusted
1 Sent by server *.cmu.med.ubc.ca
Fingerprint SHA256: f4b438546bd030a81c9ffb435c7f176aa789d7bef0100380c71a5eabd817458a
Pin SHA256: rXOhI9fLQHzzMiv6UfMGwgkfQYUydxKz1ahkTDYIujM=

EC 256 bits / SHA384withECDSA
2 Sent by server Entrust OV TLS Issuing ECC CA 1
Fingerprint SHA256: 87026a05bc3ad085a8e447c2d2864e2ebec7d017dc488de255cf4e5eb0576271
Pin SHA256: RqnrFMJcpF5K3Rp4AFdL4LQQNfohCVS0RXjj/YcXmJ4=

EC 384 bits / SHA384withECDSA
3 In trust store SSL.com TLS ECC Root CA 2022   Self-signed
Fingerprint SHA256: c32ffd9f46f936d16c3673990959434b9ad60aafbb9e7cf33654f144cc1ba143
Pin SHA256: G/ANXI8TwJTdF+AFBM8IiIUPEv0Gf6H5LA/b9guG4yE=

EC 384 bits / SHA384withECDSA
Path #1: Trusted
1 Sent by server *.cmu.med.ubc.ca
Fingerprint SHA256: f4b438546bd030a81c9ffb435c7f176aa789d7bef0100380c71a5eabd817458a
Pin SHA256: rXOhI9fLQHzzMiv6UfMGwgkfQYUydxKz1ahkTDYIujM=

EC 256 bits / SHA384withECDSA
2 Sent by server Entrust OV TLS Issuing ECC CA 1
Fingerprint SHA256: 87026a05bc3ad085a8e447c2d2864e2ebec7d017dc488de255cf4e5eb0576271
Pin SHA256: RqnrFMJcpF5K3Rp4AFdL4LQQNfohCVS0RXjj/YcXmJ4=

EC 384 bits / SHA384withECDSA
3 In trust store SSL.com TLS ECC Root CA 2022   Self-signed
Fingerprint SHA256: c32ffd9f46f936d16c3673990959434b9ad60aafbb9e7cf33654f144cc1ba143
Pin SHA256: G/ANXI8TwJTdF+AFBM8IiIUPEv0Gf6H5LA/b9guG4yE=

EC 384 bits / SHA384withECDSA
Path #1: Trusted
1 Sent by server *.cmu.med.ubc.ca
Fingerprint SHA256: f4b438546bd030a81c9ffb435c7f176aa789d7bef0100380c71a5eabd817458a
Pin SHA256: rXOhI9fLQHzzMiv6UfMGwgkfQYUydxKz1ahkTDYIujM=

EC 256 bits / SHA384withECDSA
2 Sent by server Entrust OV TLS Issuing ECC CA 1
Fingerprint SHA256: 87026a05bc3ad085a8e447c2d2864e2ebec7d017dc488de255cf4e5eb0576271
Pin SHA256: RqnrFMJcpF5K3Rp4AFdL4LQQNfohCVS0RXjj/YcXmJ4=

EC 384 bits / SHA384withECDSA
3 In trust store SSL.com TLS ECC Root CA 2022   Self-signed
Fingerprint SHA256: c32ffd9f46f936d16c3673990959434b9ad60aafbb9e7cf33654f144cc1ba143
Pin SHA256: G/ANXI8TwJTdF+AFBM8IiIUPEv0Gf6H5LA/b9guG4yE=

EC 384 bits / SHA384withECDSA
Path #1: Trusted
1 Sent by server *.cmu.med.ubc.ca
Fingerprint SHA256: f4b438546bd030a81c9ffb435c7f176aa789d7bef0100380c71a5eabd817458a
Pin SHA256: rXOhI9fLQHzzMiv6UfMGwgkfQYUydxKz1ahkTDYIujM=

EC 256 bits / SHA384withECDSA
2 Sent by server Entrust OV TLS Issuing ECC CA 1
Fingerprint SHA256: 87026a05bc3ad085a8e447c2d2864e2ebec7d017dc488de255cf4e5eb0576271
Pin SHA256: RqnrFMJcpF5K3Rp4AFdL4LQQNfohCVS0RXjj/YcXmJ4=

EC 384 bits / SHA384withECDSA
3 In trust store SSL.com TLS ECC Root CA 2022   Self-signed
Fingerprint SHA256: c32ffd9f46f936d16c3673990959434b9ad60aafbb9e7cf33654f144cc1ba143
Pin SHA256: G/ANXI8TwJTdF+AFBM8IiIUPEv0Gf6H5LA/b9guG4yE=

EC 384 bits / SHA384withECDSA
Path #1: Trusted
1 Sent by server *.cmu.med.ubc.ca
Fingerprint SHA256: f4b438546bd030a81c9ffb435c7f176aa789d7bef0100380c71a5eabd817458a
Pin SHA256: rXOhI9fLQHzzMiv6UfMGwgkfQYUydxKz1ahkTDYIujM=

EC 256 bits / SHA384withECDSA
2 Sent by server Entrust OV TLS Issuing ECC CA 1
Fingerprint SHA256: 87026a05bc3ad085a8e447c2d2864e2ebec7d017dc488de255cf4e5eb0576271
Pin SHA256: RqnrFMJcpF5K3Rp4AFdL4LQQNfohCVS0RXjj/YcXmJ4=

EC 384 bits / SHA384withECDSA
3 In trust store SSL.com TLS ECC Root CA 2022   Self-signed
Fingerprint SHA256: c32ffd9f46f936d16c3673990959434b9ad60aafbb9e7cf33654f144cc1ba143
Pin SHA256: G/ANXI8TwJTdF+AFBM8IiIUPEv0Gf6H5LA/b9guG4yE=

EC 384 bits / SHA384withECDSA

Click here to expand

Configuration
Protocols
TLS 1.3 No
TLS 1.2 Yes
TLS 1.1 No
TLS 1.0 No
SSL 3 No
SSL 2 No


Cipher Suites
# TLS 1.2 (suites in server-preferred order)
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c)   ECDH secp384r1 (eq. 7680 bits RSA)   FS 256
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b)   ECDH x25519 (eq. 3072 bits RSA)   FS 128


Handshake Simulation
Android 4.4.2 EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Android 5.0.0 EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Android 6.0 EC 256 (SHA384)   TLS 1.2 > http/1.1   TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Android 7.0 EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Android 8.0 EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Android 8.1 EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Android 9.0 EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
BingPreview Jan 2015 EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Chrome 49 / XP SP3 Server closed connection
Chrome 69 / Win 7  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Chrome 70 / Win 10 EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Chrome 80 / Win 10  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Firefox 31.3.0 ESR / Win 7 EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 47 / Win 7  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256   ECDH secp256r1  FS
Firefox 49 / XP SP3 EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Firefox 62 / Win 7  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Firefox 73 / Win 10  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Googlebot Feb 2018 EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
IE 11 / Win 7  R EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
IE 11 / Win 8.1  R EC 256 (SHA384)   TLS 1.2 > http/1.1   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
IE 11 / Win Phone 8.1  R EC 256 (SHA384)   TLS 1.2 > http/1.1   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
IE 11 / Win Phone 8.1 Update  R EC 256 (SHA384)   TLS 1.2 > http/1.1   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
IE 11 / Win 10  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Edge 15 / Win 10  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Edge 16 / Win 10  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Edge 18 / Win 10  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Edge 13 / Win Phone 10  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Java 8u161 EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Java 11.0.3 EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Java 12.0.1 EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
OpenSSL 1.0.1l  R EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
OpenSSL 1.0.2s  R EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
OpenSSL 1.1.0k  R EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
OpenSSL 1.1.1c  R EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 6 / iOS 6.0.1 Server closed connection
Safari 7 / iOS 7.1  R Server closed connection
Safari 7 / OS X 10.9  R Server closed connection
Safari 8 / iOS 8.4  R Server closed connection
Safari 8 / OS X 10.10  R Server closed connection
Safari 9 / iOS 9  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 9 / OS X 10.11  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 10 / iOS 10  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 10 / OS X 10.12  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 12.1.2 / MacOS 10.14.6 Beta  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 12.1.1 / iOS 12.3.1  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Apple ATS 9 / iOS 9  R EC 256 (SHA384)   TLS 1.2 > h2   TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Yahoo Slurp Jan 2015 EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
YandexBot Jan 2015 EC 256 (SHA384)   TLS 1.2 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
# Not simulated clients (Protocol mismatch)
Android 2.3.7   No SNI 2 Protocol mismatch (not simulated)
Android 4.0.4 Protocol mismatch (not simulated)
Android 4.1.1 Protocol mismatch (not simulated)
Android 4.2.2 Protocol mismatch (not simulated)
Android 4.3 Protocol mismatch (not simulated)
Baidu Jan 2015 Protocol mismatch (not simulated)
IE 6 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)
IE 7 / Vista Protocol mismatch (not simulated)
IE 8 / XP   No FS 1   No SNI 2 Protocol mismatch (not simulated)
IE 8-10 / Win 7  R Protocol mismatch (not simulated)
IE 10 / Win Phone 8.0 Protocol mismatch (not simulated)
Java 6u45   No SNI 2 Protocol mismatch (not simulated)
Java 7u25 Protocol mismatch (not simulated)
OpenSSL 0.9.8y Protocol mismatch (not simulated)
Safari 5.1.9 / OS X 10.6.8 Protocol mismatch (not simulated)
Safari 6.0.4 / OS X 10.8.4  R Protocol mismatch (not simulated)

Click here to expand

(1) Clients that do not support Forward Secrecy (FS) are excluded when determining support for it.
(2) No support for virtual SSL hosting (SNI). Connects to the default site if the server uses SNI.
(3) Only first connection attempt simulated. Browsers sometimes retry with a lower protocol version.
(R) Denotes a reference browser or client, with which we expect better effective security.
(All) We use defaults, but some platforms do not use their best protocols and features (e.g., Java 6 & 7, older IE).
(All) Certificate trust is not checked in handshake simulation, we only perform TLS handshake.


Protocol Details
Secure Renegotiation Supported
Secure Client-Initiated Renegotiation No
Insecure Client-Initiated Renegotiation No
BEAST attack Mitigated server-side (more info)  
POODLE (SSLv3) No, SSL 3 not supported (more info)
POODLE (TLS) No (more info)
Zombie POODLE No (more info)  
GOLDENDOODLE No (more info)  
OpenSSL 0-Length No (more info)  
Sleeping POODLE No (more info)  
Downgrade attack prevention Unknown (requires support for at least two protocols, excl. SSL2)
SSL/TLS compression No
RC4 No
Heartbeat (extension) No
Heartbleed (vulnerability) No (more info)
Ticketbleed (vulnerability) No (more info)
OpenSSL CCS vuln. (CVE-2014-0224) No (more info)
OpenSSL Padding Oracle vuln.
(CVE-2016-2107)
No (more info)
ROBOT (vulnerability) No (more info)
Forward Secrecy Yes (with most browsers)   ROBUST (more info)
ALPN Yes   h2 http/1.1
NPN No
Session resumption (caching) No (IDs assigned but not accepted)
Session resumption (tickets) No
OCSP stapling Yes
Strict Transport Security (HSTS) Yes
max-age=31536000; includeSubDomains; preload
HSTS Preloading Not in: Chrome  Edge  Firefox  IE 
Public Key Pinning (HPKP) No (more info)
Public Key Pinning Report-Only No
Public Key Pinning (Static) No (more info)
Long handshake intolerance No
TLS extension intolerance No
TLS version intolerance No
Incorrect SNI alerts No
Uses common DH primes No, DHE suites not supported
DH public server param (Ys) reuse No, DHE suites not supported
ECDH public server param reuse Yes
Supported Named Groups secp384r1, x25519, secp256r1 (server preferred order)
SSL 2 handshake compatibility No


HTTP Requests
1 https://cmu.med.ubc.ca/  (HTTP/1.1 302 Redirect)
1
Cache-Control no-cache, no-store
Pragma no-cache
Content-Type text/html; charset=UTF-8
Expires -1
Location https://authentication.ubc.ca/idp/profile/SAML2/Redirect/SSO?SAMLRequest=fZJfb4IwFMW%2FCum7FKoQ0wiJ04eZuEmE7WEvSynX0QRa1lv259sPUTOXLL625%2F7uOSd3gaJtOr7sXa338N4DOu%2BrbTTy8SMhvdXcCFTItWgBuZM8Xz5sOfMD3lnjjDQN8ZaIYJ0yemU09i3YHOyHkvC03yakdq5DTqlse7%2BFyu9L6UtB81qVpWnA1T6ioUcqo9kuL4i3HmwoLY7A33ExeATtlBzfLxRVdXTwcVANnBF7qJQF6Wie74i3WSfkVRwYzIMwCMQ0mM9YOA2jUhziKi6jMo7kbJAh9rDR6IR2CWEBiyZBPAnjImCcMR7OX4iXnePeKV0p%2FXa7m%2FIkQn5fFNnkFOsZLI6RBgFJF8eG%2BbjYXnV%2BGysuRZP0%2F1oX9Ap72tHxx4GzWWemUfLbWzaN%2BVxZEA4SEhKankb%2BHkH6Aw%3D%3D&RelayState=ss%3Amem%3Ae127265a7ab3ab47f0da7214eff6e04865a864b9e31d5c8f9638e21ca820e556
Server Microsoft-IIS/10.0
Set-Cookie _opensaml_req_ss%3Amem%3Ae127265a7ab3ab47f0da7214eff6e04865a864b9e31d5c8f9638e21ca820e556=_af2e80100a308421315baf6d6b5b65c4; path=/; secure; HttpOnly; SameSite=None
X-Powered-By ASP.NET
Strict-Transport-Security max-age=31536000; includeSubDomains; preload
Date Mon, 16 Jun 2025 02:22:18 GMT
Connection close
Content-Length 741


Miscellaneous
Test date Mon, 16 Jun 2025 02:22:05 UTC
Test duration 48.454 seconds
HTTP status code 302
HTTP forwarding https://authentication.ubc.ca
HTTP server signature Microsoft-IIS/10.0
Server hostname cmu.med.ubc.ca


SSL Report v2.4.0