SSL-Tools

SSL check results of feuerwehr-reichenbach-ol.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for feuerwehr-reichenbach-ol.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 Sat, 21 Dec 2024 01:30:30 +0000

The mailservers of feuerwehr-reichenbach-ol.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @feuerwehr-reichenbach-ol.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.knabedesign.de
2a01:238:43ff:3d00:3b4b:bdc6:c60d:9914
 10
supported
knabedesign.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.knabedesign.de
85.214.155.149
 10
supported
knabedesign.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

We have not received any emails from a @feuerwehr-reichenbach-ol.de address so far. Test mail delivery

Certificates

First seen at:

CN=knabedesign.de

Certificate chain
  • knabedesign.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • knabedesign.de
Alternative Names
  • *.knabedesign.de
  • knabedesign.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2024-12-06
Not valid after
2025-03-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EF:29:18:4D:A8:E0:67:6F:B5:E4:C3:55:AC:44:B5:3F:47:98:44:01:24:70:C6:FF:5D:46:97:BB:0C:2F:3F:59
SHA1
9D:9C:FD:2E:88:EF:84:C3:82:B1:C2:DB:13:F4:E4:A9:27:36:F4:11
X509v3 extensions
subjectKeyIdentifier
  • 63:BD:59:AB:53:B2:3C:FD:51:8C:6C:94:01:E6:9E:8A:97:BB:76:08
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Dec 6 19:50:35.313 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:70:D1:66:63:C9:4B:CF:79:69:6B:9B:53:
  • 68:57:5C:50:82:27:D3:C8:E5:94:8D:E6:0B:83:E2:49:
  • 7E:4E:D1:EE:02:20:62:5C:D7:84:1F:0B:4A:C4:0A:04:
  • DC:42:6C:D3:1B:25:54:56:28:C4:3A:0F:F0:D5:48:4C:
  • F7:CD:81:C3:38:CB
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Dec 6 19:50:35.340 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:68:E8:3A:94:EB:A3:6D:26:66:55:30:19:
  • D7:D6:CA:87:C8:A8:1E:6A:62:76:3F:13:B0:C1:8E:68:
  • 60:F3:FD:E0:02:21:00:C8:AB:45:C0:97:8E:4A:2F:98:
  • 05:51:30:EB:B5:98:0A:DC:A5:42:79:ED:B2:43:6D:C2:
  • 0F:29:70:38:18:BD:A7