Based on the error description and the screenshot showing https://api.versabiz.pe flagged as "No es seguro" (Not Secure), this typically happens due to a few common configuration or SSL certificate provisioning issues:

1. Mixed Content Issues (Frontend calling HTTP instead of HTTPS)

Even if your backend domain has a valid SSL certificate, if your frontend is deployed over HTTPS and attempts to fetch or call the backend using http://api.versabiz.pe (hardcoded or misconfigured in environment variables), the browser will block or flag the connection as insecure due to mixed content policies.

Fix: Double-check your frontend environment variables (e.g., NEXT_PUBLIC_API_URL or equivalent) to ensure they explicitly start with https:// rather than http://.

1. SSL Certificate Still Provisioning or Domain Validation Pending

Since you configured the custom domain's DNS on Vercel (or whichever host you're using for the API), a "Not Secure" browser warning often means the SSL certificate hasn't finished issuing, or a DNS record (like a missing CNAME or TXT validation record) is misconfigured, preventing Let's Encrypt / the platform from completing the automated HTTPS certificate generation.

Fix: Go back to your hosting dashboard, verify that the custom domain status shows a green/active SSL check, and ensure all DNS records (such as A or CNAME records pointing to your deployment) are fully propagated.

1. Missing HSTS or Improper Redirection

If the server accepts plain HTTP traffic without automatically redirecting it to HTTPS, or if the SSL handshake fails on initial load, browsers default to the warning view.

Fix: Ensure your deployment platform or reverse proxy enforces Automatic HTTPS Redirection so any incoming http:// request is seamlessly upgraded to `