SSL-Tools

SSL check results of tissom.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for tissom.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 Sat, 18 Oct 2025 16:42:38 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
tissom.webseitenserver.com
2a03:4000:20:2a2:45:90:5:194
 10
supported
tissom.webseitenserver.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
8 s
tissom.webseitenserver.com
45.90.5.194
 10
supported
tissom.webseitenserver.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • SSLv3
7 s

Outgoing Mails

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

Certificates

First seen at:

CN=tissom.webseitenserver.com

Certificate chain
  • tissom.webseitenserver.com
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E7
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • tissom.webseitenserver.com
Alternative Names
  • mx0.unitel2000.de
  • tissom.webseitenserver.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E7
validity period
Not valid before
2025-09-08
Not valid after
2025-12-07
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
86:98:5A:4A:76:33:EA:B7:9C:D7:F1:C8:73:BF:A5:FD:FA:7F:95:B6:F5:DE:97:A5:30:FD:86:04:DB:16:FE:B9
SHA1
82:DF:91:63:E4:D1:42:FC:E7:04:3C:D6:9E:AC:82:A4:AC:9D:FB:C2
X509v3 extensions
subjectKeyIdentifier
  • 34:3F:9F:7E:98:37:D7:1C:33:25:27:14:82:B1:F9:23:70:93:73:59
authorityKeyIdentifier
  • keyid:AE:48:9E:DC:87:1D:44:A0:6F:DA:A2:E5:60:74:04:78:C2:9C:00:80
authorityInfoAccess
  • CA Issuers - URI:http://e7.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e7.c.lencr.org/101.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : Sep 8 03:10:17.931 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E3:D4:2D:CC:3F:CA:08:C6:70:A9:92:
  • EB:F6:56:BF:A7:23:86:A8:F0:9F:EA:EB:EB:63:97:03:
  • A6:11:B8:1C:D3:02:21:00:F1:99:42:DC:55:84:BD:A3:
  • 2F:CE:B8:A2:92:38:33:B9:0D:D6:A3:C2:38:70:A1:2F:
  • DE:AB:12:B1:C5:03:84:E0
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
  • 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
  • Timestamp : Sep 8 03:10:17.994 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7E:81:5C:95:74:63:5A:2E:31:45:38:9B:
  • D2:B4:E9:23:DC:17:FF:13:24:9E:97:89:DC:7D:4A:51:
  • 35:60:92:EC:02:21:00:FF:42:3B:1F:F1:D6:06:57:83:
  • 0F:F4:C6:3A:25:F6:BD:81:D8:45:67:ED:FF:25:62:01:
  • 2A:22:2B:94:BF:6F:3C

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.tissom.webseitenserver.com
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
valid
valid