SSL-Tools

SSL check results of ladoi.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for ladoi.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, 23 Apr 2024 21:37:19 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
merkur.christoph.cx
2a02:c206:3013:6194::1
 10
supported
merkur.christoph.cx
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
merkur.christoph.cx
84.247.138.234
 10
supported
merkur.christoph.cx
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s

Outgoing Mails

We have not received any emails from a @ladoi.de address so far. Test mail delivery

Certificates

First seen at:

CN=merkur.christoph.cx

Certificate chain
  • merkur.christoph.cx
    • remaining
    • 256 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • merkur.christoph.cx
Alternative Names
  • merkur.christoph.cx
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-19
Not valid after
2024-07-18
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
18:31:5F:08:03:D4:AB:5E:82:75:79:53:B0:B5:B7:07:30:1C:3A:B3:C6:99:B3:83:75:FF:A5:45:6A:A8:B9:49
SHA1
4B:DF:72:EF:87:9F:03:FC:D5:64:3D:9A:47:45:1F:D9:8A:B4:E9:B3
X509v3 extensions
subjectKeyIdentifier
  • 76:CF:A2:27:DA:EA:2D:67:49:47:13:7E:F3:8C:39:B1:96:80:5F:78
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 : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 19 19:49:10.581 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F2:B1:C2:BE:29:37:A1:8B:42:3A:59:
  • A6:17:28:79:5B:7A:4C:B9:53:D7:CB:5A:8F:C7:E0:42:
  • 1B:81:C6:20:D8:02:20:0E:E1:2F:71:18:F4:6E:8A:89:
  • AB:7C:12:06:DF:E5:31:F7:08:1C:13:02:04:69:FC:08:
  • 32:CD:A4:BC:B2:A6:5C
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Apr 19 19:49:10.593 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:62:1D:88:27:7D:FB:57:F0:42:2A:55:6C:
  • 07:78:D6:07:00:2C:C9:83:53:EA:6F:73:E3:9C:3C:DC:
  • 81:DB:AE:7C:02:21:00:80:24:DB:47:A3:32:DD:E2:B9:
  • A3:D4:A0:83:88:CC:60:58:D6:4E:29:CD:73:43:8A:D6:
  • F5:D1:3E:68:91:CE:22