SSL-Tools

SSL check results of coach-circle.com

NEW You can also bulk check multiple servers.

Discover if the mail servers for coach-circle.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 Fri, 15 Aug 2025 07:57:52 +0000

The mailservers of coach-circle.com can be reached through a secure connection.

Servers

Incoming Mails

These servers are responsible for incoming mails to @coach-circle.com addresses.

Hostname / IP address Priority STARTTLS Certificates Protocol
srv1.estroh.com
2001:41d0:8:d407::1
 1
supported
srv1.estroh.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s
srv1.estroh.com
5.135.154.7
 1
supported
srv1.estroh.com
DANE
valid
PFS
supported
Heartbleed
not vulnerable
Weak ciphers
not found
  • TLSv1.2
  • TLSv1.1
  • TLSv1.0
  • SSLv3
8 s

Outgoing Mails

We have not received any emails from a @coach-circle.com address so far. Test mail delivery

Certificates

First seen at:

CN=srv1.estroh.com

Certificate chain
  • srv1.estroh.com
    • remaining
    • 2048 bit
    • sha256WithRSAEncryption
      • R11
        • remaining
        • 2048 bit
        • sha256WithRSAEncryption
          • ISRG Root X1 (Certificate is self-signed.)
            • remaining
            • 4096 bit
            • sha256WithRSAEncryption
Subject
Common Name (CN)
  • srv1.estroh.com
Alternative Names
  • srv1.estroh.com
Issuer
Country (C)
  • US
Organization (O)
  • Let's Encrypt
Common Name (CN)
  • R11
validity period
Not valid before
2025-08-10
Not valid after
2025-11-08
This certifcate has been verified for the following usages:
  • Digital Signature
  • Key Encipherment
  • TLS Web Server Authentication
  • TLS Web Client Authentication
Fingerprints
SHA256
AF:83:8D:97:CA:49:01:0B:CF:6C:11:99:B3:FC:E1:23:1B:B3:29:19:26:F1:F2:1F:05:00:4D:28:AA:35:AF:57
SHA1
8B:78:11:33:66:F3:E1:90:02:15:5C:3D:C8:D5:FE:F4:64:8D:BB:AE
X509v3 extensions
subjectKeyIdentifier
  • FB:27:F5:9A:D0:DD:0C:51:73:1A:64:29:83:46:14:35:C1:50:5B:68
authorityKeyIdentifier
  • keyid:C5:CF:46:A4:EA:F4:C3:C0:7A:6C:95:C4:2D:B0:5E:92:2F:26:E3:B9
authorityInfoAccess
  • CA Issuers - URI:http://r11.i.lencr.org/
certificatePolicies
  • Policy: 2.23.140.1.2.1
crlDistributionPoints
  • Full Name:
  • URI:http://r11.c.lencr.org/16.crl
ct_precert_scts
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : CC:FB:0F:6A:85:71:09:65:FE:95:9B:53:CE:E9:B2:7C:
  • 22:E9:85:5C:0D:97:8D:B6:A9:7E:54:C0:FE:4C:0D:B0
  • Timestamp : Aug 10 11:18:34.989 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:44:02:20:6C:99:3B:72:8F:3C:B5:20:F6:18:1A:EF:
  • 20:C4:A7:5F:C2:0C:55:BD:39:59:D1:82:7B:13:7E:72:
  • 9A:F4:44:CF:02:20:54:37:4C:A8:43:CC:09:68:F5:25:
  • 4A:EC:37:4C:F5:C2:CE:40:FA:CE:E8:E3:F5:7B:8F:50:
  • 69:52:2C:F0:AB:C6
  • Signed Certificate Timestamp:
  • Version : v1 (0x0)
  • Log ID : DD:DC:CA:34:95:D7:E1:16:05:E7:95:32:FA:C7:9F:F8:
  • 3D:1C:50:DF:DB:00:3A:14:12:76:0A:2C:AC:BB:C8:2A
  • Timestamp : Aug 10 11:18:35.049 2025 GMT
  • Extensions: none
  • Signature : ecdsa-with-SHA256
  • 30:46:02:21:00:B8:78:BA:95:08:EE:16:69:8E:7A:FC:
  • 8C:08:A9:E9:A9:A3:3C:FB:FD:68:92:81:2D:06:E0:B0:
  • 7D:FC:79:09:D6:02:21:00:FE:FD:DF:D6:13:A6:43:C2:
  • A2:87:F1:3F:29:F7:EC:96:D0:70:D5:9E:7A:3B:DE:75:
  • 50:3C:3C:90:88:F2:A0:8D

DANE

DNS-based Authentication of Named Entities (DANE) is a protocol to allow X.509 certificates to be bound to DNS using TLSA records and DNSSEC.

Name Options DNSSEC Matches
_25._tcp.srv1.estroh.com
  • DANE-TA: Trust Anchor Assertion
  • Use subject public key
  • SHA-256 Hash
valid
valid