SSL-Tools

SSL check results of mail.mainzer-design.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.mainzer-design.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, 15 May 2024 13:14:28 +0000

The mailservers of mail.mainzer-design.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.mainzer-design.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.mainzer-design.de
148.251.69.29
 -
supported
mail.mainzer-design.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
4 s
mail.mainzer-design.de
2a01:4f8:202:3302::2
 -
supported
mail.mainzer-design.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
6 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.mainzer-design.de

Certificate chain
  • mail.mainzer-design.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.mainzer-design.de
Alternative Names
  • autoconfig.mainzer-design.de
  • autodiscover.mainzer-design.de
  • imap.mainzer-design.de
  • mail.mainzer-design.de
  • smtp.mainzer-design.de
  • time.wieneu.gmbh
  • webtest.mainzer-design.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-05-07
Not valid after
2024-08-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
9E:4A:D0:36:FB:83:33:41:7B:1F:50:70:E4:85:4D:C5:0A:A0:68:CE:3B:8A:DF:7A:A0:4B:40:0D:05:03:83:83
SHA1
F3:0E:64:48:9A:42:D4:C2:EE:F9:E9:B6:4E:58:60:8B:36:1E:10:D1
X509v3 extensions
subjectKeyIdentifier
  • D7:25:76:BD:BB:E1:A7:7E:6D:C6:2E:A0:6D:6D:62:13:A7:E6:50:0B
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 : 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 : May 7 15:47:46.740 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5B:3D:E3:6B:1F:5E:D5:6C:95:FC:45:49:
  • 95:C5:15:EA:E7:6C:C9:32:6E:C4:26:1E:40:00:F6:7D:
  • E0:AD:A9:B2:02:20:77:36:1D:DA:F4:62:A5:DB:16:A5:
  • 40:89:11:30:10:2D:8A:50:5B:B2:42:D4:7D:75:97:C8:
  • 18:BC:F9:96:03:29
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DF:E1:56:EB:AA:05:AF:B5:9C:0F:86:71:8D:A8:C0:32:
  • 4E:AE:56:D9:6E:A7:F5:A5:6A:01:D1:C1:3B:BE:52:5C
  • Timestamp : May 7 15:47:46.953 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F2:F7:F5:DC:B3:6B:5A:99:9B:1E:AF:
  • A6:4C:65:DA:C0:20:DB:E9:21:B7:70:3B:D9:B5:2C:2C:
  • C7:37:A2:DF:53:02:20:53:76:B4:16:09:A2:45:8B:EF:
  • 82:B0:B0:44:A0:DD:E1:76:ED:3A:B0:69:1E:95:18:33:
  • 64:DE:BF:45:4A:55:77