SSL-Tools

SSL check results of alternate.de

NEW You can also bulk check multiple servers.

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

JSON Refresh

Report created Tue, 16 Apr 2024 12:49:36 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mailserver01.tle.de
195.234.50.53
 10
supported
mailserver01.tle.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mailserver02.tle.de
195.234.50.54
 10
supported
mailserver02.tle.de
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 @alternate.de address so far. Test mail delivery

Certificates

First seen at:

CN=mailserver01.tle.de

Certificate chain
  • mailserver01.tle.de
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mailserver01.tle.de
Alternative Names
  • mailserver01.tle.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-23
Not valid after
2024-06-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
7E:88:E6:1B:01:63:36:38:F9:4C:40:6C:A1:2F:6D:28:19:9B:28:F9:18:78:BF:BA:95:6F:46:B3:09:81:D9:4E
SHA1
82:89:EF:D5:9A:FD:80:63:99:B1:83:64:1D:16:9F:2A:8B:BB:31:2F
X509v3 extensions
subjectKeyIdentifier
  • E8:33:62:38:8C:F9:56:CF:B4:8F:A7:AE:8A:31:69:0E:00:0D:70:B9
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 : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Mar 23 20:13:36.251 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:23:92:5E:F2:9B:A0:6C:4E:BA:69:DD:45:
  • 7E:76:D5:B4:AB:41:51:D2:16:02:B7:79:E3:1C:E9:6A:
  • F4:24:77:E4:02:20:38:D2:CE:32:D5:56:53:6C:6A:CD:
  • A1:BB:B8:59:67:BD:38:75:30:1F:00:1A:C1:86:60:8B:
  • 9D:20:66:F0:8D:D4
  • 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 : Mar 23 20:13:36.263 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:EB:89:E0:A1:06:C4:70:06:71:4F:CD:
  • EE:3D:AA:38:DA:A8:41:05:EE:E6:65:B8:B9:8F:D5:03:
  • 71:36:07:AD:B0:02:20:01:72:3C:35:A3:DC:C6:6D:A6:
  • 63:94:5C:06:92:17:85:EF:AB:60:F5:62:9F:89:BC:B0:
  • 43:22:7B:F7:2F:6F:3B
First seen at:

CN=mailserver02.tle.de

Certificate chain
  • mailserver02.tle.de
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mailserver02.tle.de
Alternative Names
  • mailserver02.tle.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-13
Not valid after
2024-07-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1A:AF:98:EA:DE:E4:20:13:7B:DC:CC:78:7F:72:71:D3:F8:1E:4C:2E:F9:5B:19:44:3D:C9:5E:B6:60:C7:2F:97
SHA1
C6:EE:02:2E:76:38:E0:26:E3:50:87:A5:A3:5D:4A:F7:6F:0A:5F:A5
X509v3 extensions
subjectKeyIdentifier
  • A5:A8:DF:27:C2:C2:3B:29:7E:E2:A7:0E:C7:9E:7B:71:E7:9B:97:E0
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 : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 14 00:20:47.050 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D0:2C:7A:E4:1A:34:CC:C4:A5:10:2B:
  • E5:C1:22:FB:9B:9D:9D:AF:7B:EF:9D:F8:84:C2:3F:9F:
  • 26:EC:BF:90:6A:02:21:00:F1:A5:9E:58:1F:DC:E5:42:
  • 82:AB:8F:6A:9B:DA:A1:0E:8D:27:A3:1B:42:EF:8B:A4:
  • 02:73:3E:CA:DD:2E:5D:40
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Apr 14 00:20:47.084 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E7:88:10:4E:30:23:1E:C6:6A:C7:AB:
  • FD:85:7F:C2:97:75:2B:B2:A1:C0:0E:1E:D1:F4:8F:9A:
  • AD:0D:CF:F0:82:02:20:2B:6F:36:5B:B4:C6:2C:89:5C:
  • D1:27:79:2D:BF:3B:43:75:FD:31:04:DF:59:19:A2:FB:
  • 30:B3:EF:45:6D:2D:D0