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, 11 Jun 2024 11:37:08 +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-06-11
Not valid after
2024-09-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
36:37:DB:C1:F5:A6:7E:28:10:00:C1:45:FE:66:B2:CC:8A:81:B1:98:A9:A8:06:8C:E0:D1:66:C0:89:B9:17:35
SHA1
D7:84:3F:93:FE:2E:D4:6D:A4:54:83:64:39:08:4C:31:FE:DF:3B:08
X509v3 extensions
subjectKeyIdentifier
  • C2:2E:91:2D:AC:09:9F:3D:2F:27:4B:C6:75:BC:0B:65:37:6B:4C:15
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 : Jun 11 11:16:03.363 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:2C:99:8B:34:2B:1E:2C:20:90:E3:17:CC:
  • 4D:97:B1:9D:1E:BC:94:7C:6C:04:BB:51:18:72:4C:CB:
  • 21:5D:23:D4:02:20:3B:67:82:34:3B:A6:4E:6C:49:D8:
  • 91:83:02:62:C6:1E:7B:9E:DA:35:76:38:3A:F8:AF:DA:
  • E6:35:46:AB:00:9E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 48:B0:E3:6B:DA:A6:47:34:0F:E5:6A:02:FA:9D:30:EB:
  • 1C:52:01:CB:56:DD:2C:81:D9:BB:BF:AB:39:D8:84:73
  • Timestamp : Jun 11 11:16:03.429 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:30:CC:04:08:75:75:52:8C:C6:B5:A3:AA:
  • 35:8F:56:D3:3B:C5:73:C7:9F:B9:CF:9A:74:5A:57:25:
  • 63:43:EA:AA:02:20:74:97:EB:14:60:B4:D3:18:96:A8:
  • 26:B8:A1:C1:A7:B7:21:ED:1E:A1:34:62:6B:79:9A:42:
  • 70:A9:68:EC:6A:0A