SSL-Tools

SSL check results of multitype.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for multitype.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 Fri, 04 Oct 2024 00:30:22 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.multitype.de
2a02:c202:3014:4070::1
 10
supported
mail.multitype.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
9 s
mail.multitype.de
198.7.126.12
 10
supported
mail.multitype.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.multitype.de

Certificate chain
  • mail.multitype.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.multitype.de
Alternative Names
  • autoconfig.multitype.de
  • autodiscover.multitype.de
  • mail.multitype.de
  • webmail.multitype.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-09-15
Not valid after
2024-12-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
DC:22:60:63:70:9C:D2:24:20:44:70:F4:2D:F8:CC:9E:3F:E0:DF:8E:EA:E4:29:96:62:DF:F2:97:B4:A1:36:2E
SHA1
D1:D4:91:68:6C:CF:F0:8F:1B:41:C5:A3:2F:5A:75:B7:59:F3:BD:4B
X509v3 extensions
subjectKeyIdentifier
  • D6:CD:C5:E3:AB:2B:DC:34:73:5C:9A:97:98:4F:A1:26:1A:CB:82:24
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Sep 15 12:53:52.464 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:68:53:F4:BA:0F:9D:04:23:1C:C3:88:9C:
  • 9B:81:4B:BA:0A:63:C5:45:8E:15:7F:9E:9D:D7:05:64:
  • A7:5B:E5:60:02:21:00:D0:93:BA:71:AD:5F:84:CF:7C:
  • 20:F4:E7:E2:A5:80:A7:3D:66:6E:E7:30:6E:4B:8B:3D:
  • 58:C0:CA:17:B8:28:41
  • 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 : Sep 15 12:53:52.486 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F9:36:89:F4:97:3E:15:F7:B5:E8:7A:
  • A4:81:C8:0B:D4:1E:5C:0C:A9:A6:E2:71:31:4E:91:B9:
  • 6C:63:EE:A9:EB:02:21:00:9D:8C:D8:83:3E:41:00:BD:
  • 5F:88:E5:E2:FA:33:5A:9A:85:A1:15:B2:80:AD:01:EC:
  • 4E:59:4E:99:44:57:28:D2