SSL-Tools

SSL check results of imap.ruhnke.cloud

NEW You can also bulk check multiple servers.

Discover if the mail servers for imap.ruhnke.cloud 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 Thu, 09 Jul 2020 15:04:39 +0000

The mailservers of imap.ruhnke.cloud can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @imap.ruhnke.cloud addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
imap.ruhnke.cloud
77.20.0.210
 -
supported
mail.ruhnke.cloud
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
imap.ruhnke.cloud
2a02:8108:9080:1b8c:9556:48e6:65b9:a25a
 -
supported
mail.ruhnke.cloud
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s

Outgoing Mails

We have not received any emails from a @imap.ruhnke.cloud address so far. Test mail delivery

Certificates

First seen at:

CN=mail.ruhnke.cloud

Certificate chain
Subject
Common Name (CN)
  • mail.ruhnke.cloud
Alternative Names
  • imap.ruhnke.cloud
  • mail.ruhnke.cloud
  • smtp.ruhnke.cloud
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2020-05-03
Not valid after
2020-08-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
83:07:7F:E9:32:F5:13:D6:05:0F:4F:C3:4B:42:D1:FE:82:E9:F8:CB:65:BF:D1:85:6B:67:3F:4D:04:AC:97:4D
SHA1
64:C2:EF:BE:04:11:24:24:ED:4F:61:C2:D6:0E:47:79:59:DE:3B:21
X509v3 extensions
subjectKeyIdentifier
  • D0:F0:7A:85:14:79:AA:93:BA:B1:F8:CF:34:B2:07:AE:A6:8C:02:A5
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 : 5E:A7:73:F9:DF:56:C0:E7:B5:36:48:7D:D0:49:E0:32:
  • 7A:91:9A:0C:84:A1:12:12:84:18:75:96:81:71:45:58
  • Timestamp : May 3 03:12:28.913 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:27:42:B7:EB:B2:2A:D5:22:5F:F8:5D:AD:
  • E2:C0:4F:B4:CD:A1:3E:D6:E1:11:66:2B:E3:13:80:4B:
  • 6D:29:DF:D3:02:20:27:9E:50:0A:76:2C:04:18:05:26:
  • 4C:14:ED:75:18:9D:B5:C6:25:AA:7C:D9:17:68:A0:78:
  • 0A:C0:A8:53:E3:47
  • 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 3 03:12:28.952 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7B:F6:8D:B2:8A:92:52:1B:41:64:18:6F:
  • ED:BB:93:6F:C6:92:DF:4A:11:07:92:CD:33:C7:A5:A3:
  • 92:7C:61:28:02:21:00:EF:D2:6A:F7:5B:5F:0C:43:7F:
  • 4E:AB:C0:47:87:91:A3:93:69:3A:DC:31:4C:E7:6E:CE:
  • 18:2F:9C:CF:49:A5:F9

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.imap.ruhnke.cloud
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid