SSL-Tools

SSL check results of seybold.cc

NEW You can also bulk check multiple servers.

Discover if the mail servers for seybold.cc 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, 15 Feb 2025 18:29:27 +0000

The mailservers of seybold.cc can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @seybold.cc addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
mail.seybold.cc
77.24.36.81
 10
supported
mail.seybold.cc
DANE
missing
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • SSLv3
8 s

Outgoing Mails

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

Certificates

First seen at:

CN=mail.seybold.cc

Certificate chain
  • mail.seybold.cc
    • remaining
    • 4096 bit
    • sha256WithRSAEncryption
      • R10
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • mail.seybold.cc
Alternative Names
  • autoconfig.seybold.cc
  • autodiscover.seybold.cc
  • mail.seybold.cc
  • mta-sts.seybold.cc
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R10
validity period
Not valid before
2025-02-15
Not valid after
2025-05-16
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
19:87:F2:F2:9E:4A:36:77:83:C8:85:D1:7B:06:B7:52:62:0C:C0:F6:C9:B4:A8:AC:1A:FC:AC:31:06:34:E7:DB
SHA1
4D:DA:4D:69:E7:A9:A1:C5:A1:57:4F:F4:32:DD:57:E6:BE:1C:E0:69
X509v3 extensions
subjectKeyIdentifier
  • E7:D5:6C:EA:11:19:C8:20:06:F7:9D:AB:93:D3:AF:95:61:F2:94:AD
authorityKeyIdentifier
  • keyid:BB:BC:C3:47:A5:E4:BC:A9:C6:C3:A4:72:0C:10:8D:A2:35:E1:C8:E8
authorityInfoAccess
  • OCSP - URI:http://r10.o.lencr.org
  • CA Issuers - URI:http://r10.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : 7D:59:1E:12:E1:78:2A:7B:1C:61:67:7C:5E:FD:F8:D0:
  • 87:5C:14:A0:4E:95:9E:B9:03:2F:D9:0E:8C:2E:79:B8
  • Timestamp : Feb 15 10:27:41.322 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:03:98:C8:83:25:47:4C:C1:47:4E:F5:38:
  • E8:63:3A:0F:46:96:B2:A6:67:80:96:59:E2:65:94:19:
  • 31:77:59:27:02:21:00:E7:25:8B:25:EA:91:06:6A:CF:
  • CE:B0:6B:D6:D3:34:D3:F7:81:3F:4F:3A:0D:1D:AD:EC:
  • C0:96:35:16:46:FF:AF
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : E0:92:B3:FC:0C:1D:C8:E7:68:36:1F:DE:61:B9:96:4D:
  • 0A:52:78:19:8A:72:D6:72:C4:B0:4D:A5:6D:6F:54:04
  • Timestamp : Feb 15 10:27:41.516 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:45:02:20:31:C5:BB:8E:27:36:86:66:09:12:7B:0E:
  • C6:36:E8:E3:0F:9F:81:EF:BD:34:9D:5B:77:F7:6D:2A:
  • 0F:B3:39:DC:02:21:00:EB:C8:3F:5A:CA:91:71:4C:E5:
  • BC:55:67:28:A4:EC:22:3C:17:65:6D:CD:9A:CF:C0:20:
  • AE:9D:D7:76:D6:DC:20