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 Tue, 20 Aug 2024 11:56:29 +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:13b:37cb::2
 10
supported
mail.edaxi.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
15 s
mail.edaxi.de
94.130.132.6
 10
supported
mail.edaxi.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
15 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
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 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)
  • R11
validity period
Not valid before
2024-08-20
Not valid after
2024-11-18
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
FF:F8:DF:A9:0A:34:D7:9F:23:CA:49:26:D6:F6:66:85:42:74:AB:87:5D:F9:2F:2F:66:3E:00:F2:C2:75:89:F0
SHA1
EC:58:09:1A:D7:B0:A1:08:67:9A:2F:D3:AA:23:70:AE:0B:9D:A4:62
X509v3 extensions
subjectKeyIdentifier
  • B5:B4:9E:BF:2D:F4:D6:8F:1C:C7:E4:52:25:CC:C0:AD:E6:6B:23:82
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.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 : Aug 20 11:55:39.644 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F5:1C:91:54:76:79:D8:8C:DF:0B:57:
  • 14:53:3B:06:24:2F:75:34:4C:93:9B:50:63:C4:48:4B:
  • 86:FB:7B:8D:8F:02:20:55:F5:65:A6:09:A7:64:A7:9D:
  • FC:C7:A8:A2:65:4B:F3:65:DD:62:FD:02:07:60:9D:68:
  • 11:A5:F5:4E:A2:02:9C
  • 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 : Aug 20 11:55:39.680 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:3C:FA:8C:ED:EC:46:D4:0D:2C:7C:5A:71:
  • 17:D2:67:B4:AE:FC:9F:F5:27:F4:BF:E1:F6:C5:BF:01:
  • 43:88:17:8F:02:21:00:AC:48:CF:57:15:0A:B2:E6:DB:
  • 7C:A9:EC:DB:F7:19:F3:B7:BF:36:2D:5D:2C:F6:AC:4A:
  • 58:F2:29:9B:45:CD:D1