SSL-Tools

SSL check results of sys4.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for sys4.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, 10 Jan 2023 13:17:34 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.sys4.de
2001:1578:400:111::7
 10
supported
mail.sys4.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
18 s
mail.sys4.de
194.126.158.132
 10
supported
mail.sys4.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
17 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.sys4.de

Certificate chain
  • mail.sys4.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.sys4.de
Alternative Names
  • mail.sys4.de
  • mx1.sys4.de
  • webmail.sys4.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-01-01
Not valid after
2023-04-01
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
3F:1E:6F:52:C3:4F:98:18:87:85:91:75:B1:22:E5:A1:A8:A9:DD:E0:05:45:33:E6:42:E4:D2:CB:97:E6:EE:A1
SHA1
E3:D3:03:16:7D:0D:A9:A9:B2:DB:C8:7D:EA:93:BE:AD:43:A4:61:4F
X509v3 extensions
subjectKeyIdentifier
  • 53:E3:7A:42:F6:B1:A5:83:27:1C:C6:6B:60:B1:2B:1A:69:B7:E3:DC
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
  • B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
  • Timestamp : Jan 2 00:02:09.408 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:6D:3F:4A:AC:CB:FB:66:DA:47:B7:E2:EA:
  • C0:26:D7:40:22:1B:AB:B8:29:94:2A:A8:D2:DC:EB:70:
  • 64:C6:F8:A7:02:21:00:C9:78:D9:5B:49:DA:F5:03:2B:
  • 63:9C:FD:2A:15:98:5C:4D:01:AE:18:DC:81:14:12:23:
  • E1:88:72:67:42:20:0D
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Jan 2 00:02:09.850 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:33:BF:5D:37:D9:A4:26:1B:69:54:FF:33:
  • 18:56:EB:E6:A0:9D:3F:B6:88:7D:00:0F:B0:0E:E5:BB:
  • A0:D9:52:AB:02:20:3C:88:59:CA:4C:3F:04:6E:FD:2D:
  • 55:01:3E:3A:40:D3:05:9F:EA:A3:0E:B1:7B:66:0A:12:
  • FC:F1:BC:CA:75:92

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.mail.sys4.de
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid