SSL-Tools

SSL check results of engelbrechtsmuenster.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for engelbrechtsmuenster.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, 21 Jun 2020 23:12:35 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.engelbrechtsmuenster.de
2a03:4000:24:764:8c7:cbff:fefa:b43c
 10
supported
engelbrechtsmuenster.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
9 s
mail.engelbrechtsmuenster.de
185.233.106.115
 10
supported
engelbrechtsmuenster.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s

Outgoing Mails

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

Certificates

First seen at:

CN=engelbrechtsmuenster.de

Certificate chain
Subject
Common Name (CN)
  • engelbrechtsmuenster.de
Alternative Names
  • autoconfig.engelbrechtsmuenster.de
  • engelbrechtsmuenster.de
  • home.engelbrechtsmuenster.de
  • imap.engelbrechtsmuenster.de
  • mail.engelbrechtsmuenster.de
  • pop3.engelbrechtsmuenster.de
  • smtp.engelbrechtsmuenster.de
  • srv01.engelbrechtsmuenster.de
  • www.engelbrechtsmuenster.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-06-01
Not valid after
2020-08-30
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D8:28:50:82:66:6C:27:2A:EB:31:0D:BE:ED:D5:60:1D:4B:CD:4E:CA:16:EA:2A:B9:A1:F9:3A:50:E6:CF:A9:2A
SHA1
17:20:25:90:B6:D2:3E:CD:20:79:2E:E0:9C:A0:3E:B3:F2:BD:74:22
X509v3 extensions
subjectKeyIdentifier
  • E7:7F:DD:29:24:04:A5:20:3B:E0:E7:38:9B:64:08:93:86:8D:CD:5A
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.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 : 5E:A7:73:F9:DF:56:C0:E7:B5:36:48:7D:D0:49:E0:32:
  • 7A:91:9A:0C:84:A1:12:12:84:18:75:96:81:71:45:58
  • Timestamp : Jun 1 01:48:54.672 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:8C:EA:71:0A:C0:3A:E1:96:FB:19:D1:
  • EE:61:84:5F:55:EE:A6:4D:A8:6D:7F:E3:6F:8C:4A:F2:
  • E7:C1:1C:20:3E:02:21:00:98:91:63:A3:0F:AD:06:04:
  • 63:0D:FE:BA:54:2E:78:8C:6F:41:31:42:5B:8B:84:5D:
  • E2:F6:F9:EE:3B:71:E3:C5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
  • 25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
  • Timestamp : Jun 1 01:48:54.654 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0F:47:C3:98:89:9B:9A:D9:4E:20:D5:B5:
  • 83:D9:CC:61:CA:6D:3F:2A:2B:B4:9D:73:43:FB:F7:8B:
  • 94:BE:32:26:02:21:00:E2:EB:70:BE:42:43:D8:20:86:
  • 7C:46:21:9B:E9:BB:F3:AC:C0:56:7C:65:81:E6:AD:98:
  • D2:D3:AE:34:23:29:A5