Certification Paths |
|
Server Key and Certificate #1
|
|
| Subject |
mail.mercia.cz
Fingerprint SHA256: 42a7cd05986eb48b7e68b29d6eadb986b583a83e83d2416d310e5ccf3cf44f2f Pin SHA256: f2KsSefegcOn47M/KDEaCRxueRbBIirD4EKhbS9bZf8= |
| Common names | mail.mercia.cz |
| Alternative names | mail.mercia.cz srv-mail.mercia.lan |
| Serial Number | 008e47eb04 |
| Valid from | Wed, 27 May 2020 00:00:00 UTC |
| Valid until | Fri, 05 Apr 2030 23:59:59 UTC (expires in 4 years and 8 months) |
| Key | RSA 3072 bits (e 65537) |
| Weak key (Debian) | No |
| Issuer | Auto Mercia CA
|
| Signature algorithm | SHA512withRSA |
| Extended Validation | No |
| Certificate Transparency | No |
| OCSP Must Staple | No |
| Revocation information |
CRL CRL: http://crl.mercia.cz/crl/crl.pem |
| Revocation status | Unchecked (only trusted certificates can be checked) |
| DNS CAA | Yes policy host: mercia.cz issue: letsencrypt.org flags:0 issue: digicert.com flags:0 |
| Trusted | No NOT TRUSTED
(Why?)
Mozilla Apple Android Java Windows |
|
Certification Paths |
| Protocols | |
| TLS 1.3 | Yes |
| TLS 1.2 | No |
| TLS 1.1 | No |
| TLS 1.0 | No |
| SSL 3 | No |
| SSL 2 | No |
| Cipher Suites | ||
|
# TLS 1.3 (suites in server-preferred order)
|
||
TLS_AES_256_GCM_SHA384 (0x1302)
ECDH secp256r1 (eq. 3072 bits RSA) FS
|
256 | |
TLS_CHACHA20_POLY1305_SHA256 (0x1303)
ECDH secp256r1 (eq. 3072 bits RSA) FS
|
256 | |
TLS_AES_128_GCM_SHA256 (0x1301)
ECDH secp256r1 (eq. 3072 bits RSA) FS
|
128 | |
| Handshake Simulation | |||
| Android 8.1 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Android 9.0 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Chrome 69 / Win 7 R |
Server sent fatal alert: handshake_failure |
||
| Chrome 70 / Win 10 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Chrome 80 / Win 10 R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Firefox 62 / Win 7 R |
Server sent fatal alert: handshake_failure |
||
| Firefox 73 / Win 10 R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Java 11.0.3 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Java 12.0.1 | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| OpenSSL 1.1.0k R |
Server sent fatal alert: handshake_failure |
||
| OpenSSL 1.1.1c R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Safari 12.1.2 / MacOS 10.14.6 Beta R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp256r1 FS |
| Safari 12.1.1 / iOS 12.3.1 R | - | TLS 1.3 | TLS_AES_256_GCM_SHA384 ECDH secp256r1 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) |
||
| Android 4.4.2 |
Protocol mismatch (not simulated) |
||
| Android 5.0.0 |
Protocol mismatch (not simulated) |
||
| Android 6.0 |
Protocol mismatch (not simulated) |
||
| Android 7.0 |
Protocol mismatch (not simulated) |
||
| Android 8.0 |
Protocol mismatch (not simulated) |
||
| Baidu Jan 2015 |
Protocol mismatch (not simulated) |
||
| BingPreview Jan 2015 |
Protocol mismatch (not simulated) |
||
| Chrome 49 / XP SP3 |
Protocol mismatch (not simulated) |
||
| Firefox 31.3.0 ESR / Win 7 |
Protocol mismatch (not simulated) |
||
| Firefox 47 / Win 7 R |
Protocol mismatch (not simulated) |
||
| Firefox 49 / XP SP3 |
Protocol mismatch (not simulated) |
||
| Googlebot Feb 2018 |
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 11 / Win 7 R |
Protocol mismatch (not simulated) |
||
| IE 11 / Win 8.1 R |
Protocol mismatch (not simulated) |
||
| IE 10 / Win Phone 8.0 |
Protocol mismatch (not simulated) |
||
| IE 11 / Win Phone 8.1 R |
Protocol mismatch (not simulated) |
||
| IE 11 / Win Phone 8.1 Update R |
Protocol mismatch (not simulated) |
||
| IE 11 / Win 10 R |
Protocol mismatch (not simulated) |
||
| Edge 15 / Win 10 R |
Protocol mismatch (not simulated) |
||
| Edge 16 / Win 10 R |
Protocol mismatch (not simulated) |
||
| Edge 18 / Win 10 R |
Protocol mismatch (not simulated) |
||
| Edge 13 / Win Phone 10 R |
Protocol mismatch (not simulated) |
||
| Java 6u45 No SNI 2 |
Protocol mismatch (not simulated) |
||
| Java 7u25 |
Protocol mismatch (not simulated) |
||
| Java 8u161 |
Protocol mismatch (not simulated) |
||
| OpenSSL 0.9.8y |
Protocol mismatch (not simulated) |
||
| OpenSSL 1.0.1l R |
Protocol mismatch (not simulated) |
||
| OpenSSL 1.0.2s R |
Protocol mismatch (not simulated) |
||
| Safari 5.1.9 / OS X 10.6.8 |
Protocol mismatch (not simulated) |
||
| Safari 6 / iOS 6.0.1 |
Protocol mismatch (not simulated) |
||
| Safari 6.0.4 / OS X 10.8.4 R |
Protocol mismatch (not simulated) |
||
| Safari 7 / iOS 7.1 R |
Protocol mismatch (not simulated) |
||
| Safari 7 / OS X 10.9 R |
Protocol mismatch (not simulated) |
||
| Safari 8 / iOS 8.4 R |
Protocol mismatch (not simulated) |
||
| Safari 8 / OS X 10.10 R |
Protocol mismatch (not simulated) |
||
| Safari 9 / iOS 9 R |
Protocol mismatch (not simulated) |
||
| Safari 9 / OS X 10.11 R |
Protocol mismatch (not simulated) |
||
| Safari 10 / iOS 10 R |
Protocol mismatch (not simulated) |
||
| Safari 10 / OS X 10.12 R |
Protocol mismatch (not simulated) |
||
| Apple ATS 9 / iOS 9 R |
Protocol mismatch (not simulated) |
||
| Yahoo Slurp Jan 2015 |
Protocol mismatch (not simulated) |
||
| YandexBot Jan 2015 |
Protocol mismatch (not simulated) |
||
| (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 | |
| ROBOT (vulnerability) | No (more info) |
| Forward Secrecy | Yes (with most browsers) ROBUST (more info) |
| ALPN | Yes http/1.1 |
| Session resumption (tickets) | No |
| OCSP stapling | Yes |
| Strict Transport Security (HSTS) | Yes
max-age=63072000; 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) |
| Supported Named Groups | secp256r1, secp384r1, secp521r1 (server preferred order) |
| SSL 2 handshake compatibility | No |
| 0-RTT enabled | No |
|
HTTP Requests
|
|
1 https://mail.mercia.cz/
(HTTP/1.1 200 OK)
| 1 | |
| Date | Thu, 17 Jul 2025 07:28:26 GMT | |
| Server | Apache/2.4.43 (Unix) OpenSSL/1.1.1 PHP/7.4.4 | |
| Strict-Transport-Security | max-age=63072000; includeSubdomains; preload | |
| X-Frame-Options | SAMEORIGIN | |
| Referrer-Policy | same-origin | |
| Last-Modified | Tue, 26 May 2020 20:53:55 GMT | |
| ETag | "118-5a6934b2f5a95" | |
| Accept-Ranges | bytes | |
| Content-Length | 280 | |
| X-Content-Type-Options | nosniff | |
| Connection | close | |
| Content-Type | text/html | |
| Miscellaneous | |
| Test date | Thu, 17 Jul 2025 07:28:17 UTC |
| Test duration | 32.117 seconds |
| HTTP status code | 200 |
| HTTP server signature | Apache/2.4.43 (Unix) OpenSSL/1.1.1 PHP/7.4.4 |
| Server hostname | mail.mercia.cz |
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.1