SSL check results of msm-poststelle.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for msm-poststelle.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 Tue, 04 May 2021 14:05:26 +0000

We can not guarantee a secure connection to the mailservers of msm-poststelle.de!

Please contact the operator of msm-poststelle.de and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/msm-poststelle.de

Servers

Incoming Mails

These servers are responsible for incoming mails to @msm-poststelle.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.msm-poststelle.de
2001:1640:175:8100:6e78:7463:abcd:ef12
Results incomplete
10
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.msm-poststelle.de
85.220.255.222
10
supported
mail.msm-poststelle.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
15 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.msm-poststelle.de

Certificate chain
  • mail.msm-poststelle.de
    • remaining
    • 384 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • mail.msm-poststelle.de
Alternative Names
  • mail.msm-poststelle.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-19
Not valid after
2021-05-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C6:03:BC:02:06:C7:00:C1:F8:6C:07:D6:16:E8:24:FA:90:40:87:A0:9F:19:E2:7A:6D:27:2F:09:6C:2F:CF:3D
SHA1
4B:97:BC:A6:98:05:43:F3:CD:D3:0D:81:C4:73:EF:DB:40:D2:B4:56
X509v3 extensions
subjectKeyIdentifier
  • 97:6B:A6:5D:20:B3:EF:A1:E2:4A:BC:AF:D1:D3:0C:44:8C:2F:AC:9D
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 : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
  • DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
  • Timestamp : Feb 19 18:16:56.131 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:3D:30:C5:E4:0F:7C:45:16:A2:78:D3:7E:
  • 53:04:AA:34:FA:87:2E:D2:5F:6A:33:C4:C5:92:69:E9:
  • FE:E6:17:BF:02:20:51:AC:3E:51:29:FE:75:B3:D1:9E:
  • 8E:CD:D3:3E:75:D3:58:36:03:B7:48:0D:A0:BA:DA:C4:
  • 42:63:93:3F:74:91
  • 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 : Feb 19 18:16:56.163 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:21:99:30:A0:EE:FB:80:C5:56:2B:C9:64:
  • BB:89:1C:CE:36:28:90:CB:E7:BE:40:EC:6D:2B:98:4C:
  • BA:5C:AC:D9:02:20:6C:9B:C2:73:A5:16:1F:1B:B7:0D:
  • 4D:D1:26:75:E8:CD:D4:2A:4C:18:3D:60:CE:8C:41:C3:
  • 7D:9A:99:81:4E:C6