Skip to content

Finding

Every file on the page loads over https

Nothing on the page is pulled over a plain connection.

Last updated September 20, 2026

Good to know · About ten minutes

Why AI-built apps get this

An AI builder gives you HTTPS on the hosted address and stops there. The moment you point your own domain at it, the redirect, the certificate and every hard-coded http:// in a copied snippet become yours. Nothing in the build warns you, because from the inside everything still works.

What it affects

Nothing on the page is pulled over a plain connection.

What the evidence line looks like

GET http://example.com returned 301 to https://example.com, certificate valid to 2026-12-01

Every finding on a result carries a line like this one: the request that was made and the answer that came back. You can run the same request yourself and get the same answer, which is the point.

The fix

Nothing to change here.

Prompt for your coding agent

Keep all asset references on https.

A result gives you this prompt written for your builder, in its own dialect, and a batch prompt that carries every fix at once.

Incidents that involved this

  • Not verified

    First-quarter 2026 assessment of 200 apps

    183 of 200 vibe-coded apps, 91.5 percent, contained at least one vulnerability traceable to AI hallucination or missing security context.

  • Declared

    CVE growth in AI-generated code

    CVE entries attributed to AI-generated code rose from 6 in January 2026 to more than 35 in March 2026.

  • Observed

    5,600 vibe-coded apps scanned

    More than 2,000 vulnerabilities and more than 400 exposed secrets found across vibe-coded apps.

  • Not verified

    Tenzai study of AI-built apps

    69 vulnerabilities across 15 apps built by five AI coding tools.

Related terms

Run the free Launch Risk Check on your app

ShipReady is not a penetration test or a security certification. No automated check can prove an application is secure.

Last updated September 20, 2026