SSL check results of codelunatix.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for codelunatix.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

Report created Tue, 23 Feb 2021 13:58:58 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.codelunatix.de
2a03:4000:53:15a::1
10
supported
codelunatix.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s
mail.codelunatix.de
202.61.246.162
10
supported
codelunatix.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=codelunatix.de

Certificate chain
  • codelunatix.de
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • DST Root CA X3 (Certificate is self-signed.)
            • remaining
            • 2048 bit
            • sha1WithRSAEncryption

Subject
Common Name (CN)
  • codelunatix.de
Alternative Names
  • *.codelunatix.de
  • codelunatix.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2021-02-23
Not valid after
2021-05-24
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
25:88:3E:3B:DD:FC:15:4B:76:2C:94:8E:96:5C:8C:D5:30:E7:24:9F:EB:6C:D6:0A:4B:86:A2:64:15:18:15:F5
SHA1
35:09:96:4D:78:16:EF:50:A4:56:C0:01:CE:64:D0:C5:03:F0:57:EE
X509v3 extensions
subjectKeyIdentifier
  • E3:3C:08:5F:D8:EE:1A:D1:F4:21:BE:5E:F1:AC:A7:17:A1:2C:A2:CC
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
  • Policy: 1.3.6.1.4.1.44947.1.1.1
  • CPS: http://cps.letsencrypt.org
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
  • D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
  • Timestamp : Feb 23 10:27:26.234 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6F:E0:58:A4:DA:79:7A:EB:27:33:6B:82:
  • 89:C0:2D:C1:A6:F2:89:D0:4B:BC:E2:D9:FC:3C:CF:36:
  • F9:95:59:C1:02:20:29:9A:BE:2A:8E:40:B9:0B:60:9A:
  • 15:0B:A5:74:61:CC:9D:21:0F:1B:61:C0:BC:01:13:B7:
  • C8:64:23:EC:1D:2A
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : F6:5C:94:2F:D1:77:30:22:14:54:18:08:30:94:56:8E:
  • E3:4D:13:19:33:BF:DF:0C:2F:20:0B:CC:4E:F1:64:E3
  • Timestamp : Feb 23 10:27:26.227 2021 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:98:5B:C5:D9:98:FA:E9:80:0D:69:F3:
  • 50:60:DC:18:3B:A4:60:DE:A4:C9:4B:32:20:38:66:F5:
  • 50:C7:33:C3:00:02:20:4A:F4:48:4E:85:CC:A6:71:83:
  • 19:4A:1B:FA:CE:FD:DA:F3:4B:B5:E0:5B:17:CE:2C:72:
  • 0B:E7:F3:0C:89:37:D1