Paste the output of curl -I https://your-site, or the response headers the browser's network tools copy, and it tells you what's missing or wrong: CSP, HSTS, cookie flags (Secure, HttpOnly, SameSite) and the rest of the usual security headers.
This tool AUDITS what a site is already sending. If you want the nginx or Apache configuration for your own project, use the SPA configuration tool.
Response headers don't repeat the request's scheme. If you paste the command line (curl -I https://…) or the bare URL, it's detected from there; with no clue at all, HTTPS is assumed (the most common real case) — and you can correct it by hand with the toggle.