Skip to content

Product

Why a curl isn't a website scan

Static fetches catch headers and TLS. A real browser catches what users actually load — and what still blocks handoff.

· by Henry Smith

Why a curl isn't a website scan

I still reach for curl first: it shows headers, status, TLS, and the initial HTML response.

A real browser finishes the page with scripts, redirects, and client-side routes, so a complete check needs both the static response and the rendered result.