SSL-Tools

SSL check results of devmoon.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for devmoon.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, 25 May 2025 00:32:32 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mailcow-01.rz.devmoon.de
2001:1b60:3:35:8913::104
 10
supported
mailcow-01.rz.devmoon.de
DANE
errors
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
9 s
mailcow-01.rz.devmoon.de
87.118.87.110
 10
supported
mailcow-01.rz.devmoon.de
DANE
errors
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
6 s

Outgoing Mails

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

Certificates

First seen at:

CN=mailcow-01.rz.devmoon.de

Certificate chain
  • mailcow-01.rz.devmoon.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mailcow-01.rz.devmoon.de
Alternative Names
  • mailcow-01.rz.devmoon.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-05-09
Not valid after
2025-08-07
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
CF:20:EB:F1:26:0A:18:34:E6:6A:B3:79:3D:3D:86:57:BC:A7:1E:23:78:61:D8:47:5B:B4:5F:58:05:DB:56:C8
SHA1
B2:07:F0:58:6E:E6:49:2C:B7:4C:EE:E2:AC:73:94:48:BF:A4:49:C8
X509v3 extensions
subjectKeyIdentifier
  • 32:00:FE:E3:05:A9:37:23:9C:51:55:64:C7:C3:69:40:52:80:92:F6
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/106.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 : May 9 06:23:27.654 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D7:94:28:1E:AD:60:19:33:1F:AE:3A:
  • 71:43:96:4D:F4:C4:3F:A4:18:92:7D:C9:F4:AD:CD:D8:
  • 9E:0C:74:FA:AF:02:20:23:6F:FF:A6:ED:9F:05:49:A8:
  • F0:84:3B:2A:31:33:9B:D9:81:B6:3D:79:59:29:1F:DF:
  • 6F:24:6B:6A:9B:F4:94
  • 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 : May 9 06:23:27.656 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7C:2D:51:77:4A:10:7B:B3:23:11:41:DF:
  • 4E:A6:9B:52:F9:62:65:7C:2B:92:62:31:B0:17:3F:CB:
  • 85:A8:7E:3E:02:21:00:C0:FE:04:C1:7D:E3:CA:43:4E:
  • 09:B8:74:61:33:84:B6:D8:C2:F3:93:D8:1F:7C:AD:1E:
  • C4:E0:C6:DE:08:6B:70

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.mailcow-01.rz.devmoon.de
  • DANE-EE: Domain Issued Certificate
  • Use subject public key
  • SHA-256 Hash
error
Debug
—