SSL-Tools

SSL check results of mail.stlueke.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.stlueke.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 Sun, 09 May 2021 09:42:51 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.stlueke.de
93.198.244.185
 10
supported
web.stlueke.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=web.stlueke.de

Certificate chain
  • web.stlueke.de
    • 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)
  • web.stlueke.de
Alternative Names
  • asien01.stlueke.de
  • asien02.stlueke.de
  • australien01.stlueke.de
  • europa01.stlueke.de
  • europa02.stlueke.de
  • mail.stlueke.de
  • matorina.stlueke.de
  • nordamerika.stlueke.de
  • stlueke.de
  • web.stlueke.de
  • www.stlueke.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-04-12
Not valid after
2021-07-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EC:A5:32:14:7E:4E:C6:C5:6F:9A:69:A6:7E:B2:9B:66:08:63:84:F6:14:7C:D0:CE:45:A3:24:EC:3F:63:38:59
SHA1
B4:1C:9D:06:CA:D0:E1:2F:01:21:9F:A0:79:A8:F5:84:E6:BE:B7:29
X509v3 extensions
subjectKeyIdentifier
  • F4:67:88:3B:2E:F1:58:98:1C:5C:38:27:D5:52:7F:56:DE:13:B7:7E
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 : 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 : Apr 12 12:49:09.044 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A2:63:4B:E1:78:B7:2F:29:85:01:17:
  • 1C:52:15:9E:73:C6:76:BD:72:D9:13:8A:17:7E:66:F2:
  • CA:BA:06:8A:76:02:21:00:DE:F6:2D:3C:1D:AE:94:2D:
  • 08:E0:BA:7E:C3:B4:4D:7A:BB:10:06:41:6E:0B:53:7E:
  • BB:D9:54:37:B1:CD:B6:AE
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Apr 12 12:49:09.167 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:80:3D:2B:E2:C8:AA:1F:EA:6D:2C:5B:
  • B8:18:8D:AD:7E:17:5B:6E:C1:E2:4C:87:F0:8E:70:43:
  • 13:05:D6:5D:CA:02:21:00:F3:47:D9:5D:91:04:8A:17:
  • 69:AD:62:2F:53:AF:7B:30:3E:AE:51:AE:30:F6:8D:25:
  • C1:02:CD:59:84:D5:AD:A8