The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to test if your domain supports TLS with the Cisco Registered Envelope Service (CRES).
How do I test if my domain supports TLS with CRES?
Note: You will need a CRES administrator account pre-configured to perform the following steps.
If you believe the SSL cert supporting your domain is correct, as the CRES Account Admin, you can log into the CRES server and run a diagnostic check to see if there is a TLS connection between the CRES server and your domain:
Then click on the account number listed at the bottom that pertains to your company.
After clicking the account number, you should be presented with a new set of sub-tabs.
Select the sub-tab called "Features". Enter in your domain (e.g. example.com) and then click on "Test Domain".
Depending on the results, if the results show that your domain supports TLS, then click on "Add domain" and the CRES Admin team will review the submission and notify you when your domain has been added to the CRES TLS supported domains.
If there is any failure, the results will also display the cause of the failure. Address the problem and then re-do the test.
Another option you have is to configure how the CRES server handles TLS connection failures. Click on the "Details" sub-tab and you should be presented with this option:
On TLS failure choose one of the following delivery preferences: - Fallback to Registered Envelope Delivery - Bounce Messages