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

Report created Thu, 14 Jan 2021 08:48:31 +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
mailsrvn.loebelch.de
159.69.179.189
10
supported
loebelch.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s

Outgoing Mails

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

Host TLS Version & Cipher
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
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • loebelch.de
Alternative Names
  • *.loebelch.de
  • loebelch.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-01-13
Not valid after
2021-04-13
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
E0:E1:E6:CF:38:64:9A:D6:D1:FB:62:BE:B4:69:6E:70:E9:7B:6B:B1:ED:CF:84:0D:60:0A:48:A0:18:FB:2B:90
SHA1
5A:8D:16:4F:C5:77:4F:A5:45:C7:50:40:93:59:56:AC:FA:34:D6:E3
X509v3 extensions
subjectKeyIdentifier
  • 50:B0:96:90:5E:55:42:81:8B:7A:99:81:47:9F:CB:36:46:D7:4C:99
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
  • 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 : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
  • DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
  • Timestamp : Jan 13 14:46:51.131 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:2D:49:E8:06:EE:04:29:4F:9F:6A:18:F3:
  • C4:E7:CC:92:A1:B2:46:E3:37:7A:FD:43:01:38:15:33:
  • 15:FE:B3:A5:02:20:15:53:74:6F:32:B7:5B:A5:07:E2:
  • BE:CC:D3:94:DE:09:F4:B9:09:C4:BF:F9:10:DF:5A:ED:
  • 08:D5:77:5F:95:3E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
  • 79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
  • Timestamp : Jan 13 14:46:51.188 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:1D:74:98:4E:30:7B:D8:C4:A2:D2:4B:88:
  • D2:63:16:55:AD:FA:05:6B:56:8B:F6:3E:55:B2:B4:02:
  • F6:BC:5A:8C:02:21:00:ED:C8:8D:68:10:09:74:28:FF:
  • D8:D9:DC:AE:71:94:9F:BB:4D:A9:69:7B:10:63:2C:F0:
  • 9F:59:F9:8B:F2:43:B0