SSL-Tools

SSL check results of jacoboily.info

NEW You can also bulk check multiple servers.

Discover if the mail servers for jacoboily.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 Thu, 18 Apr 2024 12:11:14 +0000

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

Servers

Incoming Mails

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

Hostname / IP address Priority STARTTLS Certificates Protocol
jacoboily.info
2604:a880:cad:d0::c2d:8001
 10
supported
jacoboily.info
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s
jacoboily.info
137.184.162.190
 10
supported
jacoboily.info
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
5 s

Outgoing Mails

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

Certificates

First seen at:

CN=jacoboily.info

Certificate chain
  • jacoboily.info
    • remaining
    • 384 bit
    • sha256WithRSAEncryption
      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • jacoboily.info
Alternative Names
  • jacoboily.info
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-04-17
Not valid after
2024-07-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
6F:55:E2:C9:88:48:51:31:2D:30:FD:8E:68:85:D3:5F:9C:80:5F:B6:B2:C6:2D:25:60:FC:6E:1E:B6:FB:40:87
SHA1
30:32:09:9C:C9:3C:78:F6:B7:50:88:73:B4:12:B0:F9:F0:B2:26:B8
X509v3 extensions
subjectKeyIdentifier
  • 0F:AF:A6:F8:D1:20:D5:96:A6:9F:70:5F:CC:4F:53:1D:D5:21:BE:88
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 : 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 : Apr 17 08:59:07.456 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:5C:9B:B3:82:BE:68:DB:01:86:42:15:D4:
  • 1A:71:8E:7D:21:58:AD:D9:27:AA:26:C3:31:56:0D:D5:
  • 7E:F6:61:73:02:20:4A:CD:9B:A6:D4:85:D8:77:A2:F4:
  • 32:63:1A:B4:21:AD:66:A7:E9:34:7E:F2:DB:D3:A5:14:
  • 2A:0A:F6:B4:CE:38
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 19:98:10:71:09:F0:D6:52:2E:30:80:D2:9E:3F:64:BB:
  • 83:6E:28:CC:F9:0F:52:8E:EE:DF:CE:4A:3F:16:B4:CA
  • Timestamp : Apr 17 08:59:07.471 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:2C:58:F5:44:B0:16:E0:A5:E1:61:B6:11:
  • A9:39:33:D9:21:56:78:80:82:8B:8F:17:77:D3:10:B4:
  • 6E:A6:CF:5A:02:20:47:CE:21:7B:16:4C:65:04:D4:DB:
  • F8:23:2E:D3:4B:46:57:DC:15:90:EE:7A:69:C3:7F:73:
  • BD:5F:F5:42:51:0B
tlsfeature
  • status_request