SSL-Tools

SSL check results of wachutka.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for wachutka.com 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, 05 Nov 2024 07:26:38 +0000

The mailservers of wachutka.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @wachutka.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
okeanos.evfr.de
2a01:4f8:162:1030::1
 10
supported
tardys.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s
okeanos.evfr.de
5.9.85.236
 10
supported
tardys.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 @wachutka.com address so far. Test mail delivery

Certificates

First seen at:

CN=tardys.de

Certificate chain
  • tardys.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E6
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • tardys.de
Alternative Names
  • okeanos.evfr.de
  • tardys.de
  • wachutka.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E6
validity period
Not valid before
2024-11-05
Not valid after
2025-02-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
75:32:F0:A0:2B:AF:CA:03:17:C3:2C:B3:1D:DF:38:A3:A2:61:05:E4:62:59:93:46:3A:61:32:16:F5:54:DE:B2
SHA1
60:39:49:33:54:A5:93:CC:41:2D:69:57:44:21:F4:18:00:EB:20:1D
X509v3 extensions
subjectKeyIdentifier
  • 80:0D:63:B8:92:43:D1:BC:A3:FC:27:0A:0A:A8:46:4F:25:66:11:5B
authorityKeyIdentifier
  • keyid:93:27:46:98:03:A9:51:68:8E:98:D6:C4:42:48:DB:23:BF:58:94:D2
authorityInfoAccess
  • OCSP - URI:http://e6.o.lencr.org
  • CA Issuers - URI:http://e6.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E6:D2:31:63:40:77:8C:C1:10:41:06:D7:71:B9:CE:C1:
  • D2:40:F6:96:84:86:FB:BA:87:32:1D:FD:1E:37:8E:50
  • Timestamp : Nov 5 07:08:48.960 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:EF:4A:48:4A:56:A9:0D:CB:DD:DC:B1:
  • A2:D4:E0:53:1F:09:E3:2D:C9:3B:AD:74:95:3B:F5:73:
  • 45:07:96:D5:F1:02:20:4B:7B:99:98:B4:E4:A0:03:FC:
  • 33:E1:B7:10:8B:40:08:01:DB:0E:02:89:F7:C6:D2:CE:
  • E8:B5:1B:EA:23:C6:E5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Nov 5 07:08:48.954 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:97:9D:DE:74:90:CE:28:22:90:08:F9:
  • 20:A0:14:AC:25:D4:E7:16:04:CA:5F:4C:60:FF:14:5F:
  • 3E:24:DC:6A:CB:02:20:2B:81:2C:41:0F:20:92:57:9F:
  • D0:37:F9:D7:13:8B:50:03:4B:FB:F1:55:6E:40:51:ED:
  • 53:A3:95:3A:A8:E5:CD