SSL check results of capocasa.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for capocasa.net 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 Sat, 26 Apr 2025 07:16:47 +0000

We can not guarantee a secure connection to the mailservers of capocasa.net!

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

/mailservers/capocasa.net

Servers

Incoming Mails

These servers are responsible for incoming mails to @capocasa.net addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
capocasa.net
2a01:4f9:6b:47c1::1
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
1 s
capocasa.net
65.108.71.196
10
supported
capocasa.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
3 s
capocasa.net.capocasa.net
65.108.71.196
10
supported
capocasa.net
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
2 s

Outgoing Mails

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

Certificates

First seen at:

CN=capocasa.net

Certificate chain
  • capocasa.net
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • capocasa.net
Alternative Names
  • *.capocasa.net
  • capocasa.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-03-07
Not valid after
2025-06-05
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
CB:F3:39:CE:17:7F:84:A9:2F:2C:60:02:E9:3B:E2:B2:A0:0F:93:96:70:A0:6D:4D:E4:28:8F:0A:C1:90:B7:4C
SHA1
B1:57:79:FF:3C:59:06:E2:70:7D:E6:9B:40:F3:40:36:39:DF:1F:94
X509v3 extensions
subjectKeyIdentifier
  • 7D:8E:21:49:AB:D5:CD:9F:5A:62:F2:9B:FC:A8:11:FB:54:87:B6:22
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • OCSP - URI:http://r11.o.lencr.org
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E3:0A:E4:45:EF:BD:AD:9B:7E:38:ED:47:67:77:53:
  • D7:82:5B:84:94:D7:2B:5E:1B:2C:C4:B9:50:A4:47:E7
  • Timestamp : Mar 7 02:02:01.170 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E1:66:A7:4C:01:5D:12:8B:BC:3A:27:
  • C1:65:25:E7:9D:B0:16:1D:74:4D:CD:00:D2:FE:FF:EC:
  • C0:14:D7:28:FC:02:21:00:CD:4E:89:1F:9E:5C:CF:68:
  • 6D:F9:6D:C0:A4:4F:13:54:D2:BA:83:66:5C:54:41:27:
  • 96:00:FA:B6:5C:1A:90:A9
  • 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 : Mar 7 02:02:01.192 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:8B:28:45:97:0D:F5:8E:5C:9E:16:7A:
  • ED:9E:D7:D5:15:24:A6:B2:C5:05:EC:FA:20:1B:51:3A:
  • C1:FD:A2:9C:A2:02:20:0E:74:62:89:7E:77:B5:7E:50:
  • 37:BC:BD:D8:98:1B:EC:14:D9:09:F4:28:E9:7E:A8:44:
  • 35:27:27:B3:93:3C:3E