SSL-Tools

SSL check results of decrux.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for decrux.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 Mon, 16 Jan 2023 17:56:32 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
decrux-de.mail.compitence.net
212.99.201.25
 10
supported
*.mail.compitence.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s
decrux-de.mail.compitence.net
212.99.201.27
 10
supported
*.mail.compitence.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=*.mail.compitence.net

Certificate chain
  • *.mail.compitence.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.mail.compitence.net
Alternative Names
  • *.mail.compitence.net
  • mail.compitence.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-11-26
Not valid after
2023-02-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
9B:3D:71:07:E6:7C:DD:F7:0B:AE:FE:1D:68:5F:50:5F:B4:A2:EF:54:C4:17:BE:8F:05:E9:99:81:15:94:B0:EA
SHA1
DA:88:81:91:17:92:7A:95:8C:C0:53:65:53:C9:08:19:98:34:5B:6F
X509v3 extensions
subjectKeyIdentifier
  • 51:73:9D:05:2F:A3:45:91:D4:35:E6:40:4E:B9:B8:A9:EB:C0:BF:E6
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 : 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 : Nov 26 13:24:52.158 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:56:BE:6B:86:1C:F6:54:86:C0:40:2C:5A:
  • 40:90:9D:D4:75:A9:9F:6D:EB:2E:30:79:B1:25:A3:91:
  • B2:FD:F3:84:02:20:04:51:9A:56:38:4C:EE:15:77:E1:
  • 43:87:CE:5E:1C:BE:06:5C:1F:9D:31:73:5D:8D:E1:08:
  • 7A:72:E1:9C:76:7E
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B7:3E:FB:24:DF:9C:4D:BA:75:F2:39:C5:BA:58:F4:6C:
  • 5D:FC:42:CF:7A:9F:35:C4:9E:1D:09:81:25:ED:B4:99
  • Timestamp : Nov 26 13:24:52.636 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:57:41:0E:DB:D2:E7:47:A2:7C:D1:53:B1:
  • F8:C1:EA:67:39:E9:4B:CD:81:56:20:D9:38:8B:F0:06:
  • 89:BE:DF:01:02:21:00:F6:00:09:17:C2:13:08:89:C2:
  • 71:E4:A0:7A:30:B7:EC:6B:B1:52:64:4A:F7:6C:85:EF:
  • CF:1A:31:E0:24:55:31