Report an HTTPS or certificate warning
Capture the exact warning and keep credentials out of an untrusted connection.
Stop before entering sensitive information
If your browser warns that a connection is not private or the certificate is invalid, record the warning before proceeding. Do not enter account credentials, payment details, or customer information on that connection while its identity is in doubt.
Collect the useful details
- The exact HTTPS hostname you opened.
- The browser's error code or warning text.
- The date and time shown on your device.
- Whether the warning affects another device or connection.
- Whether the issue started after a domain, hosting, or certificate change.
A certificate for one hostname may not cover a different hostname. Redirecting users to an IP address can also produce a mismatch even when the intended website has a valid certificate.
Avoid broad workarounds
Do not disable browser certificate validation or ask all employees to ignore the warning. An administrator should investigate the served certificate, hostname, chain, and routing path. A valid certificate configured at a distribution does not automatically confirm every origin or redirect is correct.
Verify the repair
Reopen the intended HTTPS address and confirm that the final hostname is correct and the warning is gone. Report any remaining device-specific behavior on the same ticket, including whether an older redirect is still being followed.
Include this guide and what you tried in your ticket so we can pick up from there.
Contact support