SSL-Tools

SSL check results of tuxnet24.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for tuxnet24.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, 23 Feb 2021 11:00:06 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
thor.tuxnet24.de
94.130.99.67
 10
supported
*.tuxnet24.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s
cs01.tomedia.de
185.3.235.169
Results incomplete
50
supported
not checked
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

We have received emails from these servers with @tuxnet24.de sender addresses. Test mail delivery

Host TLS Version & Cipher
thor.tuxnet24.de (94.130.99.67)
TLSv1.3 TLS_AES_256_GCM_SHA384

Certificates

First seen at:

CN=*.tuxnet24.de

Certificate chain
  • *.tuxnet24.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption
Subject
Common Name (CN)
  • *.tuxnet24.de
Alternative Names
  • *.tuxnet24.de
  • tuxnet24.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-11
Not valid after
2021-05-12
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
84:43:E6:26:B0:62:B2:1E:2F:FE:50:6E:97:3C:98:A5:A5:C0:00:A2:32:4A:78:50:1F:A1:B3:3C:AD:3F:B2:7E
SHA1
AC:FE:95:DF:38:54:80:08:30:D0:70:F0:68:60:12:E8:C4:2A:CB:62
X509v3 extensions
subjectKeyIdentifier
  • 58:22:F9:19:F4:C2:BB:CB:F0:FC:7D:79:AC:C0:9C:16:2C:D7:70:0C
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 : 44:94:65:2E:B0:EE:CE:AF:C4:40:07:D8:A8:FE:28:C0:
  • DA:E6:82:BE:D8:CB:31:B5:3F:D3:33:96:B5:B6:81:A8
  • Timestamp : Feb 11 20:44:35.104 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B2:1D:E7:DC:21:FC:C3:91:F8:69:99:
  • D8:06:55:80:07:4B:9D:1C:75:F0:C8:CF:13:CE:0F:46:
  • 90:59:6D:FD:4E:02:20:56:76:1D:40:31:32:AF:7E:54:
  • E8:49:74:D8:5A:6A:AA:A8:1E:85:24:81:98:69:91:64:
  • C2:68:71:A2:3A:C4:DC
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Feb 11 20:44:35.083 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:CC:AF:D2:58:F8:F4:83:E0:94:1A:C4:
  • 78:17:F7:67:98:6F:BD:43:DB:C0:94:8A:05:EB:B8:B8:
  • D5:7D:54:42:98:02:21:00:D0:90:96:30:CB:3E:A7:19:
  • 3B:C4:AA:5A:68:95:3C:F3:37:D0:19:DA:5F:8F:75:BE:
  • FD:15:DE:B7:2C:C7:4B:5B