SSL check results of trainchain.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for trainchain.de 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, 20 Jan 2025 13:39:11 +0000

The mailservers of trainchain.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @trainchain.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.hendelzon.com
2a01:4f8:2190:1b0d::2
10
supported
mail.hendelzon.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.hendelzon.com
49.12.174.210
10
supported
mail.hendelzon.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.hendelzon.com

Certificate chain
  • mail.hendelzon.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • mail.hendelzon.com
Alternative Names
  • mail.hendelzon.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-01-17
Not valid after
2025-04-17
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
CB:44:19:FC:A6:58:09:5B:99:C5:31:67:72:68:EE:3D:9E:67:39:A2:B3:47:A8:7F:4D:AF:DD:CD:BF:10:E9:53
SHA1
DA:A4:06:E3:48:C8:B8:76:9C:7B:E4:37:EC:54:F9:54:77:8D:47:0D
X509v3 extensions
subjectKeyIdentifier
  • 7A:02:FE:B3:21:CB:F2:04:EF:1A:E9:4D:58:A3:F6:9B:4A:28:13:21
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Jan 17 01:46:55.042 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:1E:E7:9F:8F:36:C8:D5:18:7B:8C:61:3D:
  • 44:A9:C1:23:26:2C:EB:B4:45:5E:B0:DB:6C:F8:5C:F6:
  • C6:C8:97:0A:02:20:31:23:E8:C2:A7:55:C7:D8:AF:74:
  • 57:55:CA:78:75:6A:F2:91:F1:D7:94:F0:A9:75:52:16:
  • 7E:27:AD:FD:EA:9B
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 4E:75:A3:27:5C:9A:10:C3:38:5B:6C:D4:DF:3F:52:EB:
  • 1D:F0:E0:8E:1B:8D:69:C0:B1:FA:64:B1:62:9A:39:DF
  • Timestamp : Jan 17 01:46:55.039 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C0:14:96:94:78:F9:AF:BE:4A:31:B4:
  • 45:05:4D:C1:25:61:DC:07:EC:87:B2:67:76:FB:28:23:
  • 2F:96:AA:8B:2E:02:21:00:E2:EB:5A:AE:E6:78:7E:CA:
  • B1:AC:5D:4C:F6:3F:AD:20:77:F0:78:BA:65:58:C5:9A:
  • D4:93:75:06:72:F3:82:45