SSL-Tools

SSL check results of duxbow.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for duxbow.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 Fri, 03 Oct 2025 21:54:00 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.duxbow.de
2a03:4000:62:aab:743d:fbff:fe05:9d1c
 0
supported
mail.duxbow.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s
mail.duxbow.de
89.58.26.137
 0
supported
mail.duxbow.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
4 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.duxbow.de

Certificate chain
  • mail.duxbow.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R12
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.duxbow.de
Alternative Names
  • autoconfig.duxbow.de
  • autoconfig.hndrk.blog
  • autodiscover.duxbow.de
  • autodiscover.hndrk.blog
  • autodiscover.paraskcd.com
  • mail.duxbow.de
  • mta-sts.duxbow.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R12
validity period
Not valid before
2025-09-30
Not valid after
2025-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
15:08:5B:2E:F9:9F:BC:AC:F3:6D:2B:A4:3A:F0:DE:AC:D0:FE:DE:86:8A:12:6B:3F:B5:32:41:E9:15:42:35:FF
SHA1
EF:7F:B7:DF:6B:A9:6C:2E:7E:DE:03:DF:F5:A8:1E:7E:FF:AC:A6:95
X509v3 extensions
subjectKeyIdentifier
  • E9:B3:BE:A7:C5:19:92:B3:FE:85:71:84:3D:D5:A3:0A:1D:5E:61:94
authorityKeyIdentifier
  • keyid:00:B5:29:F2:2D:8E:6F:31:E8:9B:4C:AD:78:3E:FA:DC:E9:0C:D1:D2
authorityInfoAccess
  • CA Issuers - URI:http://r12.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r12.c.lencr.org/38.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Sep 30 10:42:34.433 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2E:A0:51:88:CF:B5:77:73:F8:EA:23:11:
  • C6:D1:21:8D:AB:CF:63:A6:90:5E:62:3B:98:4F:C6:57:
  • D7:32:F9:3A:02:21:00:F5:88:A8:83:E4:ED:81:07:6E:
  • F1:4E:5F:2F:AC:72:84:18:4B:8C:ED:DB:04:F4:9F:75:
  • 81:D5:8E:BD:7B:18:08
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 12:F1:4E:34:BD:53:72:4C:84:06:19:C3:8F:3F:7A:13:
  • F8:E7:B5:62:87:88:9C:6D:30:05:84:EB:E5:86:26:3A
  • Timestamp : Sep 30 10:42:34.418 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:CF:F4:3C:B6:C9:1B:A2:CE:AE:27:2F:
  • 89:E5:18:A5:16:2B:1D:00:C3:7D:1A:02:11:74:4A:81:
  • EF:62:3C:DD:B0:02:21:00:BC:B9:32:A3:33:05:6E:C6:
  • 24:8F:B0:A6:BD:BD:07:3A:E7:F3:CD:BB:EE:B6:CD:A5:
  • D4:00:DE:3D:E7:FF:5B:53

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