SSL Report: icmprovisioningpre.bostonscientific.com (34.225.98.95)
Assessed on:  Fri, 13 Jun 2025 05:28:07 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
T
If trust issues are ignored: B
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's certificate is not trusted, see below for details.
HTTP request to this server failed, see below for details.
This server supports TLS 1.0 and TLS 1.1. Grade capped to B. MORE INFO »
This server does not support TLS 1.3.  MORE INFO »
Certificate #1: RSA 4096 bits (SHA256withRSA)
Server Key and Certificate #1
Subject icmprovisioningpre.bostonscientific.com
Fingerprint SHA256: e9f9a1df1edc846f8d6f23a8810159134b0c6e564bdb46e15dc996dba53e6c61
Pin SHA256: SY0R5iEc2dhv7WeYmJ3ghIG3cl6BO3oO4Mqqt7OzGFE=
Common names icmprovisioningpre.bostonscientific.com
Alternative names icmprovisioningpre.bostonscientific.com www.icmprovisioningpre.bostonscientific.com www.was1.bostonscientific.com was1.bostonscientific.com www.was9.bostonscientific.com was9.bostonscientific.com was2.bostonscientific.com www.was2.bostonscientific.com
Serial Number 67c26677cba02539
Valid from Wed, 08 Jan 2025 17:35:26 UTC
Valid until Thu, 08 Jan 2026 17:35:25 UTC (expires in 6 months and 26 days)
Key RSA 4096 bits (e 65537)
Weak key (Debian) No
Issuer pca_pe C=US ST=Minnesota L=St. Paul O=Boston Scientific OU=RM
Signature algorithm SHA256withRSA
Extended Validation No
Certificate Transparency No
OCSP Must Staple No
Revocation information None
DNS CAA No (more info)
Trusted No   NOT TRUSTED (Why?)
Mozilla  Apple  Android  Java  Windows 


Additional Certificates (if supplied)
Certificates provided 3 (4524 bytes)
Chain issues Contains anchor
#2
Subject pca_pe C=US ST=Minnesota L=St. Paul O=Boston Scientific OU=RM
Fingerprint SHA256: 78a41b1a804eb2b8da36f56588c53e3cc6631ae0e1a238ef9ac2457cc247598b
Pin SHA256: YhW3yUJCxLeDqPrbacS6HIfnNiHDHusffRor9A2AGMo=
Valid until Wed, 31 Dec 2059 01:01:01 UTC (expires in 34 years and 6 months)
Key RSA 4096 bits (e 65537)
Issuer rmca_sha2_pe
Signature algorithm SHA256withRSA
#3
Subject rmca_sha2_pe   Not in trust store
Fingerprint SHA256: 39248f94e0235999b4e582748d4800bd15fd68d406da01a322abb7fdc993e89e
Pin SHA256: cfshgfeOSu0ueFLK+wWcKn2UlfGKBcT2GwMS2BycdgY=
Valid until Wed, 31 Dec 2059 01:01:01 UTC (expires in 34 years and 6 months)
Key RSA 4096 bits (e 65537)
Issuer rmca_sha2_pe   Self-signed
Signature algorithm SHA256withRSA


Certification Paths
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server icmprovisioningpre.bostonscientific.com
Fingerprint SHA256: e9f9a1df1edc846f8d6f23a8810159134b0c6e564bdb46e15dc996dba53e6c61
Pin SHA256: SY0R5iEc2dhv7WeYmJ3ghIG3cl6BO3oO4Mqqt7OzGFE=

RSA 4096 bits (e 65537) / SHA256withRSA
2 Sent by server pca_pe C=US ST=Minnesota L=St. Paul O=Boston Scientific OU=RM
Fingerprint SHA256: 78a41b1a804eb2b8da36f56588c53e3cc6631ae0e1a238ef9ac2457cc247598b
Pin SHA256: YhW3yUJCxLeDqPrbacS6HIfnNiHDHusffRor9A2AGMo=

RSA 4096 bits (e 65537) / SHA256withRSA
3 Sent by server
  Not in trust store
rmca_sha2_pe   Self-signed
Fingerprint SHA256: 39248f94e0235999b4e582748d4800bd15fd68d406da01a322abb7fdc993e89e
Pin SHA256: cfshgfeOSu0ueFLK+wWcKn2UlfGKBcT2GwMS2BycdgY=

RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server icmprovisioningpre.bostonscientific.com
Fingerprint SHA256: e9f9a1df1edc846f8d6f23a8810159134b0c6e564bdb46e15dc996dba53e6c61
Pin SHA256: SY0R5iEc2dhv7WeYmJ3ghIG3cl6BO3oO4Mqqt7OzGFE=

RSA 4096 bits (e 65537) / SHA256withRSA
2 Sent by server pca_pe C=US ST=Minnesota L=St. Paul O=Boston Scientific OU=RM
Fingerprint SHA256: 78a41b1a804eb2b8da36f56588c53e3cc6631ae0e1a238ef9ac2457cc247598b
Pin SHA256: YhW3yUJCxLeDqPrbacS6HIfnNiHDHusffRor9A2AGMo=

RSA 4096 bits (e 65537) / SHA256withRSA
3 Sent by server
  Not in trust store
rmca_sha2_pe   Self-signed
Fingerprint SHA256: 39248f94e0235999b4e582748d4800bd15fd68d406da01a322abb7fdc993e89e
Pin SHA256: cfshgfeOSu0ueFLK+wWcKn2UlfGKBcT2GwMS2BycdgY=

RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server icmprovisioningpre.bostonscientific.com
Fingerprint SHA256: e9f9a1df1edc846f8d6f23a8810159134b0c6e564bdb46e15dc996dba53e6c61
Pin SHA256: SY0R5iEc2dhv7WeYmJ3ghIG3cl6BO3oO4Mqqt7OzGFE=

RSA 4096 bits (e 65537) / SHA256withRSA
2 Sent by server pca_pe C=US ST=Minnesota L=St. Paul O=Boston Scientific OU=RM
Fingerprint SHA256: 78a41b1a804eb2b8da36f56588c53e3cc6631ae0e1a238ef9ac2457cc247598b
Pin SHA256: YhW3yUJCxLeDqPrbacS6HIfnNiHDHusffRor9A2AGMo=

RSA 4096 bits (e 65537) / SHA256withRSA
3 Sent by server
  Not in trust store
rmca_sha2_pe   Self-signed
Fingerprint SHA256: 39248f94e0235999b4e582748d4800bd15fd68d406da01a322abb7fdc993e89e
Pin SHA256: cfshgfeOSu0ueFLK+wWcKn2UlfGKBcT2GwMS2BycdgY=

RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server icmprovisioningpre.bostonscientific.com
Fingerprint SHA256: e9f9a1df1edc846f8d6f23a8810159134b0c6e564bdb46e15dc996dba53e6c61
Pin SHA256: SY0R5iEc2dhv7WeYmJ3ghIG3cl6BO3oO4Mqqt7OzGFE=

RSA 4096 bits (e 65537) / SHA256withRSA
2 Sent by server pca_pe C=US ST=Minnesota L=St. Paul O=Boston Scientific OU=RM
Fingerprint SHA256: 78a41b1a804eb2b8da36f56588c53e3cc6631ae0e1a238ef9ac2457cc247598b
Pin SHA256: YhW3yUJCxLeDqPrbacS6HIfnNiHDHusffRor9A2AGMo=

RSA 4096 bits (e 65537) / SHA256withRSA
3 Sent by server
  Not in trust store
rmca_sha2_pe   Self-signed
Fingerprint SHA256: 39248f94e0235999b4e582748d4800bd15fd68d406da01a322abb7fdc993e89e
Pin SHA256: cfshgfeOSu0ueFLK+wWcKn2UlfGKBcT2GwMS2BycdgY=

RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1 Sent by server icmprovisioningpre.bostonscientific.com
Fingerprint SHA256: e9f9a1df1edc846f8d6f23a8810159134b0c6e564bdb46e15dc996dba53e6c61
Pin SHA256: SY0R5iEc2dhv7WeYmJ3ghIG3cl6BO3oO4Mqqt7OzGFE=

RSA 4096 bits (e 65537) / SHA256withRSA
2 Sent by server pca_pe C=US ST=Minnesota L=St. Paul O=Boston Scientific OU=RM
Fingerprint SHA256: 78a41b1a804eb2b8da36f56588c53e3cc6631ae0e1a238ef9ac2457cc247598b
Pin SHA256: YhW3yUJCxLeDqPrbacS6HIfnNiHDHusffRor9A2AGMo=

RSA 4096 bits (e 65537) / SHA256withRSA
3 Sent by server
  Not in trust store
rmca_sha2_pe   Self-signed
Fingerprint SHA256: 39248f94e0235999b4e582748d4800bd15fd68d406da01a322abb7fdc993e89e
Pin SHA256: cfshgfeOSu0ueFLK+wWcKn2UlfGKBcT2GwMS2BycdgY=

RSA 4096 bits (e 65537) / SHA256withRSA

Click here to expand

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


Cipher Suites
# TLS 1.2 (suites in server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)   ECDH secp384r1 (eq. 7680 bits RSA)   FS 256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)   ECDH secp384r1 (eq. 7680 bits RSA)   FS   WEAK 256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (0xc028)   ECDH secp384r1 (eq. 7680 bits RSA)   FS   WEAK 256
TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (0xcca8)   ECDH secp384r1 (eq. 7680 bits RSA)   FS 256
TLS_RSA_WITH_AES_256_GCM_SHA384 (0x9d)   WEAK 256
TLS_RSA_WITH_AES_256_CCM (0xc09d)   WEAK 256
TLS_RSA_WITH_AES_256_CCM_8 (0xc0a1)   WEAK 256
TLS_RSA_WITH_AES_256_CBC_SHA (0x35)   WEAK 256
TLS_RSA_WITH_AES_256_CBC_SHA256 (0x3d)   WEAK 256
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x84)   WEAK 256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f)   DH 2048 bits   FS 256
TLS_DHE_RSA_WITH_AES_256_CCM (0xc09f)   DH 2048 bits   FS 256
TLS_DHE_RSA_WITH_AES_256_CCM_8 (0xc0a3)   DH 2048 bits   FS 256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39)   DH 2048 bits   FS   WEAK 256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (0x6b)   DH 2048 bits   FS   WEAK 256
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x88)   DH 2048 bits   FS   WEAK 256
# TLS 1.1 (suites in server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)   ECDH secp384r1 (eq. 7680 bits RSA)   FS   WEAK 256
TLS_RSA_WITH_AES_256_CBC_SHA (0x35)   WEAK 256
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x84)   WEAK 256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39)   DH 2048 bits   FS   WEAK 256
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x88)   DH 2048 bits   FS   WEAK 256
# TLS 1.0 (suites in server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014)   ECDH secp384r1 (eq. 7680 bits RSA)   FS   WEAK 256
TLS_RSA_WITH_AES_256_CBC_SHA (0x35)   WEAK 256
TLS_RSA_WITH_CAMELLIA_256_CBC_SHA (0x84)   WEAK 256
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39)   DH 2048 bits   FS   WEAK 256
TLS_DHE_RSA_WITH_CAMELLIA_256_CBC_SHA (0x88)   DH 2048 bits   FS   WEAK 256


Handshake Simulation
Android 2.3.7   No SNI 2 Server sent fatal alert: handshake_failure
Android 4.0.4 RSA 4096 (SHA256)   TLS 1.0 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Android 4.1.1 RSA 4096 (SHA256)   TLS 1.0 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Android 4.2.2 RSA 4096 (SHA256)   TLS 1.0 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Android 4.3 RSA 4096 (SHA256)   TLS 1.0 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Android 4.4.2 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Android 5.0.0 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Android 6.0 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Android 7.0 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Android 8.0 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Android 8.1 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Android 9.0 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Baidu Jan 2015 RSA 4096 (SHA256)   TLS 1.0 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
BingPreview Jan 2015 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Chrome 49 / XP SP3 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Chrome 69 / Win 7  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Chrome 70 / Win 10 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Chrome 80 / Win 10  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Firefox 31.3.0 ESR / Win 7 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Firefox 47 / Win 7  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Firefox 49 / XP SP3 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Firefox 62 / Win 7  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Firefox 73 / Win 10  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Googlebot Feb 2018 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
IE 7 / Vista RSA 4096 (SHA256)   TLS 1.0 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
IE 8 / XP   No FS 1   No SNI 2 Server sent fatal alert: handshake_failure
IE 8-10 / Win 7  R RSA 4096 (SHA256)   TLS 1.0 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
IE 11 / Win 7  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
IE 11 / Win 8.1  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
IE 10 / Win Phone 8.0 RSA 4096 (SHA256)   TLS 1.0 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
IE 11 / Win Phone 8.1  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
IE 11 / Win Phone 8.1 Update  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
IE 11 / Win 10  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Edge 15 / Win 10  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Edge 16 / Win 10  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Edge 18 / Win 10  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Edge 13 / Win Phone 10  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Java 6u45   No SNI 2 Server sent fatal alert: handshake_failure
Java 7u25 Server sent fatal alert: handshake_failure
Java 8u161 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Java 11.0.3 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Java 12.0.1 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
OpenSSL 0.9.8y RSA 4096 (SHA256)   TLS 1.0 TLS_RSA_WITH_AES_256_CBC_SHA  No FS
OpenSSL 1.0.1l  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
OpenSSL 1.0.2s  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
OpenSSL 1.1.0k  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
OpenSSL 1.1.1c  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 5.1.9 / OS X 10.6.8 RSA 4096 (SHA256)   TLS 1.0 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Safari 6 / iOS 6.0.1 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Safari 6.0.4 / OS X 10.8.4  R RSA 4096 (SHA256)   TLS 1.0 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Safari 7 / iOS 7.1  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Safari 7 / OS X 10.9  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Safari 8 / iOS 8.4  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Safari 8 / OS X 10.10  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA   ECDH secp384r1  FS
Safari 9 / iOS 9  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 9 / OS X 10.11  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 10 / iOS 10  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 10 / OS X 10.12  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 12.1.2 / MacOS 10.14.6 Beta  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Safari 12.1.1 / iOS 12.3.1  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Apple ATS 9 / iOS 9  R RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
Yahoo Slurp Jan 2015 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
YandexBot Jan 2015 RSA 4096 (SHA256)   TLS 1.2 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384   ECDH secp384r1  FS
# Not simulated clients (Protocol mismatch)
IE 6 / XP   No FS 1   No SNI 2 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 Not mitigated server-side (more info)   TLS 1.0: 0xc014
POODLE (SSLv3) No, SSL 3 not supported (more info)
POODLE (TLS) No (more info)
Zombie POODLE Unknown (more info)
GOLDENDOODLE Unknown (more info)
OpenSSL 0-Length Unknown (more info)
Sleeping POODLE Unknown (more info)
Downgrade attack prevention Yes, TLS_FALLBACK_SCSV supported (more info)
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 With modern browsers (more info)
ALPN No
NPN No
Session resumption (caching) Unknown
Session resumption (tickets) No
OCSP stapling No
Strict Transport Security (HSTS) Unknown (failed HTTP request?)
HSTS Preloading Not in: Chrome  Edge  Firefox  IE 
Public Key Pinning (HPKP) Unknown (failed HTTP request?)
Public Key Pinning Report-Only Unknown (failed HTTP request?)
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
DH public server param (Ys) reuse No
ECDH public server param reuse No
Supported Named Groups secp384r1, secp256r1, x25519 (server preferred order)
SSL 2 handshake compatibility Yes


HTTP Requests
1 https://icmprovisioningpre.bostonscientific.com/  (Request failed)


Miscellaneous
Test date Fri, 13 Jun 2025 05:26:39 UTC
Test duration 87.907 seconds
HTTP status code Request failed
HTTP server signature Unknown
Server hostname ec2-34-225-98-95.compute-1.amazonaws.com


Why is my certificate not trusted?

There are many reasons why a certificate may not be trusted. The exact problem is indicated on the report card in bright red. The problems fall into three categories:

  1. Invalid certificate
  2. Invalid configuration
  3. Unknown Certificate Authority

1. Invalid certificate

A certificate is invalid if:

2. Invalid configuration

In some cases, the certificate chain does not contain all the necessary certificates to connect the web server certificate to one of the root certificates in our trust store. Less commonly, one of the certificates in the chain (other than the web server certificate) will have expired, and that invalidates the entire chain.

3. Unknown Certificate Authority

In order for trust to be established, we must have the root certificate of the signing Certificate Authority in our trust store. SSL Labs does not maintain its own trust store; instead we use the store maintained by Mozilla.

If we mark a web site as not trusted, that means that the average web user's browser will not trust it either. For certain special groups of users, such web sites can still be secure. For example, if you can securely verify that a self-signed web site is operated by a person you trust, then you can trust that self-signed web site too. Or, if you work for an organisation that manages its own trust, and you have their own root certificate already embedded in your browser. Such special cases do not work for the general public, however, and this is what we indicate on our report card.

4. Interoperability issues

In some rare cases trust cannot be established because of interoperability issues between our code and the code or configuration running on the server. We manually review such cases, but if you encounter such an issue please feel free to contact us. Such problems are very difficult to troubleshoot and you may be able to provide us with information that might help us determine the root cause.

SSL Report v2.4.0