SSL-Tools

SSL check results of edaxi.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for edaxi.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, 03 Jan 2025 22:43:01 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.edaxi.de
2a01:4f8:10a:3c1f::2
 10
supported
mail.edaxi.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.edaxi.de
88.99.211.39
 10
supported
mail.edaxi.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 @edaxi.de sender addresses. Test mail delivery

Host TLS Version & Cipher
mars.edaxi.de (IPv6:2a01:4f8:13b:37cb::2)
TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384

Certificates

First seen at:

CN=mail.edaxi.de

Certificate chain
  • mail.edaxi.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E5
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.edaxi.de
Alternative Names
  • mail.edaxi.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E5
validity period
Not valid before
2025-01-03
Not valid after
2025-04-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
DD:13:8C:FF:CB:20:BE:F2:5F:63:0B:0C:03:48:17:B8:6A:8C:F4:37:D1:7A:5D:D4:35:38:33:8C:72:CD:EB:5A
SHA1
6D:03:5A:E7:CA:B3:E1:28:97:3A:FB:45:1C:9A:67:65:03:D2:E5:82
X509v3 extensions
subjectKeyIdentifier
  • 03:3A:CF:CB:33:44:83:4F:15:17:B6:EF:51:49:A4:16:C7:DD:20:C6
authorityKeyIdentifier
  • keyid:9F:2B:5F:CF:3C:21:4F:9D:04:B7:ED:2B:2C:C4:C6:70:8B:D2:D7:0D
authorityInfoAccess
  • OCSP - URI:http://e5.o.lencr.org
  • CA Issuers - URI:http://e5.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E0:92:B3:FC:0C:1D:C8:E7:68:36:1F:DE:61:B9:96:4D:
  • 0A:52:78:19:8A:72:D6:72:C4:B0:4D:A5:6D:6F:54:04
  • Timestamp : Jan 3 16:49:38.162 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:66:55:24:E4:EF:B0:EF:76:F2:68:7B:CC:
  • B9:E5:15:9C:12:56:D6:54:48:F2:C6:53:E7:0E:54:59:
  • 06:1F:B0:0D:02:20:6B:80:BB:32:BD:6B:7D:21:10:A3:
  • E8:AA:FF:9C:4F:D6:21:7D:3F:3B:B9:61:41:82:6C:46:
  • BB:C5:FA:91:FF:1D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 4E:75:A3:27:5C:9A:10:C3:38:5B:6C:D4:DF:3F:52:EB:
  • 1D:F0:E0:8E:1B:8D:69:C0:B1:FA:64:B1:62:9A:39:DF
  • Timestamp : Jan 3 16:49:38.142 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5C:F0:DC:0F:41:5B:5F:1A:7F:D5:CE:74:
  • 85:B2:85:A8:F9:3F:86:24:B7:32:CE:68:16:9C:03:2E:
  • B9:2F:F9:CA:02:20:6B:8F:64:6F:B6:02:C1:C6:F0:EB:
  • 5D:3E:FD:CC:09:15:93:67:7E:B5:EB:3E:58:29:95:D7:
  • 69:16:DE:DD:F4:A2