SSL check results of wuensch.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for wuensch.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 Mon, 02 Dec 2024 08:47:42 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.wuensch.de
62.153.63.242
5
supported
mail.wuensch.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
mx01.wuensch.de
62.153.63.242
10
supported
mail.wuensch.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
mforward.dtag.de
194.25.242.123
Results incomplete
20
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.wuensch.de

Certificate chain
  • mail.wuensch.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption

      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • mail.wuensch.de
Alternative Names
  • mail.wuensch.de
  • mx01.wuensch.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-12-02
Not valid after
2025-03-02
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
05:20:C2:F9:80:01:E8:70:CF:8F:A8:B7:59:FF:91:45:FA:68:73:20:EA:D3:2C:A1:F0:9C:8B:1F:74:DC:7F:34
SHA1
6F:19:95:FD:7B:93:25:09:FE:6D:16:87:61:51:8C:22:CD:8B:A7:BE
X509v3 extensions
subjectKeyIdentifier
  • 24:0C:3C:85:97:0C:E3:9D:27:96:07:89:E9:73:22:EE:87:3C:0C:80
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Dec 2 08:37:48.526 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:85:8B:F8:A3:A7:60:C5:5F:55:18:A5:
  • 06:38:16:E2:FE:49:CF:21:79:5F:56:BA:40:73:73:FD:
  • 9F:EB:06:60:BB:02:20:07:49:62:DF:8B:3A:B6:1F:F7:
  • 2A:D8:BE:7C:E0:92:50:82:D8:A6:D8:A7:DD:77:64:EC:
  • 6F:AA:39:DE:F0:E6:1F
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Dec 2 08:37:50.523 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:13:4E:88:59:DA:9B:CB:5E:31:39:EB:FF:
  • 6D:67:48:7F:24:F1:B1:A1:98:37:B7:10:F0:92:B7:27:
  • 95:51:36:F3:02:21:00:DE:2A:20:C2:54:A6:79:FA:2D:
  • 81:22:91:4A:FE:12:C9:89:D2:34:6A:C4:D9:31:AB:EB:
  • D7:88:54:1D:13:F2:A3