SSL-Tools

SSL check results of digiplex.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for digiplex.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, 10 Jan 2025 19:07:45 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
digiplex.de
2a02:a00:e00f:fffe::13:517
 10
supported
digiplex.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
digiplex.de
46.41.0.162
 10
supported
digiplex.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=digiplex.de

Certificate chain
  • digiplex.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • digiplex.de
Alternative Names
  • digiplex.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2025-01-06
Not valid after
2025-04-06
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AF:EE:6A:E9:15:1E:ED:88:0C:B7:EE:4D:D6:B2:61:9B:4F:96:B2:F8:49:1A:5C:EE:C5:8C:47:A1:0B:9D:88:2F
SHA1
38:8F:FB:78:21:85:74:7A:0B:48:D9:FA:55:E6:5E:FB:64:32:A9:CB
X509v3 extensions
subjectKeyIdentifier
  • A0:A3:D0:6B:37:06:B8:F1:4D:AE:23:A6:D1:28:4D:51:08:99:FA:1E
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • OCSP - URI:http://e6.o.lencr.org
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Jan 6 08:37:40.470 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:A8:EA:F8:76:0B:DD:EE:3B:95:3C:A5:
  • 5D:2A:AE:9C:60:CC:00:3A:29:1E:94:14:EB:8D:16:EE:
  • 27:85:F5:DF:A4:02:21:00:AC:87:C6:F8:BC:02:57:9A:
  • EF:84:11:85:9A:43:6C:6C:BD:79:53:64:41:93:A5:68:
  • 31:C0:2C:B9:5D:25:C4:DC
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 73:20:22:0F:08:16:8A:F9:F3:C4:A6:8B:0A:B2:6A:9A:
  • 4A:00:EE:F5:77:85:8A:08:4D:05:00:D4:A5:42:44:59
  • Timestamp : Jan 6 08:37:40.483 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:BC:A7:A6:7E:85:D2:1E:45:6F:0F:C8:
  • C6:58:3C:97:4A:6B:44:E1:04:4F:30:9F:54:3C:E5:52:
  • 5D:73:61:7C:BF:02:21:00:92:30:63:3D:D0:CA:6A:18:
  • 4C:A1:4A:E1:AE:29:E1:2C:D4:CF:A0:37:1A:28:0D:05:
  • 34:14:5A:ED:26:EE:EC:73