SSL-Tools

SSL check results of bouquet24.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for bouquet24.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, 14 Nov 2025 14:24:05 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mx01.bouquet24.de
193.23.126.37
 10
supported
mx01.bouquet24.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.bouquet24.de
45.74.33.33
 20
supported
mail.bouquet24.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
13 s

Outgoing Mails

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

Certificates

First seen at:

CN=mx01.bouquet24.de

Certificate chain
  • mx01.bouquet24.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E8
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mx01.bouquet24.de
Alternative Names
  • autoconfig.bouquet24.de
  • autodiscover.bouquet24.de
  • imap.bouquet24.de
  • mta-sts.bouquet24.de
  • mx01.bouquet24.de
  • smtp.bouquet24.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E8
validity period
Not valid before
2025-10-24
Not valid after
2026-01-22
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1D:4E:B0:43:03:30:F3:43:25:9F:B2:30:56:FB:07:6B:63:84:CD:1F:4D:3B:E8:EC:00:40:30:8A:A4:A2:D7:AC
SHA1
77:7A:D9:FB:E5:A6:FD:A0:B0:AF:4F:22:99:76:33:CA:45:8D:AA:FA
X509v3 extensions
subjectKeyIdentifier
  • F2:E4:40:60:08:5D:0D:2B:46:BF:6B:C4:EB:21:FD:2F:5F:12:B1:53
authorityKeyIdentifier
  • keyid:8F:0D:13:A2:F6:2E:7E:D1:50:6C:33:18:38:5D:59:8E:23:72:91:CA
authorityInfoAccess
  • CA Issuers - URI:http://e8.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e8.c.lencr.org/118.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 64:11:C4:6C:A4:12:EC:A7:89:1C:A2:02:2E:00:BC:AB:
  • 4F:28:07:D4:1E:35:27:AB:EA:FE:D5:03:C9:7D:CD:F0
  • Timestamp : Oct 24 16:14:03.403 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:B6:A3:5B:92:EC:07:FC:78:FE:02:54:
  • 04:00:C0:D4:85:96:38:D2:77:15:B3:20:E8:E3:D6:18:
  • 58:AA:64:D3:3B:02:20:25:C0:5F:9A:4C:4D:C0:3A:B8:
  • 5F:6C:A3:02:CB:02:C6:9A:76:F6:B9:99:F4:72:16:8D:
  • E2:8A:2E:77:5F:99:78
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CB:38:F7:15:89:7C:84:A1:44:5F:5B:C1:DD:FB:C9:6E:
  • F2:9A:59:CD:47:0A:69:05:85:B0:CB:14:C3:14:58:E7
  • Timestamp : Oct 24 16:14:03.422 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:89:C8:3C:33:8A:E9:52:63:D0:43:C8:
  • 1C:9C:85:7E:7E:39:F1:62:5E:5F:30:C1:B7:50:F3:50:
  • EB:39:3D:5B:24:02:20:50:D6:4A:0E:AB:D8:FB:50:5D:
  • 1F:58:76:BC:9F:2C:95:E9:DC:A7:C7:CF:C9:9C:E9:E3:
  • A8:0D:E4:6E:8E:62:F1
First seen at:

CN=mail.bouquet24.de

Certificate chain
  • mail.bouquet24.de
    • remaining
    • 256 bit
    • ecdsa-with-SHA384
      • E8
        • remaining
        • 384 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.bouquet24.de
Alternative Names
  • imap.bouquet24.de
  • mail.bouquet24.de
  • smtp.bouquet24.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • E8
validity period
Not valid before
2025-09-24
Not valid after
2025-12-23
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
37:AF:1D:14:32:93:12:80:CF:29:FE:24:DC:44:EE:4C:8C:41:E1:DC:6A:EB:4C:74:81:4B:C8:A2:38:A4:4F:FD
SHA1
3D:F2:45:2A:F0:9F:8B:CB:8F:26:30:D6:77:53:F7:EA:9B:28:4F:70
X509v3 extensions
subjectKeyIdentifier
  • 86:24:94:E7:BB:74:9D:B6:78:1C:A7:00:ED:38:23:7F:CC:3C:48:F9
authorityKeyIdentifier
  • keyid:8F:0D:13:A2:F6:2E:7E:D1:50:6C:33:18:38:5D:59:8E:23:72:91:CA
authorityInfoAccess
  • CA Issuers - URI:http://e8.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://e8.c.lencr.org/83.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 24 19:28:17.852 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:66:0C:8B:D2:08:8B:E2:03:D3:76:5B:E5:
  • 60:FD:FB:E4:D4:B8:F1:BF:C5:10:2D:00:00:A7:0F:52:
  • 55:1C:1D:D6:02:21:00:D5:D9:E4:21:05:DE:1C:05:1B:
  • 65:66:09:09:4F:EA:3C:C4:28:7E:54:74:6E:D7:54:8E:
  • 61:17:63:82:AC:FC:4F
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
  • 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
  • Timestamp : Sep 24 19:28:17.861 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:33:5C:31:90:A2:1E:41:70:CC:79:2A:48:
  • 15:D8:FF:3C:31:D1:69:FD:5D:A5:0B:D6:06:05:9B:18:
  • 8D:EF:3C:20:02:21:00:ED:53:E4:3E:0B:39:6C:27:C5:
  • 9B:91:BD:63:0F:A7:8E:35:08:92:0E:36:4D:B1:D9:7C:
  • B8:13:65:1F:21:17:CD

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