A valid certificate must cover the hostname visitors use and be installed on the server that receives their request.
What to check
- Check the certificate name and expiration
- Confirm DNS points to the intended server
- Find HTTP assets and conflicting redirects
What the results mean
Check expiration, DNS, and redirects together. Mixed HTTP assets can still trigger browser warnings after the main certificate is fixed.
Read the specific browser warning
An expired certificate, a certificate issued for another name, and mixed HTTP content need different fixes. Check the exact domain in the address bar, including www, and confirm which server answers that name. If DNS points to the wrong destination, renewing a certificate on the intended host may not fix what visitors actually receive.
Test the complete secure path
After correcting issuance or installation, test the root domain, www, important subpages, and the site's HTTP to HTTPS redirects. Inspect images, scripts, forms, and embedded content for insecure requests. Prevent multiple redirect rules from sending visitors between addresses in a loop.
Is it safe to ignore the warning temporarily?
No. Visitors may leave or avoid submitting information. Work from a trusted account connection to verify the certificate and routing, and do not ask customers to click through a browser warning.
Greg Grigorian
For hosting trouble, migrations, backups, or a site that stopped working, get a clear diagnosis and a tested recovery path. Greg can review the setup and handle the work.