SSL-Tools

SSL check results of littlewishes.info

NEW You can also bulk check multiple servers.

Discover if the mail servers for littlewishes.info 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 Mon, 16 May 2022 05:30:48 +0000

The mailservers of littlewishes.info can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @littlewishes.info addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.littlewishes.info
162.241.252.227
 0
supported
webdisk.littlewishes.info
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
43 s

Outgoing Mails

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

Certificates

First seen at:

CN=webdisk.littlewishes.info

Certificate chain
  • webdisk.littlewishes.info
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • webdisk.littlewishes.info
Alternative Names
  • autodiscover.littlewishes.info
  • cpanel.littlewishes.info
  • cpcalendars.littlewishes.info
  • cpcontacts.littlewishes.info
  • littlewishes.info
  • mail.littlewishes.info
  • webdisk.littlewishes.info
  • webmail.littlewishes.info
  • www.littlewishes.info
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2022-04-04
Not valid after
2022-07-03
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
BD:F2:6B:6E:3E:48:85:7D:4D:37:D4:A2:A0:72:77:EB:32:95:E2:6D:0F:C2:1F:CF:79:58:28:23:00:4E:18:DD
SHA1
2F:E9:8C:F6:47:DC:11:AA:F7:09:2A:5C:42:44:2F:64:AA:A4:C8:FD
X509v3 extensions
subjectKeyIdentifier
  • 89:23:0F:97:62:F9:EF:6A:8E:55:32:C8:93:E5:25:A6:A1:0A:A3:43
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 : 46:A5:55:EB:75:FA:91:20:30:B5:A2:89:69:F4:F3:7D:
  • 11:2C:41:74:BE:FD:49:B8:85:AB:F2:FC:70:FE:6D:47
  • Timestamp : Apr 4 09:05:29.305 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:C1:DC:AB:12:C1:21:35:70:9A:5F:4D:
  • F2:B5:F7:66:21:EE:23:91:E4:2D:15:C2:A2:F1:DF:C6:
  • 40:0A:E0:A6:E5:02:21:00:99:42:23:65:7C:83:EB:42:
  • A7:8E:8B:F5:72:35:37:2A:22:10:34:4A:68:AF:F6:97:
  • BD:B4:52:C6:A7:C2:38:E0
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 6F:53:76:AC:31:F0:31:19:D8:99:00:A4:51:15:FF:77:
  • 15:1C:11:D9:02:C1:00:29:06:8D:B2:08:9A:37:D9:13
  • Timestamp : Apr 4 09:05:29.528 2022 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:E1:74:10:55:20:37:B0:03:25:89:1B:
  • 13:3A:0C:5F:3A:B4:FA:F1:3C:24:8E:6F:8D:3C:D3:B8:
  • B6:7A:FF:A1:53:02:21:00:A9:8C:D9:93:BF:27:1D:1B:
  • 76:16:32:AF:94:B5:63:D2:79:03:5E:7D:95:8F:BE:9A:
  • 00:3C:53:29:22:11:94:62