SSL-Tools

SSL check results of rinklin-naturkost.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for rinklin-naturkost.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, 16 Apr 2024 14:06:50 +0000

The mailservers of rinklin-naturkost.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @rinklin-naturkost.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.rinklin-naturkost.de
159.69.30.58
 10
supported
mail.rinklin-naturkost.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
6 s

Outgoing Mails

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

Host TLS Version & Cipher
mail.rinklin-naturkost.de (159.69.30.58)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=mail.rinklin-naturkost.de

Certificate chain
  • mail.rinklin-naturkost.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.rinklin-naturkost.de
Alternative Names
  • mail.rinklin-naturkost.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-12
Not valid after
2024-07-11
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
47:85:2A:FE:E1:0D:7C:99:58:13:70:A4:FC:66:69:38:63:D1:B1:80:1F:BB:47:8B:A7:49:44:C6:41:66:F4:24
SHA1
1E:D2:7A:1A:B6:25:51:21:48:25:43:35:5A:A1:CF:AC:E9:DE:6A:38
X509v3 extensions
subjectKeyIdentifier
  • F1:E7:80:05:D9:76:91:7B:88:A0:2C:12:55:41:0B:F9:42:1E:74:45
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Apr 12 22:16:50.457 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FD:37:C1:72:63:F8:DF:21:58:E4:1D:
  • 2D:86:9B:00:67:07:E3:A5:25:AF:61:57:D9:98:83:3F:
  • 0F:66:63:4C:D6:02:20:6D:71:C0:B8:E7:19:EF:5D:CF:
  • 5B:98:1E:A7:CC:2F:6C:50:5D:35:88:F4:11:74:C7:B4:
  • B8:BB:CE:7C:1C:B6:92
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Apr 12 22:16:50.482 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:34:94:DF:90:E3:FD:FC:5D:F9:EE:79:E9:
  • 88:51:F5:18:3A:2F:83:73:02:6F:1F:29:E6:E5:40:D7:
  • F3:06:BB:45:02:21:00:91:24:92:F0:20:0E:7E:56:77:
  • 29:5A:B8:30:C6:16:CA:15:1D:4D:B8:0F:9C:A2:06:36:
  • A2:20:26:D8:46:46:B3