SSL-Tools

SSL check results of dnmz.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for dnmz.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 Wed, 07 Apr 2021 23:24:58 +0000

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

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

/mailservers/dnmz.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.dnmz.de
2a03:4000:40:59b:3485:85ff:fe85:21f1
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.dnmz.de
5.252.226.26
 10
supported
v2202006121651120303.supersrv.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=v2202006121651120303.supersrv.de

Certificate chain
  • v2202006121651120303.supersrv.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • v2202006121651120303.supersrv.de
Alternative Names
  • v2202006121651120303.supersrv.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-04-06
Not valid after
2021-07-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EA:1A:40:89:CE:52:33:E4:7A:F4:24:BC:D2:F7:A7:3D:8E:09:39:E2:78:84:1C:A0:27:CB:30:6A:D0:5C:7E:E9
SHA1
2A:01:77:95:29:20:70:AF:F7:B3:A5:7B:45:F9:16:C7:04:13:E4:31
X509v3 extensions
subjectKeyIdentifier
  • 7C:5E:B4:CA:7E:4E:20:A2:4A:26:96:C1:3A:E9:69:5F:BC:C5:86:D3
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 : 5C:DC:43:92:FE:E6:AB:45:44:B1:5E:9A:D4:56:E6:10:
  • 37:FB:D5:FA:47:DC:A1:73:94:B2:5E:E6:F6:C7:0E:CA
  • Timestamp : Apr 6 22:02:08.632 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F3:2B:2B:0C:E2:EE:A5:F7:64:9E:27:
  • 40:2B:AB:1E:6A:63:D5:CD:B3:DE:F6:04:A9:22:2C:2E:
  • 5D:1C:6F:6C:CE:02:21:00:F5:55:4A:52:63:76:8B:C8:
  • 11:E2:80:0A:46:52:D0:8A:33:AF:49:2D:12:74:C8:A5:
  • 12:F7:49:79:75:03:D9:61
  • 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 6 22:02:08.675 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:46:4F:63:F1:05:D1:82:DB:B3:83:BD:62:
  • 07:64:5C:FF:28:63:28:AA:D4:4C:48:BD:B0:46:58:8D:
  • 43:95:05:1A:02:20:21:64:5C:E7:71:B6:31:5D:9A:AD:
  • 89:0B:A8:BD:73:21:E8:3B:E6:D9:67:05:ED:B4:41:17:
  • 8F:3E:4E:DC:82:BA