SSL check results of calloyd.net

NEW You can also bulk check multiple servers.

Discover if the mail servers for calloyd.net 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 Wed, 17 Apr 2024 18:13:13 +0000

The mailservers of calloyd.net can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @calloyd.net addresses.

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

Certificates

First seen at:

CN=mail.calloyd.net

Certificate chain
  • mail.calloyd.net
    • remaining
    • 384 bit
    • sha256WithRSAEncryption

      • R3
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption

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

Subject
Common Name (CN)
  • mail.calloyd.net
Alternative Names
  • mail.calloyd.net
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R3
validity period
Not valid before
2024-02-09
Not valid after
2024-05-09
This certifcate has been verified for the following usages:
  • Digital Signature
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
F8:07:68:C9:64:50:E7:91:0E:61:9E:E1:00:83:0C:31:47:8E:20:07:C9:4F:DA:E8:0A:0C:48:6A:92:75:CA:EF
SHA1
C9:5D:7D:FB:BD:14:94:E5:0F:DD:18:9B:05:27:98:65:0E:F6:AA:DE
X509v3 extensions
subjectKeyIdentifier
  • D6:ED:3F:55:75:BE:27:66:16:6A:D1:D8:23:64:F6:73:EF:0C:EF:B1
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 : Feb 9 11:06:31.206 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:03:45:A5:67:39:3E:22:E9:13:2E:3B:05:
  • 62:81:AA:A3:83:0A:CF:33:F3:3B:88:02:6F:6A:AF:B5:
  • 01:9A:F1:19:02:21:00:9D:72:C6:69:42:0C:78:54:F6:
  • B1:DB:2E:A2:E2:6C:EE:15:37:3D:CD:3B:89:BF:18:75:
  • 9D:63:7A:35:B3:0A:51
  • 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 : Feb 9 11:06:31.199 2024 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:85:15:A0:5D:2D:74:D0:85:6C:30:CD:
  • 69:28:40:C9:AF:88:F9:2E:9E:DA:4B:30:3A:11:D5:BA:
  • CD:3F:9A:E5:13:02:21:00:83:00:1A:D3:81:2F:C2:E0:
  • 59:37:29:DA:49:14:67:72:E8:15:D7:FB:64:40:2D:25:
  • 95:32:6E:E2:E5:44:01:2A