SSL-Tools

SSL check results of mail.wito-sicherheitstechnik.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for mail.wito-sicherheitstechnik.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, 21 Nov 2023 10:25:18 +0000

The mailservers of mail.wito-sicherheitstechnik.de can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @mail.wito-sicherheitstechnik.de addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.wito-sicherheitstechnik.de
83.171.238.248
 -
supported
*.wito-sicherheitstechnik.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.wito-sicherheitstechnik.de address so far. Test mail delivery

Certificates

First seen at:

CN=*.wito-sicherheitstechnik.de

Certificate chain
  • *.wito-sicherheitstechnik.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • *.wito-sicherheitstechnik.de
Alternative Names
  • *.wito-sicherheitstechnik.de
  • wito-sicherheitstechnik.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2023-09-30
Not valid after
2023-12-29
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
D3:D3:08:CD:83:D3:AC:91:CE:1C:2F:86:D3:2F:BD:09:BC:95:61:64:D3:5B:CE:33:C7:D6:03:55:73:23:CE:03
SHA1
A4:7D:78:D9:86:E4:75:2A:D3:6C:63:C7:10:2F:60:3B:72:DE:CA:E2
X509v3 extensions
subjectKeyIdentifier
  • 02:AD:86:E0:EA:E5:0C:5B:AF:E2:3F:6F:EE:3C:0E:A1:05:A8:C1:70
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 : 7A:32:8C:54:D8:B7:2D:B6:20:EA:38:E0:52:1E:E9:84:
  • 16:70:32:13:85:4D:3B:D2:2B:C1:3A:57:A3:52:EB:52
  • Timestamp : Oct 1 00:51:52.752 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:AF:C9:37:BF:E5:D6:96:8D:F0:5F:BD:
  • DB:17:71:6A:E5:22:E9:78:C6:D8:79:5F:B1:46:1D:21:
  • 44:CB:04:20:95:02:20:26:F1:02:75:2E:B4:4F:67:B1:
  • 9E:D2:71:56:21:FC:74:A4:74:50:0C:D6:57:19:27:81:
  • 5F:15:A3:82:03:5D:A5
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : AD:F7:BE:FA:7C:FF:10:C8:8B:9D:3D:9C:1E:3E:18:6A:
  • B4:67:29:5D:CF:B1:0C:24:CA:85:86:34:EB:DC:82:8A
  • Timestamp : Oct 1 00:51:52.836 2023 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:35:D9:65:BF:45:7A:4B:68:F3:DC:B8:3D:
  • 7C:5F:DF:63:77:FA:DC:E7:0F:29:79:DB:CE:8E:F3:D3:
  • C7:CF:9A:07:02:20:70:4C:8E:76:A3:5E:52:E6:AC:30:
  • 2F:98:12:C0:AA:85:2C:9F:A1:5F:E0:82:16:0E:F6:D7:
  • CC:BF:07:F3:4C:35