SSL-Tools

SSL check results of tt-lan.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for tt-lan.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 Thu, 25 Apr 2024 21:04:12 +0000

The mailservers of tt-lan.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @tt-lan.de addresses.

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

Certificates

First seen at:

CN=tt-lan.de

Certificate chain
  • tt-lan.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • tt-lan.de
Alternative Names
  • *.tt-lan.de
  • tt-lan.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-23
Not valid after
2024-06-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1F:B3:47:3D:AC:B7:F3:06:48:A3:36:58:6C:1D:1F:58:18:94:AB:33:20:F1:E5:BA:DB:5D:AB:B4:B5:BC:63:65
SHA1
BF:6C:45:2E:A7:BB:70:6F:EA:F5:4E:6A:27:B7:B3:CA:EC:5B:8C:9E
X509v3 extensions
subjectKeyIdentifier
  • 87:5D:36:0C:D5:A6:5C:9D:26:8D:23:3E:AF:B4:59:5D:66:1E:03:A6
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 23 21:36:11.082 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:DA:47:C1:8A:4B:05:1E:0E:DA:9A:8E:
  • 20:4C:8A:35:1E:7C:6B:58:E7:8D:0B:DD:87:E7:F2:93:
  • B1:2C:2D:66:A0:02:20:5A:77:7A:1F:5E:5A:CE:4A:76:
  • 09:73:54:E9:A6:68:0F:B9:0F:B5:6E:7C:45:DB:F1:B8:
  • 83:B1:B8:5B:F3:29:80
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 76:FF:88:3F:0A:B6:FB:95:51:C2:61:CC:F5:87:BA:34:
  • B4:A4:CD:BB:29:DC:68:42:0A:9F:E6:67:4C:5A:3A:74
  • Timestamp : Mar 23 21:36:11.146 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7D:A1:24:53:C4:26:A4:8E:CC:D3:79:42:
  • 33:40:59:CC:20:7D:52:06:1D:A3:F1:03:1F:EF:F5:72:
  • A3:0C:6A:F2:02:21:00:AC:58:C0:A4:64:88:7B:DF:07:
  • E9:E7:51:E9:00:C4:2B:BD:18:83:FB:29:04:61:18:E2:
  • DE:35:2F:A6:D4:E0:84