SSL check results of mchw.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mchw.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 Sun, 25 May 2025 15:29:54 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mchw.de
2a0a:4cc0:c0:28c0::1
10
supported
mchw.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mchw.de
152.53.84.104
10
supported
mchw.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

We have received emails from these servers with @mchw.de sender addresses. Test mail delivery

Host TLS Version & Cipher
mchw.de (37.221.197.214)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384

Certificates

First seen at:

CN=mchw.de

Certificate chain
  • mchw.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384

      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • mchw.de
Alternative Names
  • *.mchw.de
  • mchw.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2025-05-23
Not valid after
2025-08-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
59:34:92:73:6B:C1:5E:28:01:39:6C:24:C5:5A:AC:82:38:84:7E:76:E5:9A:EB:99:56:98:31:AA:F7:A9:E8:12
SHA1
3A:71:97:47:DE:7D:37:B7:ED:77:32:A7:2F:28:26:C9:CC:6A:88:08
X509v3 extensions
subjectKeyIdentifier
  • C7:C2:AF:46:25:D6:C3:BD:3E:CA:89:BF:7E:D7:3C:77:09:66:A7:88
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e5.c.lencr.org/61.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : May 23 23:08:13.674 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DF:49:7B:24:B8:A2:01:D3:FE:0C:F5:
  • 58:BB:DA:EF:7D:5E:FC:C1:A8:97:2B:AF:71:70:B4:FB:
  • 58:AF:7A:15:C5:02:20:2A:DE:ED:46:49:43:05:11:A3:
  • CF:B6:E4:C3:99:53:B3:93:BF:D5:B6:FB:B8:FC:AF:85:
  • C8:37:90:D3:F9:78:26
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : May 23 23:08:15.704 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A4:57:E3:53:AB:C3:33:18:AA:C4:F1:
  • 51:6F:B9:6F:16:3B:58:58:78:13:9A:70:6B:DB:1E:EE:
  • 2C:72:E8:8A:91:02:21:00:98:13:DA:CC:6E:2E:73:51:
  • B7:40:DC:D0:05:05:44:18:D2:30:76:10:1A:35:2D:25:
  • 18:3B:73:5E:43:C0:50:82

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mchw.de
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid