SSL-Tools

SSL check results of joyeriabonilla.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for joyeriabonilla.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 Tue, 23 Apr 2024 13:22:33 +0000

The mailservers of joyeriabonilla.com can be reached through a secure connection.

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.joyeriabonilla.com
178.238.235.191
 10
supported
mail.joyeriabonilla.com
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 @joyeriabonilla.com address so far. Test mail delivery

Certificates

First seen at:

CN=mail.joyeriabonilla.com

Certificate chain
  • mail.joyeriabonilla.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.joyeriabonilla.com
Alternative Names
  • admin.mail.joyeriabonilla.com
  • mail.joyeriabonilla.com
  • mail.mail.joyeriabonilla.com
  • webmail.mail.joyeriabonilla.com
  • www.mail.joyeriabonilla.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-03-16
Not valid after
2024-06-14
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
94:71:E1:03:0D:C0:7F:D4:8A:09:5E:4D:7E:2F:4F:65:AA:EC:D0:79:E5:06:96:80:91:CF:A4:07:C8:A2:62:48
SHA1
9A:00:30:15:15:B5:0A:38:54:1E:AB:3B:D3:C8:DC:68:2E:CE:10:CA
X509v3 extensions
subjectKeyIdentifier
  • 16:57:A2:65:39:2D:6F:C8:D6:05:1D:68:60:5D:67:CC:50:7F:D9:11
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
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : A2:E2:BF:D6:1E:DE:2F:2F:07:A0:D6:4E:6D:37:A7:DC:
  • 65:43:B0:C6:B5:2E:A2:DA:B7:8A:F8:9A:6D:F5:17:D8
  • Timestamp : Mar 16 01:45:28.455 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:7A:BE:41:E7:06:97:0E:EF:AD:0C:E9:88:
  • 7C:DC:74:92:B5:8F:B3:23:82:3D:56:E1:DE:17:DB:A7:
  • BB:02:AF:7A:02:21:00:CB:35:90:FC:98:F3:E6:4F:56:
  • 41:11:0D:F2:6E:56:B7:A9:12:F6:A6:B3:C1:FB:AE:28:
  • 4B:7E:2B:3E:47:9F:CB
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 3B:53:77:75:3E:2D:B9:80:4E:8B:30:5B:06:FE:40:3B:
  • 67:D8:4F:C3:F4:C7:BD:00:0D:2D:72:6F:E1:FA:D4:17
  • Timestamp : Mar 16 01:45:28.429 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:2E:D3:EF:78:1E:0E:F7:01:DF:0B:49:D4:
  • 63:07:A5:6C:8A:D5:B5:D5:1E:88:6E:23:59:BB:61:6D:
  • A6:8B:E6:AD:02:21:00:C3:CA:A5:FF:5A:3A:F5:56:26:
  • 3E:BE:E3:43:FB:86:62:D2:4C:2F:11:19:F0:CF:CB:5A:
  • 97:0B:B3:BB:AF:D7:DC