SSL Server Test: cp.dipucuenca.es (Powered by Qualys SSL Labs)

SSL Report: cp.dipucuenca.es (195.235.94.25)

Assessed on: Mon, 09 Jun 2025 07:46:10 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

If trust issues are ignored: B

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.

Intermediate certificate has an insecure signature. When renewing, ensure you upgrade to an all-SHA2 chain. MORE INFO »

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 2048 bits (SHA256withRSA)

Server Key and Certificate #1
Subject	*.dipucuenca.es Fingerprint SHA256: bf9f13377eeb3736426bf27c8abe3387e109abbc25340e1577beab0542bf93e1 Pin SHA256: SAf2uiEVzPV6L3ck6gEzNq0B74GY0BCyheKT0H63cZ0=
Common names	*.dipucuenca.es
Alternative names	*.dipucuenca.es dipucuenca.es
Serial Number	4b5fdf0fed40a7716704db6f35b4b0d1
Valid from	Tue, 08 Oct 2024 07:12:47 UTC
Valid until	Wed, 08 Oct 2025 07:12:47 UTC (expires in 3 months and 28 days)
Key	RSA 2048 bits (e 65537)
Weak key (Debian)	No
Issuer	FNMT-RCM AIA: http://www.cert.fnmt.es/certs/ACCOMP.crt
Signature algorithm	SHA256withRSA
Extended Validation	No
Certificate Transparency	Yes (certificate)
OCSP Must Staple	No
Revocation information	CRL, OCSP CRL: http://www.cert.fnmt.es/crlscomp/CRL3.crl OCSP: http://ocspcomp.cert.fnmt.es/ocsp/OcspResponder
Revocation status	Good (not revoked)
DNS CAA	No (more info)
Trusted	No NOT TRUSTED (Why?) Mozilla Apple Android Java Windows

Additional Certificates (if supplied)
Certificates provided	2 (3635 bytes)
Chain issues	None
#2
Subject	FNMT-RCM / AC Componentes Informáticos Fingerprint SHA256: db0da16032f1643a2496fde742e2bbe81daca58cd7612061420e154ce1bce2bd Pin SHA256: MEJWDQI0WXBrEdYtj1u1WdwD26XsIXQQ+57NkgXsoGc=
Valid until	Tue, 27 Jun 2028 14:17:50 UTC (expires in 3 years)
Key	RSA 2048 bits (e 65537)
Issuer	FNMT-RCM / AC RAIZ FNMT-RCM
Signature algorithm	SHA1withRSA INSECURE

Certification Paths


Path #1: Not trusted (invalid certificate [Fingerprint SHA256: db0da16032f1643a2496fde742e2bbe81daca58cd7612061420e154ce1bce2bd])
1	Sent by server	*.dipucuenca.es Fingerprint SHA256: bf9f13377eeb3736426bf27c8abe3387e109abbc25340e1577beab0542bf93e1 Pin SHA256: SAf2uiEVzPV6L3ck6gEzNq0B74GY0BCyheKT0H63cZ0= RSA 2048 bits (e 65537) / SHA256withRSA
2	Sent by server	FNMT-RCM / AC Componentes Informáticos Fingerprint SHA256: db0da16032f1643a2496fde742e2bbe81daca58cd7612061420e154ce1bce2bd Pin SHA256: MEJWDQI0WXBrEdYtj1u1WdwD26XsIXQQ+57NkgXsoGc= RSA 2048 bits (e 65537) / SHA1withRSA INSECURE SIGNATURE
3	In trust store	FNMT-RCM / AC RAIZ FNMT-RCM Self-signed Fingerprint SHA256: ebc5570c29018c4d67b1aa127baf12f703b4611ebc17b7dab5573894179b93fa Pin SHA256: L8VmekuaJnjtasatJUZfy/YJS/zZUECXx6j6R63l6Ig= RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (invalid certificate [Fingerprint SHA256: db0da16032f1643a2496fde742e2bbe81daca58cd7612061420e154ce1bce2bd])
1	Sent by server	*.dipucuenca.es Fingerprint SHA256: bf9f13377eeb3736426bf27c8abe3387e109abbc25340e1577beab0542bf93e1 Pin SHA256: SAf2uiEVzPV6L3ck6gEzNq0B74GY0BCyheKT0H63cZ0= RSA 2048 bits (e 65537) / SHA256withRSA
2	Sent by server	FNMT-RCM / AC Componentes Informáticos Fingerprint SHA256: db0da16032f1643a2496fde742e2bbe81daca58cd7612061420e154ce1bce2bd Pin SHA256: MEJWDQI0WXBrEdYtj1u1WdwD26XsIXQQ+57NkgXsoGc= RSA 2048 bits (e 65537) / SHA1withRSA INSECURE SIGNATURE
3	In trust store	FNMT-RCM / AC RAIZ FNMT-RCM Self-signed Fingerprint SHA256: ebc5570c29018c4d67b1aa127baf12f703b4611ebc17b7dab5573894179b93fa Pin SHA256: L8VmekuaJnjtasatJUZfy/YJS/zZUECXx6j6R63l6Ig= RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (invalid certificate [Fingerprint SHA256: db0da16032f1643a2496fde742e2bbe81daca58cd7612061420e154ce1bce2bd])
1	Sent by server	*.dipucuenca.es Fingerprint SHA256: bf9f13377eeb3736426bf27c8abe3387e109abbc25340e1577beab0542bf93e1 Pin SHA256: SAf2uiEVzPV6L3ck6gEzNq0B74GY0BCyheKT0H63cZ0= RSA 2048 bits (e 65537) / SHA256withRSA
2	Sent by server	FNMT-RCM / AC Componentes Informáticos Fingerprint SHA256: db0da16032f1643a2496fde742e2bbe81daca58cd7612061420e154ce1bce2bd Pin SHA256: MEJWDQI0WXBrEdYtj1u1WdwD26XsIXQQ+57NkgXsoGc= RSA 2048 bits (e 65537) / SHA1withRSA INSECURE SIGNATURE
3	In trust store	FNMT-RCM / AC RAIZ FNMT-RCM Self-signed Fingerprint SHA256: ebc5570c29018c4d67b1aa127baf12f703b4611ebc17b7dab5573894179b93fa Pin SHA256: L8VmekuaJnjtasatJUZfy/YJS/zZUECXx6j6R63l6Ig= RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (path does not chain to a trusted anchor)
1	Sent by server	*.dipucuenca.es Fingerprint SHA256: bf9f13377eeb3736426bf27c8abe3387e109abbc25340e1577beab0542bf93e1 Pin SHA256: SAf2uiEVzPV6L3ck6gEzNq0B74GY0BCyheKT0H63cZ0= RSA 2048 bits (e 65537) / SHA256withRSA
2	Sent by server	FNMT-RCM / AC Componentes Informáticos Fingerprint SHA256: db0da16032f1643a2496fde742e2bbe81daca58cd7612061420e154ce1bce2bd Pin SHA256: MEJWDQI0WXBrEdYtj1u1WdwD26XsIXQQ+57NkgXsoGc= RSA 2048 bits (e 65537) / SHA1withRSA INSECURE SIGNATURE
3	Extra download Not in trust store	FNMT-RCM / AC RAIZ FNMT-RCM Self-signed Fingerprint SHA256: ebc5570c29018c4d67b1aa127baf12f703b4611ebc17b7dab5573894179b93fa Pin SHA256: L8VmekuaJnjtasatJUZfy/YJS/zZUECXx6j6R63l6Ig= RSA 4096 bits (e 65537) / SHA256withRSA
Path #1: Not trusted (invalid certificate [Fingerprint SHA256: db0da16032f1643a2496fde742e2bbe81daca58cd7612061420e154ce1bce2bd])
1	Sent by server	*.dipucuenca.es Fingerprint SHA256: bf9f13377eeb3736426bf27c8abe3387e109abbc25340e1577beab0542bf93e1 Pin SHA256: SAf2uiEVzPV6L3ck6gEzNq0B74GY0BCyheKT0H63cZ0= RSA 2048 bits (e 65537) / SHA256withRSA
2	Sent by server	FNMT-RCM / AC Componentes Informáticos Fingerprint SHA256: db0da16032f1643a2496fde742e2bbe81daca58cd7612061420e154ce1bce2bd Pin SHA256: MEJWDQI0WXBrEdYtj1u1WdwD26XsIXQQ+57NkgXsoGc= RSA 2048 bits (e 65537) / SHA1withRSA INSECURE SIGNATURE
3	In trust store	FNMT-RCM / AC RAIZ FNMT-RCM Self-signed Fingerprint SHA256: 4d9ebb28825c9643ab15d54e5f9614f13cb3e95de3cf4eac971301f320f9226e Pin SHA256: L8VmekuaJnjtasatJUZfy/YJS/zZUECXx6j6R63l6Ig= RSA 4096 bits (e 65537) / SHA1withRSA Weak or insecure signature, but no impact on root certificate
Path #2: Not trusted (invalid certificate [Fingerprint SHA256: db0da16032f1643a2496fde742e2bbe81daca58cd7612061420e154ce1bce2bd])
1	Sent by server	*.dipucuenca.es Fingerprint SHA256: bf9f13377eeb3736426bf27c8abe3387e109abbc25340e1577beab0542bf93e1 Pin SHA256: SAf2uiEVzPV6L3ck6gEzNq0B74GY0BCyheKT0H63cZ0= RSA 2048 bits (e 65537) / SHA256withRSA
2	Sent by server	FNMT-RCM / AC Componentes Informáticos Fingerprint SHA256: db0da16032f1643a2496fde742e2bbe81daca58cd7612061420e154ce1bce2bd Pin SHA256: MEJWDQI0WXBrEdYtj1u1WdwD26XsIXQQ+57NkgXsoGc= RSA 2048 bits (e 65537) / SHA1withRSA INSECURE SIGNATURE
3	In trust store	FNMT-RCM / AC RAIZ FNMT-RCM Self-signed Fingerprint SHA256: ebc5570c29018c4d67b1aa127baf12f703b4611ebc17b7dab5573894179b93fa Pin SHA256: L8VmekuaJnjtasatJUZfy/YJS/zZUECXx6j6R63l6Ig= 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 x25519 (eq. 3072 bits RSA) FS	256
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (`0xc02f`) ECDH x25519 (eq. 3072 bits RSA) FS	128
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (`0x9f`) DH 2048 bits FS	256
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (`0x9e`) DH 2048 bits FS	128
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (`0xc028`) ECDH x25519 (eq. 3072 bits RSA) FS WEAK	256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (`0xc027`) ECDH x25519 (eq. 3072 bits RSA) FS WEAK	128
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (`0xc014`) ECDH x25519 (eq. 3072 bits RSA) FS WEAK	256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (`0xc013`) ECDH x25519 (eq. 3072 bits RSA) FS WEAK	128
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (`0x39`) DH 2048 bits FS WEAK	256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (`0x33`) DH 2048 bits FS WEAK	128
TLS_RSA_WITH_AES_256_GCM_SHA384 (`0x9d`) WEAK	256
TLS_RSA_WITH_AES_128_GCM_SHA256 (`0x9c`) WEAK	128
TLS_RSA_WITH_AES_256_CBC_SHA256 (`0x3d`) WEAK	256
TLS_RSA_WITH_AES_128_CBC_SHA256 (`0x3c`) WEAK	128
TLS_RSA_WITH_AES_256_CBC_SHA (`0x35`) WEAK	256
TLS_RSA_WITH_AES_128_CBC_SHA (`0x2f`) WEAK	128
# TLS 1.1 (suites in server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (`0xc014`) ECDH x25519 (eq. 3072 bits RSA) FS WEAK	256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (`0xc013`) ECDH x25519 (eq. 3072 bits RSA) FS WEAK	128
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (`0x39`) DH 2048 bits FS WEAK	256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (`0x33`) DH 2048 bits FS WEAK	128
TLS_RSA_WITH_AES_256_CBC_SHA (`0x35`) WEAK	256
TLS_RSA_WITH_AES_128_CBC_SHA (`0x2f`) WEAK	128
# TLS 1.0 (suites in server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (`0xc014`) ECDH x25519 (eq. 3072 bits RSA) FS WEAK	256
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (`0xc013`) ECDH x25519 (eq. 3072 bits RSA) FS WEAK	128
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (`0x39`) DH 2048 bits FS WEAK	256
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (`0x33`) DH 2048 bits FS WEAK	128
TLS_RSA_WITH_AES_256_CBC_SHA (`0x35`) WEAK	256
TLS_RSA_WITH_AES_128_CBC_SHA (`0x2f`) WEAK	128

Handshake Simulation
Android 2.3.7 No SNI ²	RSA 2048 (SHA256)	TLS 1.0	TLS_DHE_RSA_WITH_AES_128_CBC_SHA DH 2048 FS
Android 4.0.4	RSA 2048 (SHA256)	TLS 1.0	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA ECDH secp256r1 FS
Android 4.1.1	RSA 2048 (SHA256)	TLS 1.0	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA ECDH secp256r1 FS
Android 4.2.2	RSA 2048 (SHA256)	TLS 1.0	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA ECDH secp256r1 FS
Android 4.3	RSA 2048 (SHA256)	TLS 1.0	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA ECDH secp256r1 FS
Android 4.4.2	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Android 5.0.0	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS
Android 6.0	RSA 2048 (SHA256)	TLS 1.2 > http/1.1	TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS
Android 7.0	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Android 8.0	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Android 8.1	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Android 9.0	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Baidu Jan 2015	RSA 2048 (SHA256)	TLS 1.0	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA ECDH secp256r1 FS
BingPreview Jan 2015	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Chrome 49 / XP SP3	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS
Chrome 69 / Win 7 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Chrome 70 / Win 10	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Chrome 80 / Win 10 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Firefox 31.3.0 ESR / Win 7	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS
Firefox 47 / Win 7 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 ECDH secp256r1 FS
Firefox 49 / XP SP3	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Firefox 62 / Win 7 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Firefox 73 / Win 10 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Googlebot Feb 2018	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
IE 7 / Vista	RSA 2048 (SHA256)	TLS 1.0	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA ECDH secp256r1 FS
IE 8 / XP No FS ¹ No SNI ²	Server closed connection
IE 8-10 / Win 7 R	RSA 2048 (SHA256)	TLS 1.0	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA ECDH secp256r1 FS
IE 11 / Win 7 R	RSA 2048 (SHA256)	TLS 1.2	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 2048 FS
IE 11 / Win 8.1 R	RSA 2048 (SHA256)	TLS 1.2 > http/1.1	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 2048 FS
IE 10 / Win Phone 8.0	RSA 2048 (SHA256)	TLS 1.0	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA ECDH secp256r1 FS
IE 11 / Win Phone 8.1 R	RSA 2048 (SHA256)	TLS 1.2 > http/1.1	TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 ECDH secp256r1 FS
IE 11 / Win Phone 8.1 Update R	RSA 2048 (SHA256)	TLS 1.2 > http/1.1	TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 DH 2048 FS
IE 11 / Win 10 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Edge 15 / Win 10 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Edge 16 / Win 10 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Edge 18 / Win 10 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Edge 13 / Win Phone 10 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Java 6u45 No SNI ²	Client does not support DH parameters > 1024 bits RSA 2048 (SHA256) \| TLS 1.0 \| TLS_DHE_RSA_WITH_AES_128_CBC_SHA \| DH 2048
Java 7u25	RSA 2048 (SHA256)	TLS 1.0	TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA ECDH secp256r1 FS
Java 8u161	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Java 11.0.3	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Java 12.0.1	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
OpenSSL 0.9.8y	RSA 2048 (SHA256)	TLS 1.0	TLS_DHE_RSA_WITH_AES_256_CBC_SHA DH 2048 FS
OpenSSL 1.0.1l R	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
OpenSSL 1.0.2s R	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
OpenSSL 1.1.0k R	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
OpenSSL 1.1.1c R	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Safari 5.1.9 / OS X 10.6.8	RSA 2048 (SHA256)	TLS 1.0	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA ECDH secp256r1 FS
Safari 6 / iOS 6.0.1	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ECDH secp256r1 FS
Safari 6.0.4 / OS X 10.8.4 R	RSA 2048 (SHA256)	TLS 1.0	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA ECDH secp256r1 FS
Safari 7 / iOS 7.1 R	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ECDH secp256r1 FS
Safari 7 / OS X 10.9 R	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ECDH secp256r1 FS
Safari 8 / iOS 8.4 R	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ECDH secp256r1 FS
Safari 8 / OS X 10.10 R	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 ECDH secp256r1 FS
Safari 9 / iOS 9 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Safari 9 / OS X 10.11 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Safari 10 / iOS 10 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Safari 10 / OS X 10.12 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Safari 12.1.2 / MacOS 10.14.6 Beta R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Safari 12.1.1 / iOS 12.3.1 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH x25519 FS
Apple ATS 9 / iOS 9 R	RSA 2048 (SHA256)	TLS 1.2 > h2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
Yahoo Slurp Jan 2015	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
YandexBot Jan 2015	RSA 2048 (SHA256)	TLS 1.2	TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 ECDH secp256r1 FS
# Not simulated clients (Protocol mismatch)
IE 6 / XP No FS ¹ No SNI ²	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	No (more info) TLS 1.2 : `0xc027`
GOLDENDOODLE	No (more info) TLS 1.2 : `0xc027`
OpenSSL 0-Length	No (more info) TLS 1.2 : `0xc027`
Sleeping POODLE	No (more info) TLS 1.2 : `0xc027`
Downgrade attack prevention	No, TLS_FALLBACK_SCSV not 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	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 (not verified because the certificate is not trusted)
Strict Transport Security (HSTS)	No
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
DH public server param (Ys) reuse	No
ECDH public server param reuse	Yes
Supported Named Groups	x25519, secp256r1, secp384r1 (server preferred order)
SSL 2 handshake compatibility	Yes

HTTP Requests

1 https://cp.dipucuenca.es/ (HTTP/1.1 200 OK)
1
	Cache-Control	no-store, no-cache, must-revalidate,post-check=0, pre-check=0
	Pragma	no-cache
	Content-Type	text/html; charset="iso-8859-1"
	Expires	Tue, 03 Jul 2001 06:00:00 GMT
	Last-Modified	Mon, 09 Jun 2025 07:43:48 GMT
	Server	Microsoft-IIS/10.0
	X-UA-Compatible	IE=Edge
	X-Frame-Options	SAMEORIGIN
	X-XSS-Protection	1; mode=block
	X-Content-Type-Options	nosniff
	X-Permitted-Cross-Domain-Policies	none
	X-Powered-By	ASP.NET
	Date	Mon, 09 Jun 2025 07:43:48 GMT
	Connection	close
	Content-Length	497

Miscellaneous
Test date	Mon, 09 Jun 2025 07:43:20 UTC
Test duration	169.308 seconds
HTTP status code	200
HTTP server signature	Microsoft-IIS/10.0
Server hostname	cp.dipucuenca.es

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:

Invalid certificate
Invalid configuration
Unknown Certificate Authority

1. Invalid certificate

A certificate is invalid if:

It is used before its activation date
It is used after its expiry date
Certificate hostnames don't match the site hostname
It has been revoked
It has insecure signature
It has been blacklisted

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

Copyright © 2009-2025 Qualys, Inc. All Rights Reserved. Privacy Policy.	Terms and Conditions
Try Qualys for free! Experience the award-winning Qualys Cloud Platform and the entire collection of Qualys Cloud Apps, including certificate security solutions.