SSL-Tools

SSL check results of doebling.cc

NEW You can also bulk check multiple servers.

Discover if the mail servers for doebling.cc 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, 16 Sep 2025 07:58:06 +0000

We can not guarantee a secure connection to the mailservers of doebling.cc!

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

/mailservers/doebling.cc

Servers

Incoming Mails

These servers are responsible for incoming mails to @doebling.cc addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.doebling.cc
2a0f:5707:aaf1:44bc::1
Results incomplete
10 not checked
DANE
errors
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.doebling.cc
89.144.30.131
 10
supported
autodiscover.canna24.store
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
9 s

Outgoing Mails

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

Certificates

First seen at:

CN=autodiscover.canna24.store

Certificate chain
  • autodiscover.canna24.store
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch
      • R12
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • autodiscover.canna24.store
Alternative Names
  • autodiscover.canna24.store
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R12
validity period
Not valid before
2025-09-16
Not valid after
2025-12-15
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
30:F8:DE:0F:D3:6C:91:D1:80:DD:37:6D:39:8F:AA:C1:A6:89:1E:B8:B7:95:31:F8:DC:EF:CF:69:E7:2F:48:A3
SHA1
F8:A0:5D:F2:B2:F0:EF:D9:75:8C:50:AF:F0:90:DA:15:2D:E4:67:A2
X509v3 extensions
subjectKeyIdentifier
  • 8A:71:E3:EE:81:44:C5:63:91:7F:A2:69:E2:08:BC:17:D5:C5:D0:36
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/115.crl
ct_precert_scts
  • 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 16 01:35:45.395 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:11:5A:0C:0E:46:E4:02:68:DA:3D:08:7A:
  • 09:B9:65:5C:1D:DB:63:14:0A:E4:EA:33:84:B8:17:C0:
  • E9:44:BC:21:02:20:6F:01:5A:43:45:18:70:E4:50:2D:
  • C3:06:55:C9:5E:AE:7F:AF:A0:A7:E2:66:87:4C:39:EB:
  • DE:A4:82:4A:49:21
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 1A:04:FF:49:D0:54:1D:40:AF:F6:A0:C3:BF:F1:D8:C4:
  • 67:2F:4E:EC:EE:23:40:68:98:6B:17:40:2E:DC:89:7D
  • Timestamp : Sep 16 01:35:47.429 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:63:B2:1E:45:54:CB:F8:1B:E4:E2:EA:BF:
  • 17:28:23:D0:FA:3B:66:E2:89:71:81:E2:27:E7:DA:2A:
  • 42:B0:26:95:02:21:00:CD:06:61:7A:9D:EA:CB:99:DD:
  • 2A:2B:D6:02:F1:15:8B:84:81:96:83:03:C8:68:59:58:
  • B9:BC:5A:D0:6C:53:D9

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