SSL check results of catsarebeautiful.de

NEW You can also bulk check multiple servers.

Discover if the mail servers for catsarebeautiful.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 Mon, 23 Sep 2024 00:30:39 +0000

We can not guarantee a secure connection to the mailservers of catsarebeautiful.de!

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

/mailservers/catsarebeautiful.de

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.catsarebeautiful.de
2a01:4f8:c012:62b0::1
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
mail.catsarebeautiful.de
138.201.244.50
10
supported
admin.catsarebeautiful.de
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
1 s

Outgoing Mails

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

Certificates

First seen at:

CN=admin.catsarebeautiful.de

Certificate chain
  • admin.catsarebeautiful.de
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
    • Hostname Mismatch

      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption

Subject
Common Name (CN)
  • admin.catsarebeautiful.de
Alternative Names
  • admin.catsarebeautiful.de
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2024-09-17
Not valid after
2024-12-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
1E:3D:76:0D:2A:EB:29:AA:C2:6C:5C:E2:D8:2A:EA:75:30:38:79:88:50:C4:58:E8:DD:B7:F8:68:28:80:48:F2
SHA1
8A:49:95:74:B8:B5:F7:24:08:1A:88:21:58:E9:AD:87:5E:5A:5B:F7
X509v3 extensions
subjectKeyIdentifier
  • 46:00:35:69:DE:8D:4C:EE:85:ED:BE:D3:E0:03:C9:23:36:74:D7:02
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : EE:CD:D0:64:D5:DB:1A:CE:C5:5C:B7:9D:B4:CD:13:A2:
  • 32:87:46:7C:BC:EC:DE:C3:51:48:59:46:71:1F:B5:9B
  • Timestamp : Sep 17 18:17:33.457 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:F6:74:F0:DC:85:A3:6A:AB:C2:00:28:
  • 8F:9A:65:E4:0E:AA:AB:C0:6D:39:9B:13:4A:8C:18:8A:
  • A9:12:08:81:7C:02:21:00:A4:FB:09:3C:73:7D:84:63:
  • DD:B5:EC:24:6A:A4:42:AF:A8:0F:07:30:5B:F2:23:3A:
  • 19:FD:BF:44:59:E0:C5:18
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Sep 17 18:17:33.472 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B9:CD:19:3B:31:CE:98:7C:6F:B0:A1:
  • 80:CB:34:D5:EC:75:8E:52:A5:C6:C1:1B:95:C7:F8:55:
  • A5:6B:BF:F6:0B:02:21:00:A6:E8:8F:61:7F:2A:9A:E9:
  • F9:13:5E:CB:01:D0:22:E7:C5:9E:B9:18:41:49:6A:FA:
  • 0A:A2:DD:B7:8E:FA:81:C8