SSL-Tools

SSL check results of loebelch.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for loebelch.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 Fri, 22 May 2026 19:03:03 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mailsrv.loebelch.de
2a01:4f8:c17:74d4::1
 10
supported
loebelch.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
mailsrv.loebelch.de
49.12.3.38
 10
supported
loebelch.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Host TLS Version & Cipher
srv-hz2.loebelch.de (IPv6:2a01:4f8:c010:1804::1)
TLSv1.3 TLS_AES_256_GCM_SHA384
srv-hz2.loebelch.de (168.119.187.212)
TLSv1.3 TLS_AES_256_GCM_SHA384
srv-hz1.loebelch.de (159.69.179.189)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=loebelch.de

Certificate chain
  • loebelch.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E8
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • loebelch.de
Alternative Names
  • *.loebelch.de
  • loebelch.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E8
validity period
Not valid before
2026-05-09
Not valid after
2026-08-07
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
98:C8:CC:62:6C:67:36:7E:30:46:A0:6B:07:27:03:09:94:57:A6:F8:CC:51:14:00:53:1D:A7:6F:AD:2A:04:4C
SHA1
7E:7F:9B:F5:A0:46:0F:B7:A5:4D:B7:77:61:E3:80:2E:4C:64:F1:61
X509v3 extensions
subjectKeyIdentifier
  • 03:86:1E:A5:B9:E2:87:B8:43:E2:D7:0D:DE:34:4F:A3:44:B7:AB:F9
authorityKeyIdentifier
  • keyid:8F:0D:13:A2:F6:2E:7E:D1:50:6C:33:18:38:5D:59:8E:23:72:91:CA
authorityInfoAccess
  • CA Issuers - URI:http://e8.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e8.c.lencr.org/66.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : C2:31:7E:57:45:19:A3:45:EE:7F:38:DE:B2:90:41:EB:
  • C7:C2:21:5A:22:BF:7F:D5:B5:AD:76:9A:D9:0E:52:CD
  • Timestamp : May 9 08:02:50.156 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F9:4D:B7:D8:1F:AC:3F:0D:29:21:79:
  • 98:66:7B:9B:6D:F3:A8:80:3F:B3:33:EC:19:9E:CE:89:
  • D6:21:33:23:CD:02:21:00:C4:3D:EB:3E:7C:A9:98:A4:
  • 4B:0A:C0:23:B6:A8:0C:46:9B:C8:03:94:0B:52:02:28:
  • 41:1C:1C:44:C6:FD:E6:2C
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6C:FE:50:19:43:A8:5E:A9:16:BC:52:D1:33:E4:DC:C9:
  • 1E:F1:41:1C:7D:25:84:20:D1:73:80:9E:18:18:EB:3A
  • Timestamp : May 9 08:02:51.150 2026 GMT
  • Extensions: 00:00:05:00:0A:AE:81:3E
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:FF:4D:95:02:1F:2D:53:D4:11:D5:53:
  • 6F:64:5E:79:2C:72:29:36:62:0D:53:09:1D:41:20:F6:
  • 3B:04:E4:17:4C:02:21:00:C3:1A:3E:C9:90:8D:3F:C7:
  • 9C:4D:3A:71:BB:BD:01:99:38:00:99:0E:0E:17:D6:DE:
  • B8:44:C5:E3:74:4C:2C:AA