SSL-Tools

SSL check results of server7.diesendorfsystems-server.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for server7.diesendorfsystems-server.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, 29 Mar 2024 06:23:42 +0000

The mailservers of server7.diesendorfsystems-server.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @server7.diesendorfsystems-server.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
server7.diesendorfsystems-server.de
94.130.49.120
 -
supported
tech.ruhr
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

We have not received any emails from a @server7.diesendorfsystems-server.de address so far. Test mail delivery

Certificates

First seen at:

CN=tech.ruhr

Certificate chain
  • tech.ruhr
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • tech.ruhr
Alternative Names
  • diesendorfsystems.de
  • server7.diesendorfsystems-server.de
  • tech.ruhr
  • www.diesendorfsystems.de
  • www.server7.diesendorfsystems-server.de
  • www.tech.ruhr
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-29
Not valid after
2024-06-27
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8F:49:BB:D5:E7:C3:09:C5:F2:0B:03:C9:9F:61:4C:CD:DC:B6:53:5A:BA:2D:F1:9A:F4:30:22:E1:20:FD:A3:18
SHA1
6C:6C:D8:3D:89:74:08:84:F3:67:8A:AD:8F:20:04:8A:63:1B:9F:80
X509v3 extensions
subjectKeyIdentifier
  • CD:A0:B2:F9:F0:6A:6E:72:F6:AC:39:E4:9F:51:D4:D1:81:5D:83:51
authorityKeyIdentifier
  • keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
authorityInfoAccess
  • OCSP - URI:http://r3.o.lencr.org
  • CA Issuers - URI:http://r3.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • 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 : Mar 29 06:22:17.321 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:4F:86:E8:35:27:DD:97:E9:28:34:72:DE:
  • 56:32:73:7D:B8:60:18:47:D5:11:37:E8:FA:99:A9:00:
  • 85:BF:C1:36:02:20:02:08:C8:1B:70:2A:EA:EA:AB:45:
  • 15:44:9C:52:76:25:B5:85:21:CE:F2:36:93:D8:41:4A:
  • 99:59:81:3E:4D:5F
  • 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 : Mar 29 06:22:17.385 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:55:5F:FA:E8:27:C4:45:11:1B:D0:BF:7A:
  • AE:62:EF:74:A5:91:D7:7D:33:5D:78:93:A1:ED:F8:31:
  • A8:57:E4:A5:02:21:00:B6:50:B5:86:24:CC:FE:DA:02:
  • B1:E7:0D:4E:AC:52:61:C6:0E:22:8E:3A:5B:2E:82:25:
  • 03:27:03:48:F1:8C:3D