SSL-Tools

SSL check results of codesandpixels.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for codesandpixels.com 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 Sat, 09 Aug 2025 13:52:29 +0000

We can not guarantee a secure connection to the mailservers of codesandpixels.com!

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

/mailservers/codesandpixels.com

Servers

Incoming Mails

These servers are responsible for incoming mails to @codesandpixels.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
codesandpixels.com
95.179.245.162
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
codesandpixels.com
192.248.191.135
Results incomplete
10 not checked
DANE
missing
PFS
not checked
Heartbleed
not checked
Weak ciphers
not checked
11 s
mail.codesandpixels.com
74.208.46.156
 10
supported
mail.codesandpixels.com
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.codesandpixels.com

Certificate chain
Subject
Common Name (CN)
  • mail.codesandpixels.com
Alternative Names
  • mail.codesandpixels.com
Issuer
Country (C)
  • US
Organization (O)
  • (STAGING) Let's Encrypt
Common Name (CN)
  • (STAGING) Wannabe Watercress R11
validity period
Not valid before
2025-07-23
Not valid after
2025-10-21
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
EF:90:25:52:FA:1C:8E:B7:9B:16:CE:29:AE:0D:5C:CB:18:86:6E:B3:BF:B1:3F:0D:EB:1F:F4:5F:6F:5F:53:6B
SHA1
C3:97:8B:87:A8:27:2D:A9:7C:F0:C0:2B:1A:F7:D2:B6:1B:E2:57:D3
X509v3 extensions
subjectKeyIdentifier
  • 39:C4:C4:E7:3F:DE:B5:FA:4D:B7:12:6E:F6:D6:17:8C:C4:E8:92:E4
authorityKeyIdentifier
  • keyid:13:CB:D7:F6:AE:9D:FC:69:42:64:D6:5C:7C:23:CC:85:F9:47:C7:B6
authorityInfoAccess
  • CA Issuers - URI:http://stg-r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://stg-r11.c.lencr.org/120.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 28:76:1A:18:90:27:FB:EF:3C:D0:D6:1A:01:8D:76:B0:
  • 50:57:29:C7:A7:41:1B:CC:BD:F6:04:F4:5D:42:61:53
  • Timestamp : Jul 23 16:06:55.163 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:63:09:6D:1A:03:9C:DC:32:FE:23:AC:90:
  • B6:0E:DC:B5:16:37:06:06:78:35:88:5D:10:4E:EB:0F:
  • DC:59:94:0C:02:21:00:A5:B0:22:70:DE:DA:FE:6A:FC:
  • FC:F2:2C:1E:A2:48:A6:C5:25:70:6F:58:40:67:BE:40:
  • E3:5D:4B:C1:AE:48:FE
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : B0:CC:83:E5:A5:F9:7D:6B:AF:7C:09:CC:28:49:04:87:
  • 2A:C7:E8:8B:13:2C:63:50:B7:C6:FD:26:E1:6C:6C:77
  • Timestamp : Jul 23 16:06:57.134 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:21:00:D7:6C:29:96:8A:53:11:15:C4:E0:CA:
  • AD:1A:53:95:5E:C9:CE:91:52:DD:BF:53:1A:3B:06:0D:
  • 33:24:2D:E8:E3:02:20:4F:34:28:33:01:45:D5:64:24:
  • 95:E1:73:B6:76:37:57:F0:14:68:FF:0E:86:89:6B:E7:
  • F8:A0:32:5A:55:9F:33