SSL-Tools

SSL check results of feuerwehr-krobnitz-meuselwitz.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for feuerwehr-krobnitz-meuselwitz.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 Sun, 07 Jun 2026 00:30:52 +0000

The mailservers of feuerwehr-krobnitz-meuselwitz.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @feuerwehr-krobnitz-meuselwitz.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
1 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-krobnitz-meuselwitz.de address so far. Test mail delivery

Certificates

First seen at:

CN=knabedesign.de

Certificate chain
  • knabedesign.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R13
        • 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)
  • R13
validity period
Not valid before
2026-04-16
Not valid after
2026-07-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
Fingerprints
SHA256
2F:0B:62:EE:D0:3B:AC:3C:E3:01:52:7E:4F:06:EF:C0:08:2B:7A:91:82:DA:41:DA:25:40:D2:50:E3:44:C4:C6
SHA1
2E:D3:00:D8:64:10:98:C8:F7:15:4C:2E:04:89:27:32:4D:66:16:91
X509v3 extensions
subjectKeyIdentifier
  • 0F:6B:13:63:5E:15:EE:79:4A:0E:5A:42:8B:8C:D6:2F:79:31:13:5D
authorityKeyIdentifier
  • keyid:E7:AB:9F:0F:2C:33:A0:53:D3:5E:4F:78:C8:B2:84:0E:3B:D6:92:33
authorityInfoAccess
  • CA Issuers - URI:http://r13.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r13.c.lencr.org/68.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : D7:6D:7D:10:D1:A7:F5:77:C2:C7:E9:5F:D7:00:BF:F9:
  • 82:C9:33:5A:65:E1:D0:B3:01:73:17:C0:C8:C5:69:77
  • Timestamp : Apr 16 15:13:47.230 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:E2:20:8E:6D:69:A3:B3:B2:56:A7:74:
  • 9A:E7:3A:CC:01:18:F2:88:55:A2:21:5A:31:65:CB:CC:
  • D7:4E:14:82:2A:02:20:2B:90:91:22:8D:66:A3:1F:67:
  • 81:3F:3A:A8:2C:0F:F8:87:24:E7:69:8F:08:F2:D0:3E:
  • 97:78:99:3F:97:3D:D3
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 46:AF:86:3D:3B:3E:E5:9F:A5:77:DE:A8:24:5D:36:B0:
  • D9:ED:22:A2:23:F4:61:77:41:22:94:52:EE:95:50:5F
  • Timestamp : Apr 16 15:13:47.329 2026 GMT
  • Extensions: 00:00:05:00:04:0B:38:92
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:A9:99:B0:7C:E5:AB:42:AE:D5:B1:28:
  • 71:22:02:12:15:72:30:2E:E3:3A:D8:1F:42:08:7E:1E:
  • 65:75:B4:7F:F6:02:20:1C:3B:AE:EB:DC:6C:CF:65:94:
  • 23:CB:13:61:1B:B7:30:0E:DD:99:CD:58:59:4E:D0:DA:
  • E9:6B:ED:FA:E1:81:22