SSL check results of cock.email

NEW You can also bulk check multiple servers.

Discover if the mail servers for cock.email 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 Sun, 29 Jun 2025 00:30:11 +0000

We can not guarantee a secure connection to the mailservers of cock.email!

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

/mailservers/cock.email

Servers

Incoming Mails

These servers are responsible for incoming mails to @cock.email addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mx1.cock.li
2001:ac8:7d:1e::c0cc:4
10
supported
mx1.cock.li
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
10 s
mx1.cock.li
37.120.193.125
10
supported
mx1.cock.li
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
4 s
mx2.cock.li
2001:ac8:7d:1e::c0cc:2
Results incomplete
20 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mx2.cock.li
37.120.193.123
Results incomplete
20
unsupported
not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
4 s

Outgoing Mails

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

Certificates

First seen at:

CN=mx1.cock.li

Certificate chain
  • mx1.cock.li
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption

      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • mx1.cock.li
Alternative Names
  • mx1.cock.li
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-05-18
Not valid after
2025-08-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
8E:6A:75:30:4D:1E:70:C3:2A:88:BC:7D:75:6B:91:F2:F2:BC:D4:EF:2B:47:68:14:B4:5C:C4:B1:EE:66:C5:C8
SHA1
58:2D:45:04:32:8B:DF:73:60:26:34:DA:8A:1D:E2:5D:EB:CC:E4:2E
X509v3 extensions
subjectKeyIdentifier
  • BB:5E:33:68:B8:F2:D8:AB:16:A4:66:02:F1:72:2E:C8:56:7C:F7:54
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/69.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A4:42:C5:06:49:60:61:54:8F:0F:D4:EA:9C:FB:7A:2D:
  • 26:45:4D:87:A9:7F:2F:DF:45:59:F6:27:4F:3A:84:54
  • Timestamp : May 18 16:56:47.150 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:85:E5:05:45:3A:18:24:F2:B0:0C:FE:
  • D5:FC:C2:DB:81:26:B5:0B:68:F7:EF:DA:E7:C2:14:6A:
  • 6F:E1:94:8B:A1:02:21:00:87:98:A9:84:7A:F7:EF:44:
  • 7C:C5:28:C6:00:D0:D6:2B:E8:8E:32:1D:8D:2A:28:FD:
  • 77:CC:2B:0A:A3:C7:C3:4B
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 0D:E1:F2:30:2B:D3:0D:C1:40:62:12:09:EA:55:2E:FC:
  • 47:74:7C:B1:D7:E9:30:EF:0E:42:1E:B4:7E:4E:AA:34
  • Timestamp : May 18 16:56:49.150 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:92:B7:71:04:C1:5C:D2:3D:1E:55:3D:
  • 46:E4:B4:6A:0B:22:D8:AD:0A:74:D8:52:B7:4A:3C:90:
  • C3:F9:ED:90:01:02:21:00:D1:B5:75:67:1F:D4:2B:D0:
  • CC:DA:E9:CF:04:4C:62:4E:6F:DC:C3:68:6C:CB:34:24:
  • 35:27:C5:91:9C:0E:5C:D6