SSL-Tools

SSL check results of dargels.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for dargels.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 Sun, 21 Jan 2024 14:30:35 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.dargels.de
89.58.25.167
 10
supported
mdol-nethserver.dargels.de
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
11 s

Outgoing Mails

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

Certificates

First seen at:

CN=mdol-nethserver.dargels.de

Certificate chain
  • mdol-nethserver.dargels.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mdol-nethserver.dargels.de
Alternative Names
  • collabora.dargels.de
  • dargels.de
  • dev.dargels.de
  • imap.dargels.de
  • isi-dev.dargels.de
  • mail.dargels.de
  • mdol-nethserver.dargels.de
  • myancestry.de
  • nextcloud.dargels.de
  • piler.dargels.de
  • smtp.dargels.de
  • stephdl.dargels.de
  • test.dargels.de
  • webtrees.myancestry.de
  • wp.dargels.de
  • www.dargels.de
  • www.myancestry.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-01-15
Not valid after
2024-04-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
09:1F:2D:E8:AD:8A:3D:69:CB:F8:E1:BF:DA:E0:88:16:58:36:68:03:E4:3A:48:01:F4:DD:EF:6A:06:ED:0C:C1
SHA1
1D:B1:4A:15:43:77:2C:00:CE:06:35:00:00:21:93:51:F6:DE:01:48
X509v3 extensions
subjectKeyIdentifier
  • 26:28:E9:33:5D:C9:32:19:EA:14:08:42:BD:CE:C3:08:A8:77:56:5E
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 : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Jan 15 04:36:10.258 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:F7:91:FA:E8:EC:EA:95:35:D8:40:B2:
  • 06:E5:32:33:0A:B8:00:1D:4D:18:A9:B4:91:8B:6D:D4:
  • CB:E8:80:3B:D1:02:20:35:B9:87:39:D8:12:35:B7:91:
  • 29:4C:E1:5F:43:3E:3C:B7:6C:CE:2F:93:E6:79:D5:35:
  • 3C:3A:72:A4:FF:82:D7
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Jan 15 04:36:10.279 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:82:48:9F:CB:92:60:2A:FD:74:BD:B5:
  • DD:45:86:14:A7:67:57:37:87:A3:94:FE:94:D9:EE:2A:
  • BB:4D:58:26:9F:02:20:30:78:37:24:AF:4A:95:CC:22:
  • B8:9C:5F:DB:8C:D8:5A:7E:E6:03:EB:E6:59:FA:E5:F4:
  • C1:5C:AC:1F:B2:A7:3D

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