SSL-Tools

SSL check results of meido.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for meido.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 Tue, 24 Nov 2020 01:48:48 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.meido.de
2a01:4f8:c0c:302d::2
 10
supported
meido.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
9 s
mail.meido.de
94.130.99.224
 10
supported
meido.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s

Outgoing Mails

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

Certificates

First seen at:

CN=meido.de

Certificate chain
  • meido.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
Subject
Common Name (CN)
  • meido.de
Alternative Names
  • imap.meido.de
  • mail.meido.de
  • meido.de
  • office.meido.de
  • owncloud.meido.de
  • smtp.meido.de
  • ticket.meido.de
  • www.meido.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-10-22
Not valid after
2021-01-20
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
85:E2:C6:72:6D:E4:4E:01:3C:CE:AA:43:57:C7:96:C5:58:E5:2C:B7:9B:0D:85:F0:E5:9D:23:FB:31:4F:9F:8A
SHA1
2E:B9:D0:BC:0B:B7:49:19:38:FB:75:E2:E3:8D:98:91:07:86:14:15
X509v3 extensions
subjectKeyIdentifier
  • 21:9D:FB:02:2D:0C:0B:66:1F:96:03:9A:89:51:37:A1:F7:A5:45:11
authorityKeyIdentifier
  • keyid:A8:4A:6A:63:04:7D:DD:BA:E6:D1:39:B7:A6:45:65:EF:F3:A8:EC:A1
authorityInfoAccess
  • OCSP - URI:http://ocsp.int-x3.letsencrypt.org
  • CA Issuers - URI:http://cert.int-x3.letsencrypt.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : Oct 22 12:21:58.020 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0F:05:04:51:DB:AE:93:E9:8F:21:27:36:
  • F1:3C:4A:74:23:AC:4B:D6:AA:13:D4:B5:24:21:33:B3:
  • 78:C0:93:0B:02:21:00:BE:33:C0:03:81:BF:AA:4A:48:
  • F8:16:7D:9E:F6:04:AC:8B:10:D3:20:D5:EF:29:89:AC:
  • 4D:5F:50:89:1F:E5:D1
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Oct 22 12:21:58.083 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2A:03:15:1B:F6:5D:71:1F:50:9D:5B:AE:
  • E9:5B:A7:5A:65:A6:23:28:E7:72:35:04:8E:EE:3C:11:
  • 4B:5C:20:AE:02:21:00:90:7B:E3:AF:0C:65:20:24:40:
  • 56:9C:7E:C8:D8:BD:44:A0:20:8A:11:B5:80:42:16:BA:
  • 7D:BC:12:CB:34:80:E4