SSL check results of wtzm.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for wtzm.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 Fri, 26 Apr 2024 13:04:20 +0000

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

Servers

Incoming Mails

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

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

Outgoing Mails

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

Certificates

First seen at:

CN=daisy.wtzm.de

Certificate chain
  • daisy.wtzm.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • daisy.wtzm.de
Alternative Names
  • daisy.wtzm.de
  • mail.wtzm.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-26
Not valid after
2024-07-25
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
7C:2A:59:76:03:0A:73:33:02:A0:75:2B:FA:09:57:7D:D7:69:0C:79:B5:3B:74:C4:C8:09:41:8A:0D:7F:25:F3
SHA1
FB:35:1C:F5:99:98:4C:CB:B0:2F:E2:AE:F8:DF:2D:BD:E0:8A:72:88
X509v3 extensions
subjectKeyIdentifier
  • D4:3C:BD:23:9D:A4:8C:88:00:26:56:FC:7F:B1:33:03:0C:9E:FF:A9
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3F:17:4B:4F:D7:22:47:58:94:1D:65:1C:84:BE:0D:12:
  • ED:90:37:7F:1F:85:6A:EB:C1:BF:28:85:EC:F8:64:6E
  • Timestamp : Apr 26 12:58:21.681 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:22:D7:62:6F:40:90:E2:39:A5:9A:02:F3:
  • 46:1B:F4:FC:6F:D8:A0:9A:82:95:51:74:50:FA:D9:AC:
  • 03:9F:15:86:02:20:6C:FD:99:45:ED:D4:65:AA:51:0C:
  • CE:3B:F2:70:CB:2A:02:98:7D:E0:21:B1:D0:46:44:06:
  • 54:F9:52:81:5A:94
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Apr 26 12:58:21.725 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:4F:D7:10:25:FD:74:C8:C7:EF:56:56:DB:
  • EC:CE:B3:32:9E:FC:7A:2C:ED:75:E0:46:07:5D:24:59:
  • C3:C3:1D:BE:02:20:6D:57:45:9B:8A:BC:73:BE:08:4A:
  • 7B:F8:90:6F:FD:EA:F0:7D:30:A6:A0:78:7E:77:DC:65:
  • 66:34:27:83:C6:F1