SSL-Tools

SSL check results of mail.mstdev.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.mstdev.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 Mon, 21 Oct 2024 00:31:22 +0000

We can not guarantee a secure connection to the mailservers of mail.mstdev.de!

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

/mailservers/mail.mstdev.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.mstdev.de
157.90.237.159
 -
supported
mail.mstdev.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.mstdev.de
2a01:4f8:c0c:7c4c::1
Results incomplete
-
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.mstdev.de

Certificate chain
  • mail.mstdev.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.mstdev.de
Alternative Names
  • mail.mstdev.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-10-15
Not valid after
2025-01-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
45:F1:3B:59:91:72:93:59:C8:CE:2C:20:42:24:BF:C6:5E:EE:3F:72:2E:13:20:3E:BF:14:B6:4A:FF:02:56:2A
SHA1
F9:5A:7F:F4:63:D4:5F:7B:FE:A9:92:9A:D2:F3:E7:D5:43:A2:22:ED
X509v3 extensions
subjectKeyIdentifier
  • 75:51:70:4A:B9:46:65:2C:56:70:2C:E4:DD:25:AB:9D:D4:C2:D7:37
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 : CF:11:56:EE:D5:2E:7C:AF:F3:87:5B:D9:69:2E:9B:E9:
  • 1A:71:67:4A:B0:17:EC:AC:01:D2:5B:77:CE:CC:3B:08
  • Timestamp : Oct 15 08:11:44.719 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:EB:35:10:6F:A9:EC:30:4A:10:02:B1:
  • D6:6F:A8:3F:D9:5A:55:E7:A1:DF:2D:2C:EE:9F:57:AB:
  • A0:FA:1D:7A:70:02:21:00:FC:00:D5:01:C6:A8:48:45:
  • A2:B0:B4:6C:5C:5D:E3:B6:CE:EA:49:8C:1D:05:46:D0:
  • BB:AB:09:DA:40:FC:8D:D5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 13:4A:DF:1A:B5:98:42:09:78:0C:6F:EF:4C:7A:91:A4:
  • 16:B7:23:49:CE:58:57:6A:DF:AE:DA:A7:C2:AB:E0:22
  • Timestamp : Oct 15 08:11:44.824 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FD:81:70:EE:67:DB:40:DE:C3:E8:86:
  • 3E:FF:B5:6E:85:31:FC:87:07:F1:2D:89:30:32:76:F5:
  • 8A:0A:F3:FA:E6:02:20:75:4F:34:A3:E7:0B:B6:CF:1E:
  • 30:D3:30:10:3D:4D:85:1D:C8:BD:05:83:B2:09:FF:59:
  • 8C:14:8E:C6:08:14:5B