SSL check results of mail.tomlab.cz

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.tomlab.cz can be reached through a secure connection.

To establish a secure connection a mail server has to offer STARTTLS (SSL), a trustworthy SSL certificate, support for the Diffie-Hellman-Algorithm to guarantee Perfect Forward Secrecy and must not be vulnerable against the Heartbleed attack. Futhermore we recommend using end-to-end encryption with GnuPG.

Summary

Report created Mon, 22 Feb 2021 19:17:52 +0000

We can not guarantee a secure connection to the mailservers of mail.tomlab.cz!

Please contact the operator of mail.tomlab.cz and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/mail.tomlab.cz

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.tomlab.cz addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.tomlab.cz
85.255.10.242
Results incomplete
-
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
17 s
mail.tomlab.cz
2001:15e8:110:22f2::1
-
supported
mail.tomlab.cz
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
59 s

Outgoing Mails

We have not received any emails from a @mail.tomlab.cz address so far. Test mail delivery

Certificates

First seen at:

CN=mail.tomlab.cz

Certificate chain
  • mail.tomlab.cz
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • mail.tomlab.cz
Alternative Names
  • mail.tomlab.cz
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-01-23
Not valid after
2021-04-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D3:B1:04:32:8F:13:E1:82:70:38:83:4A:93:9E:32:85:C4:0F:52:DB:67:CA:00:66:0D:D7:A4:70:4A:6C:01:07
SHA1
17:8E:A8:D2:5A:41:44:30:DF:DF:66:84:CE:17:26:AA:AB:A9:87:05
X509v3 extensions
subjectKeyIdentifier
  • 58:9A:16:E5:74:73:2C:0F:17:45:5A:71:83:30:E7:6C:82:F6:4F:FE
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : Jan 23 21:26:12.849 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:97:53:A4:CF:75:99:20:6F:9D:F8:96:
  • DB:FC:42:F2:FE:1E:28:BD:2B:04:3F:BC:1B:D4:DD:56:
  • DC:4B:66:1F:F1:02:21:00:C7:82:3B:F3:52:E1:75:E2:
  • 91:45:84:19:69:CB:7A:48:7A:D4:0D:2E:C4:2E:BA:D7:
  • C5:23:70:9A:15:57:9B:07
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Jan 23 21:26:12.934 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E8:48:4E:8B:9A:7B:CF:24:E7:ED:0D:
  • 22:CD:9F:B6:E8:6A:BA:27:27:45:7C:5B:49:02:80:D8:
  • 71:F3:5E:A8:9E:02:21:00:FF:31:4B:A1:11:C1:2A:9B:
  • D4:46:2F:94:C9:B6:2F:3F:73:1C:D8:0E:CC:3B:B8:C1:
  • 8F:10:B7:56:15:AB:CE:C7