SSL check results of rickyy.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for rickyy.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

Report created Fri, 08 Nov 2019 21:48:49 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.rickyy.de
2a03:4000:6:336::1
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.rickyy.de
5.45.102.214
10
supported
mail.rico-j.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

We have received emails from these servers with @rickyy.de sender addresses. Test mail delivery

Host TLS Version & Cipher
rico-j.de (5.45.102.214)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=mail.rico-j.de

Certificate chain
Subject
Common Name (CN)
  • mail.rico-j.de
Alternative Names
  • imap.rickyy.de
  • imap.rico-j.de
  • mail.rickyy.de
  • mail.rico-j.de
  • smtp.rickyy.de
  • smtp.rico-j.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • Let's Encrypt Authority X3
validity period
Not valid before
2019-11-08
Not valid after
2020-02-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
90:90:41:CA:18:3F:00:F6:FA:D5:03:12:C5:34:83:76:40:BE:22:EA:E3:3A:1A:59:12:2A:46:4D:DB:D0:F8:DD
SHA1
43:87:09:7B:41:FA:A2:FE:7C:FE:46:57:E6:9C:18:94:F7:23:8F:7D
X509v3 extensions
subjectKeyIdentifier
  • 24:51:CD:BD:8E:F9:D1:91:8A:5F:84:2A:57:12:E0:70:B6:96:68:10
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 : Nov 8 20:14:43.912 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E9:2B:BC:E8:77:AA:82:0C:65:4E:C5:
  • 28:6D:90:95:C1:16:11:3D:24:6B:B8:49:95:9F:CA:A9:
  • 3A:8A:D9:5E:E5:02:21:00:9C:DC:0E:E0:E0:67:37:CF:
  • 71:2E:76:85:3E:84:54:AD:19:52:3F:4F:71:D1:8C:D8:
  • 6B:0C:E8:72:96:26:81:83
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B2:1E:05:CC:8B:A2:CD:8A:20:4E:87:66:F9:2B:B9:8A:
  • 25:20:67:6B:DA:FA:70:E7:B2:49:53:2D:EF:8B:90:5E
  • Timestamp : Nov 8 20:14:43.900 2019 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:0A:58:7F:E3:C2:E5:76:BF:4E:AA:18:38:
  • 18:5C:13:50:93:C3:05:FF:E7:47:92:EF:60:9D:93:02:
  • 38:D3:0D:4B:02:21:00:DB:AE:4D:FD:A4:69:FF:AA:36:
  • A9:EC:CC:67:EA:E5:48:BE:8A:5B:BE:50:68:E9:7D:73:
  • 5E:83:D5:F7:EB:BB:94