SSL-Tools

SSL check results of mail.spamassassin.cz

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.spamassassin.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

JSON Refresh

Report created Thu, 28 Mar 2024 13:25:15 +0000

The mailservers of mail.spamassassin.cz can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.spamassassin.cz
2a02:2b88:6:52e0::777
 0
supported
mail.spamassassin.cz
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
12 s
mail.spamassassin.cz
31.31.74.35
 0
supported
mail.spamassassin.cz
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
13 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.spamassassin.cz

Certificate chain
  • mail.spamassassin.cz
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.spamassassin.cz
Alternative Names
  • mail.spamassassin.cz
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-10
Not valid after
2024-05-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
18:AE:46:21:2B:E4:2F:AF:7E:2B:A8:22:7B:BC:5F:0F:B1:29:18:3B:0F:42:B4:85:30:96:3F:6E:85:78:49:0A
SHA1
35:03:B0:24:43:30:44:BF:E0:EC:41:B2:44:B7:8C:F5:16:82:21:E1
X509v3 extensions
subjectKeyIdentifier
  • 42:75:EB:33:0C:F3:FC:E5:6D:F7:63:8B:3D:79:70:93:B0:50:97:6F
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Feb 10 03:22:06.030 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6B:3B:B5:6D:C5:54:25:E3:07:47:78:AC:
  • 35:96:AE:60:3A:86:DF:5F:14:0E:DF:A5:9E:FF:3A:38:
  • 1C:F6:47:3F:02:21:00:F6:A6:11:5F:66:E0:A9:C4:5C:
  • FC:09:8D:F8:8D:F2:DC:59:ED:BE:9E:49:D3:80:D7:35:
  • CB:03:23:A9:49:3A:6D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Feb 10 03:22:06.582 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:44:9F:41:66:23:B4:34:0C:2F:E3:CB:44:
  • BE:B9:11:B6:92:6C:64:4C:8F:B4:FF:E2:AB:CD:F9:9B:
  • 51:4C:05:54:02:20:59:82:94:81:6F:CD:E3:24:5D:04:
  • 55:39:3A:F6:D7:BB:5F:8E:30:77:F9:81:03:AD:A1:D2:
  • 5E:8C:6E:2F:6D:24