GuideLaunching
Startup website security checklist for 2027
The six response headers and two settings most new startup sites still miss, measured on 4,160 sites, with the exact header to send and how to check each one.

A startup website should send six response headers and get two settings right: a Content-Security-Policy, frame protection, X-Content-Type-Options set to nosniff, Strict-Transport-Security, a Referrer-Policy and a Permissions-Policy, plus a redirect from http:// to https:// and a published DMARC record for the domain's email. Most new sites get several of these wrong. Each fix is a line or two of configuration.
We know how often they are missed because we measured it. Between 14 September and 14 November 2026, LaunchScaler scanned 4,160 reachable startup websites, most of them found through launch directories in their launch week. The full numbers are in our startup website security study. This checklist goes through each item in the order that fixes the most risk for the least work, with the header to send and how to confirm it took.
How often do new startup sites miss each item?
Counted once per site, from each site's latest scan:
| Item | Sites failing |
|---|---|
| No Content-Security-Policy | 65% |
| Trackers load before consent | 59% |
| Can be framed by another site | 54% |
| No X-Content-Type-Options nosniff | 47% |
| No HSTS header | 35% |
| No DMARC record | 29% |
| No privacy policy we could reach | 10% |
| HTTP does not redirect to HTTPS | 6% |
Only 27% of the sites sent all four of CSP, frame protection, nosniff and HSTS. 22% sent none of them. The category barely changes the picture: among the 138 sites that sell security products, 61% had no Content-Security-Policy.
1. Redirect HTTP to HTTPS on the same host
This is the cheapest item and the one most hosts already do for you. A visitor who types http://yourdomain.com should get a redirect (301 or 308) to https://yourdomain.com as the very first response, on the same host, before anything else happens. 6% of the sites we scanned did not.
Most hosts can do this with a switch. The details for each, and the redirect loops to avoid, are in our guide to the HTTP to HTTPS redirect. Check it with one request:
curl -sI http://yourdomain.com | head -3
You want a 301 or 308 status and a location: header that starts with https://yourdomain.com. A redirect to a different host first, or a 200 over plain HTTP, fails.
2. Send Strict-Transport-Security
The HTTPS redirect protects the second request. HSTS protects every request after the first visit: it tells the browser to use HTTPS for your domain without asking, so a network attacker cannot strip the redirect. 35% of sites sent no HSTS header at all.
Strict-Transport-Security: max-age=63072000; includeSubDomains
max-age=63072000 is two years, the value OWASP recommends. The preload rules and the ways HSTS can lock you out are in our HSTS header guide. Our scan passes anything of at least six months (15768000). Add includeSubDomains only when every subdomain serves HTTPS, and add preload only when you are ready to submit the domain at hstspreload.org, because removal from the preload list takes months.
3. Turn off MIME sniffing with nosniff
Without this header a browser may guess a file's type from its contents instead of trusting the Content-Type you sent, which lets an uploaded file be run as a script. It is one fixed value with no tuning, and 47% of sites still did not send it.
X-Content-Type-Options: nosniff
The value must be exactly nosniff. Anything else is treated as absent.
4. Stop other sites framing your pages
If another site can load your page inside an invisible frame, it can trick a visitor into clicking your buttons while they think they are clicking theirs. That is clickjacking, and 54% of the sites we scanned allowed it on their homepage.
Either header works. The modern one is a CSP directive:
Content-Security-Policy: frame-ancestors 'self'
The older one is still understood by every browser:
X-Frame-Options: SAMEORIGIN
Use 'none' or DENY if nothing, including your own site, ever needs to frame the page. If you embed your own pages (a widget, a checkout preview), 'self' or SAMEORIGIN keeps that working.
5. Add a Content-Security-Policy
CSP is the item most sites skip, 65% of them, because a strict policy breaks things when it is written carelessly. It is also the one that does the most: a policy that names where scripts may load from turns an injected script tag into a blocked request.
Start in report-only mode so nothing breaks:
Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self' https://your-analytics.example; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; frame-ancestors 'self'; report-uri /csp-report
Read the violation reports for a week, add the hosts your site genuinely needs, then send the same policy as Content-Security-Policy. Our Content-Security-Policy starter for a SaaS has a fuller policy with the usual analytics, payments and chat hosts already in it. Our scan, like Mozilla's Observatory, counts a report-only policy as no policy, because it blocks nothing.
Two notes from the sites we read. Framework starters often ship with no CSP at all, so check your framework's default rather than assuming it is there. And a policy with 'unsafe-inline' in script-src is better than none but gives up most of the protection; aim for nonces or hashes once the basic policy is stable.
6. Set a Referrer-Policy and a Permissions-Policy
Neither is a scored failure in our scan, and both are one line. Referrer-Policy stops full URLs, with any tokens in their query strings, from leaking to other sites through the Referer header:
Referrer-Policy: strict-origin-when-cross-origin
Permissions-Policy switches off browser features your site never uses, so an injected script cannot ask for them:
Permissions-Policy: camera=(), microphone=(), geolocation=()
7. Publish a DMARC record for your domain
This one is not a response header, but it belongs on a security checklist because it protects your domain's name. Without DMARC, anyone can send email that claims to come from your domain, and the receiving server has no policy to check it against. 29% of the domains we scanned published no DMARC record at all.
A DMARC record is a TXT record at _dmarc.yourdomain.com. Start in monitoring mode, then move to enforcement once your legitimate mail passes:
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@yourdomain.com
The full setup, with SPF and DKIM first, is in our guide to SPF, DKIM and DMARC records for a startup domain, and the free email authentication checker reads your records the same way our scan does.
8. Load trackers only after consent, and publish a privacy policy
59% of the sites we scanned stored or read analytics or advertising identifiers before the visitor made any consent choice, in a fresh browser session. If you have visitors in the EU or UK, the ePrivacy rules require consent before non-essential identifiers are stored or read, so the order matters: the banner first, the tags after a yes. What the banner must offer, and what counts as consent, is in our guide to cookie banner requirements. 9% of sites had the opposite problem, a consent banner that covered the page and blocked it until the visitor answered.
10% had no privacy policy we could reach from the homepage. If the site has a contact form, analytics or a sign-up, it collects personal data, and the policy needs to be published and linked, not drafted. The list of what it has to say is in what a SaaS privacy policy must include.
What mistakes did we see most often?
Reading the headers of thousands of new sites shows the same handful of near misses, where a team clearly tried and the header still did nothing.
- A report-only CSP left in place.
Content-Security-Policy-Report-Onlyis the right first week. Left alone for months, it is a policy that blocks nothing. Set a date to switch it. - An HSTS max-age measured in minutes. Teams test HSTS with
max-age=300and never raise it. Browsers forget the rule five minutes later. Six months is the floor our scan passes. X-Frame-Options: ALLOW-FROM. That value is obsolete and modern browsers ignore it, so the page is frameable again. Use CSPframe-ancestorswith the hosts you need instead.- Headers on the page but not on redirects or errors. On nginx,
add_headerskips error responses unless you addalways. On some hosts, a header set for one path pattern misses the homepage. Check the first response, not a later one. - Two CSP headers at once. A framework adds one and the host adds another. Browsers apply both, so the stricter one wins and parts of the page break in ways nobody can explain. Keep one source of truth.
- A nosniff value with a typo. Anything other than exactly
nosniffcounts as no header.
A starter set you can paste
If your host lets you set headers in one place, this set covers items 2 to 6 for a typical startup site. Adjust the CSP hosts to the scripts your site really loads, and keep it in report-only mode for the first week:
Strict-Transport-Security: max-age=63072000; includeSubDomains
X-Content-Type-Options: nosniff
Content-Security-Policy-Report-Only: default-src 'self'; script-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; frame-ancestors 'self'; report-uri /csp-report
X-Frame-Options: SAMEORIGIN
Referrer-Policy: strict-origin-when-cross-origin
Permissions-Policy: camera=(), microphone=(), geolocation=()
Sending both X-Frame-Options and frame-ancestors is fine. Older browsers read the first and newer ones the second, and they agree here. Once the CSP is enforcing, frame-ancestors is the one that counts.
How do you add these headers on common hosts?
Most startup sites run on a platform where headers live in one config file.
- Next.js: return them from
headers()innext.config.js, matched to/(.*). - Vercel (any framework): a
headersarray invercel.json. - Netlify: a
_headersfile in the publish directory, or[[headers]]innetlify.toml. - Cloudflare in front of any host: a Transform Rule that sets response headers.
- nginx:
add_headerlines with thealwaysflag, so they apply to error pages too.
Set them once at the edge rather than per route, so a new page cannot ship without them.
How do you check that the headers took?
Read the response of the first document request, not of an asset:
curl -sI https://yourdomain.com
Or paste the address into the free security headers checker. It reads the same headers our scan grades and shows each verdict with the value it saw. To see every item on this list at once, along with the rest of a launch readiness check, run the free scan.
What should you fix first?
If you only have ten minutes, do items 1 to 4: the redirect, HSTS, nosniff and frame protection are fixed values that need no testing and break nothing. Then start CSP in report-only mode and come back to it in a week. Then add DMARC. Those five changes would move a site from the 22% that send none of these headers to the 27% that send them all.
Questions, answered
What people ask about this
01What security headers should a startup website send?
- At minimum: Content-Security-Policy, Strict-Transport-Security with a max-age of at least six months, X-Content-Type-Options set to nosniff, and frame protection through X-Frame-Options or a CSP frame-ancestors directive. Referrer-Policy and Permissions-Policy are cheap additions on top.
02How many new startup sites miss these headers?
- Of 4,160 startup websites LaunchScaler scanned between 14 September and 14 November 2026, 65% sent no Content-Security-Policy, 54% could be framed by another site, 47% had no nosniff header and 35% had no HSTS header. Only 27% sent all four.
03Do security headers affect SEO?
- Not directly. Google does not rank pages on response headers. HTTPS and a redirect from HTTP do matter for how Google treats the site, and a hacked or spoofed site loses traffic fast, so the headers protect the rankings you have.
04Is a Content-Security-Policy hard to add?
- A strict policy takes testing, because it blocks any script or style it does not name. Start with Content-Security-Policy-Report-Only, read what it would block for a week, then switch the same policy to enforcing.
05How do I check my site's security headers?
- Open your browser's developer tools, reload the page and read the response headers on the first document request, or paste the address into LaunchScaler's free security headers checker, which reads the same headers our scan grades.
Sources
- MDN Web Docs: Content-Security-Policydeveloper.mozilla.org
- MDN Web Docs: Strict-Transport-Securitydeveloper.mozilla.org
- MDN Web Docs: X-Content-Type-Optionsdeveloper.mozilla.org
- MDN Web Docs: X-Frame-Optionsdeveloper.mozilla.org
- OWASP Secure Headers Projectowasp.org
- OWASP Cheat Sheet Series: Clickjacking Defensecheatsheetseries.owasp.org
- RFC 6797: HTTP Strict Transport Security (HSTS)rfc-editor.org
- HSTS Preload List Submissionhstspreload.org
- Mozilla HTTP Observatorydeveloper.mozilla.org


