SSL-Tools

SSL check results of secure.meiranke.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for secure.meiranke.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, 30 Jun 2020 11:12:50 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
secure.meiranke.de
82.165.115.138
 -
supported
secure.meiranke.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s
secure.meiranke.de
2001:8d8:1800:8093::1
 -
supported
secure.meiranke.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=secure.meiranke.de

Certificate chain
Subject
Common Name (CN)
  • secure.meiranke.de
Alternative Names
  • secure.meiranke.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-05-25
Not valid after
2020-08-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
C5:BB:90:07:90:E2:A2:DB:65:6E:94:DC:B2:AE:98:FE:8E:67:4A:F6:4F:6A:42:0F:FC:28:95:3D:88:37:AC:CB
SHA1
F8:37:D2:F4:DC:D6:73:CE:4C:D7:C7:E9:5E:B6:3F:A1:06:35:F5:BB
X509v3 extensions
subjectKeyIdentifier
  • 72:54:DF:5C:79:A5:B7:9E:B4:6D:01:29:E9:C8:F2:89:36:A5:C6:26
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 : F0:95:A4:59:F2:00:D1:82:40:10:2D:2F:93:88:8E:AD:
  • 4B:FE:1D:47:E3:99:E1:D0:34:A6:B0:A8:AA:8E:B2:73
  • Timestamp : May 25 18:14:10.414 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:15:A3:B6:50:C8:ED:D2:8B:27:50:BC:07:
  • 29:0A:D9:A1:A1:76:99:62:9C:FC:05:0B:53:D2:28:4A:
  • 8E:B3:C4:70:02:20:0F:7C:B4:69:E3:E2:C4:C9:FA:98:
  • CD:C3:C2:60:01:E0:6D:28:B3:79:17:BC:4B:22:A3:F2:
  • 13:D5:27:97:A9:5A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 07:B7:5C:1B:E5:7D:68:FF:F1:B0:C6:1D:23:15:C7:BA:
  • E6:57:7C:57:94:B7:6A:EE:BC:61:3A:1A:69:D3:A2:1C
  • Timestamp : May 25 18:14:10.459 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:3A:47:B3:39:DD:4F:5C:88:E0:72:64:39:
  • 0A:9F:84:3F:75:6C:54:AB:95:04:07:E4:68:81:8F:00:
  • 88:D1:D6:85:02:21:00:8E:3A:08:FF:82:38:3A:3F:1E:
  • 36:7D:08:41:30:C0:A8:C7:CF:81:F6:FA:AB:B8:5E:19:
  • D7:52:A8:3F:B3:A3:CA