Find why your HTTPS certificate isn't working, from bad DNS to Cloudflare SSL modes or CAA records, and get the padlock back.
My site says Not Secure or shows a certificate error, fix the SSL
How it works
- Read the exact browser error: Vovy opens your site and reads the error, like NET::ERR_CERT_COMMON_NAME_INVALID or ERR_TOO_MANY_REDIRECTS. Each points to a different cause.
- Check the certificate status at your host: Vovy opens your host's domain page to see if the certificate is issued, pending, or failing because DNS points somewhere else.
- Check Cloudflare SSL mode and CAA: Flexible mode often causes redirect loops. CAA records can block your host from issuing certificates. Vovy checks both in Cloudflare.
- Apply the fix: Vovy explains the fix in one card, asks, then makes it, such as setting SSL mode to Full (strict) or correcting the A record.
- Find mixed content: If the padlock still has a warning, Vovy scans the page for images or scripts loading over http:// and lists them for fixing.
What you provide
- Your site URL
- Access to your host and DNS
What you get
- Working padlock on your site
- The exact cause explained
- A list of any http:// assets to fix
FAQ
Do I have to pay for an SSL certificate?
No. Vercel, Netlify, Cloudflare and most modern hosts issue free certificates automatically.
Why does my site redirect forever?
Usually Cloudflare is set to Flexible SSL while your host also forces HTTPS, so they bounce visitors back and forth. Full (strict) fixes it.
How long does a new certificate take?
Usually a few minutes once DNS points at your host. If DNS is still changing, it can take longer.
Related tasks
All tasks