SSL-Tools

SSL check results of conthermo.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for conthermo.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, 09 Aug 2026 00:30:29 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.conthermo.de
217.91.36.104
 10
supported
mail.conthermo.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
itbs1.it-schlabach.de
213.178.10.66
Results incomplete
20
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.conthermo.de

Certificate chain
  • mail.conthermo.de
    • remaining
    • 384 bit
    • ecdsa-with-SHA384
      • YE2
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • mail.conthermo.de
Alternative Names
  • mail.conthermo.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE2
validity period
Not valid before
2026-08-05
Not valid after
2026-11-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
50:2C:DB:25:0F:86:83:92:7E:4A:D0:FE:48:BB:AE:65:25:4A:9C:83:34:0F:93:15:E0:F0:AB:8E:07:78:C0:98
SHA1
00:27:63:95:DD:0D:7F:FC:4C:71:90:5A:17:B0:EC:79:F2:6C:D6:D9
X509v3 extensions
subjectKeyIdentifier
  • 42:87:A3:FE:FA:5D:21:18:DD:CD:C1:11:6C:C0:FA:28:91:F2:67:33
authorityKeyIdentifier
  • keyid:B9:59:F2:8E:CF:22:F0:86:D3:37:48:FF:76:14:18:BA:82:D8:55:87
authorityInfoAccess
  • CA Issuers - URI:http://ye2.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye2.c.lencr.org/98.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 94:4E:43:87:FA:EC:C1:EF:81:F3:19:24:26:A8:18:65:
  • 01:C7:D3:5F:38:02:01:3F:72:67:7D:55:37:2E:19:D8
  • Timestamp : Aug 5 06:42:34.746 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:8A:32:B4:26:AF:FE:8D:7B:25:53:EC:
  • 0C:F9:9A:5E:B0:37:1B:92:70:A5:42:89:74:93:35:B1:
  • 2F:52:1D:0B:94:02:20:53:A6:F2:B9:BF:F1:97:2B:EE:
  • 3D:97:D3:E0:34:8C:36:C3:C9:4B:DF:E5:9A:D9:23:60:
  • 1D:F8:D9:EE:CE:29:58
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 26:E3:64:6E:58:69:21:23:BC:34:3F:47:24:35:9B:37:
  • 92:CD:24:5A:88:D8:15:D3:93:33:FD:99:18:AB:47:23
  • Timestamp : Aug 5 06:42:33.601 2026 GMT
  • Extensions: 00:00:05:00:31:69:8C:89
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B8:85:27:58:18:89:40:52:57:18:F4:
  • D5:E4:DD:A4:86:FD:FE:2F:2A:5D:E6:01:0A:12:A2:92:
  • 5A:1C:DD:CA:E9:02:20:5C:F9:52:9B:CF:CC:F2:A3:FD:
  • A2:45:A5:CB:01:6D:5E:5F:4E:1C:16:45:27:D0:E7:43:
  • FB:C9:ED:7E:7B:E1:8D