SSL check results of duschek.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for duschek.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

Report created Sun, 19 Jul 2026 00:31:35 +0000

We can not guarantee a secure connection to the mailservers of duschek.com!

Please contact the operator of duschek.com and ask him or her to solve this problem. This result stays accessible under the following address:

/mailservers/duschek.com

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.duschek.com
93.92.162.122
Results incomplete
10
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
bimini.austria4u.at
217.160.24.62
20
supported
bimini.austria4u.at
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 @duschek.com address so far. Test mail delivery

Certificates

First seen at:

CN=bimini.austria4u.at

Certificate chain
  • bimini.austria4u.at
    • remaining
    • 3072 bit
    • sha256WithRSAEncryption

      • R13
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • bimini.austria4u.at
Alternative Names
  • bimini.austria4u.at
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R13
validity period
Not valid before
2026-05-25
Not valid after
2026-08-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
Fingerprints
SHA256
BB:C1:2E:82:E5:21:6A:75:CE:85:3E:D5:43:0E:41:F6:62:70:A1:91:B5:C7:74:AA:50:6A:D6:F8:96:93:23:8B
SHA1
99:39:E1:8D:1C:07:5A:C9:A3:7E:60:93:B7:92:FC:6B:5D:B8:89:DF
X509v3 extensions
subjectKeyIdentifier
  • 9B:54:4D:42:47:7E:23:9E:E8:1C:B3:49:28:DD:A3:FF:C0:85:43:89
authorityKeyIdentifier
  • keyid:E7:AB:9F:0F:2C:33:A0:53:D3:5E:4F:78:C8:B2:84:0E:3B:D6:92:33
authorityInfoAccess
  • CA Issuers - URI:http://r13.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r13.c.lencr.org/116.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : C8:A3:C4:7F:C7:B3:AD:B9:35:6B:01:3F:6A:7A:12:6D:
  • E3:3A:4E:43:A5:C6:46:F9:97:AD:39:75:99:1D:CF:9A
  • Timestamp : May 25 02:45:20.935 2026 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:83:36:D9:19:4A:1A:2D:6B:88:1C:06:
  • 29:24:4F:75:2E:10:EC:04:33:00:0E:05:AA:5F:A5:F5:
  • 9C:BD:E6:45:CA:02:20:3E:9E:B0:AF:07:5A:89:D3:F3:
  • D0:D9:CE:F2:9D:46:A2:08:90:14:DE:B6:9D:58:A9:AA:
  • F3:70:EF:E1:B5:E0:89
  • 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 : May 25 02:45:21.701 2026 GMT
  • Extensions: 00:00:05:00:16:90:61:B5
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:FF:26:95:0E:92:BB:08:61:08:E6:19:
  • 99:93:40:80:60:19:E2:78:BC:4A:6E:11:F3:DD:58:65:
  • 3F:10:A1:D5:2B:02:20:66:A8:6D:13:8F:1A:1C:91:49:
  • AC:5F:02:FA:87:DC:E2:43:DE:6C:F6:E4:1F:B9:D7:BE:
  • B0:E1:AE:16:BF:B9:E6