SSL check results of dexalo.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for dexalo.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 Sat, 15 Aug 2026 19:29:23 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
smtp.dexalo.de
2a0a:51c0:30:215::1
10
supported
mail.dexalo.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
3 s
smtp.dexalo.de
31.214.144.150
10
supported
mail.dexalo.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 @dexalo.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.dexalo.de

Certificate chain
  • mail.dexalo.de
    • remaining
    • 256 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.dexalo.de
Alternative Names
  • imap.dexalo.de
  • lovelace.dexalo.de
  • mail.dexalo.de
  • smtp.dexalo.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE2
validity period
Not valid before
2026-08-14
Not valid after
2026-11-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
56:D4:E3:0F:7B:37:2C:9F:8F:8F:21:E7:AC:34:FC:A6:08:B7:E5:76:D4:45:B7:B8:4B:79:F1:07:D7:E5:C1:21
SHA1
93:11:C5:56:29:2A:76:EF:F0:86:28:35:63:7C:9C:C3:1A:2C:AC:3C
X509v3 extensions
subjectKeyIdentifier
  • BE:D9:25:78:2F:44:C7:DE:69:40:BF:E5:CD:58:AD:2E:6A:FB:B9:18
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/107.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CB:38:F7:15:89:7C:84:A1:44:5F:5B:C1:DD:FB:C9:6E:
  • F2:9A:59:CD:47:0A:69:05:85:B0:CB:14:C3:14:58:E7
  • Timestamp : Aug 14 20:34:03.778 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:0A:5C:8E:60:88:4F:D2:58:01:A3:57:88:
  • 7B:20:E5:2A:02:D8:A3:5B:B8:BA:F9:2D:8C:9C:04:2C:
  • B9:DB:CE:A4:02:20:3B:79:5E:BD:23:F4:F6:87:21:89:
  • 27:85:6A:14:F8:16:25:57:55:EE:12:AE:53:9B:2A:54:
  • 9A:CE:29:89:BB:73
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A8:26:CB:E3:0A:C6:35:12:46:53:3F:E0:65:F1:4F:19:
  • D9:6E:19:08:13:C4:1D:D9:6D:79:00:B3:12:3C:55:27
  • Timestamp : Aug 14 20:34:04.029 2026 GMT
  • Extensions: 00:00:05:00:1C:85:18:1A
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6C:7E:4D:60:63:70:F7:85:AE:25:8A:F4:
  • 63:B8:45:3D:9C:84:55:C7:6B:2B:15:10:22:F5:05:60:
  • 3D:CB:6A:9F:02:21:00:9D:30:EA:99:BD:23:08:EC:C6:
  • 92:85:41:73:30:DE:CA:15:28:E4:44:68:82:5B:C2:C8:
  • BB:5E:22:E8:31:3B:91