SSL-Tools

SSL check results of mail.trendware.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.trendware.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, 13 Jul 2026 09:41:07 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.trendware.de
2a01:4f8:161:93c9::2
 50
supported
mail.trendware.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
mail.trendware.de
91.99.39.13
 50
supported
mail.trendware.de
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 @mail.trendware.de address so far. Test mail delivery

Certificates

First seen at:

CN=mail.trendware.de

Certificate chain
  • mail.trendware.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • YE1
        • remaining
        • 384 bit
        • ecdsa-with-SHA384
          • Root YE
            • remaining
            • 384 bit
            • ecdsa-with-SHA384
              • ISRG Root X2 (Certificate is self-signed.)
                • remaining
                • 384 bit
                • ecdsa-with-SHA384
Subject
Common Name (CN)
  • mail.trendware.de
Alternative Names
  • mail.trendware.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • YE1
validity period
Not valid before
2026-06-12
Not valid after
2026-09-10
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
Fingerprints
SHA256
68:BB:86:BF:C9:81:29:F3:A3:4B:9C:3B:1A:6D:02:9A:EC:17:1B:BA:A1:8E:B3:D3:C9:C7:C8:D5:CD:3F:61:D9
SHA1
59:28:81:5F:97:17:D6:54:72:2A:A9:79:68:EB:6D:DF:31:07:96:78
X509v3 extensions
subjectKeyIdentifier
  • 97:1D:7A:18:52:7B:E1:72:28:A4:F8:5F:A2:A5:49:85:D2:DC:1A:A6
authorityKeyIdentifier
  • keyid:BB:20:CA:47:0B:FE:D7:E5:9C:F9:8F:09:2A:A3:8C:37:45:B1:BC:D8
authorityInfoAccess
  • CA Issuers - URI:http://ye1.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://ye1.c.lencr.org/33.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CB:38:F7:15:89:7C:84:A1:44:5F:5B:C1:DD:FB:C9:6E:
  • F2:9A:59:CD:47:0A:69:05:85:B0:CB:14:C3:14:58:E7
  • Timestamp : Jun 12 08:22:45.161 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:29:8C:11:44:C4:94:FD:20:3B:97:85:02:
  • 87:FD:1E:AB:FF:C5:08:FA:D5:A4:6E:3C:91:41:7C:34:
  • 4C:2C:E3:24:02:21:00:CE:25:63:25:A5:78:B4:24:4E:
  • 50:DA:45:62:54:A0:DB:02:3A:D1:EE:B2:56:21:1B:BC:
  • E7:BB:6F:78:6C:43:CF
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:8B:9D:6B:0F:FE:BF:81:B4:79:39:C6:D2:31:0A:86:
  • D6:D1:02:D4:F0:46:E2:18:2C:9D:E3:5F:5E:26:25:EF
  • Timestamp : Jun 12 08:22:45.703 2026 GMT
  • Extensions: 00:00:05:00:1D:D7:7F:C2
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:EC:40:1D:1F:D9:0E:60:54:69:3B:4A:
  • E6:42:02:C0:62:AB:C3:45:9D:C5:EA:0C:E8:11:F9:35:
  • 9B:D4:EC:43:39:02:21:00:CA:31:98:55:EB:BF:34:45:
  • 8F:C9:04:47:C6:DC:C9:9F:A2:06:F2:1A:E4:B0:85:87:
  • BD:31:4F:00:3C:C6:7E:4B