SSL-Tools

SSL check results of mout.ruhnke.cloud

NEW You can also bulk check multiple servers.

Discover if the mail servers for mout.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:41 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mout.ruhnke.cloud
212.58.76.58
 -
supported
mout.ruhnke.cloud
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
mout.ruhnke.cloud
2a02:790:ff:920:a91b:825f:6f3:866c
 -
supported
mout.ruhnke.cloud
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s

Outgoing Mails

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

Certificates

First seen at:

CN=mout.ruhnke.cloud

Certificate chain
Subject
Common Name (CN)
  • mout.ruhnke.cloud
Alternative Names
  • mout.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-30
Not valid after
2020-08-28
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F6:E9:E5:F6:D6:3F:EE:E0:0C:44:57:5A:5E:71:54:7C:26:47:7B:57:79:AA:B0:21:E4:C6:B1:DB:75:98:19:DC
SHA1
53:31:AE:3F:47:82:0A:A4:E9:7E:81:39:C2:D8:B3:22:F9:6B:0D:3A
X509v3 extensions
subjectKeyIdentifier
  • 8A:10:2E:51:1A:26:18:F1:72:E4:53:B8:6C:A8:CA:9B:5C:BC:08:7A
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 30 11:31:44.627 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:D3:F6:25:06:51:1E:C1:C1:F5:EE:21:
  • D3:EC:84:26:AA:3A:B2:8B:6A:F3:8D:3E:2D:93:65:8F:
  • 2A:D8:3F:69:34:02:21:00:C5:8E:84:1A:91:C2:E5:2F:
  • 52:EF:9E:6D:A5:22:81:70:AA:7B:C3:80:93:7E:E1:66:
  • D5:47:FA:9E:90:CB:25:C4
  • 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 30 11:31:44.664 2020 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:58:26:02:E1:B7:F4:2A:7E:D2:95:19:E0:
  • 08:A3:58:12:58:DA:F8:EF:27:6B:B0:2A:BA:7A:2B:04:
  • 2E:EA:DB:8F:02:20:0D:20:AA:66:22:8D:3D:C8:AF:7B:
  • B2:EE:A9:87:53:81:24:F4:0C:99:45:DC:4C:46:77:EE:
  • D9:7A:01:0E:7C:F3

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