↑

Set up, harden, and maintain a secure website.

Your website is often the first thing an attacker looks at, and a weak one can be defaced, used to phish your customers, or quietly serve malware. This free checklist walks a small business through the same standards security teams use: build it right, lock it down, and keep it that way.

Step 1

Set up: get the foundations right before launch.

Most website breaches start with an account, not code. Lock down who can change your domain, DNS, and site before you publish anything.

Accounts & domain

  • Turn on multi-factor authentication (MFA), ideally passkeys, for your registrar, DNS, hosting, and content management system (CMS) accounts.
  • Use named accounts with the least privilege needed; no shared logins. Remove access the day someone leaves.
  • Enable registrar lock and WHOIS privacy, and keep the registrar contact email on a mailbox you control.
  • Sign your domain with Domain Name System Security Extensions (DNSSEC).
  • Add Certification Authority Authorization (CAA) records so only your chosen certificate authorities can issue certificates for your domain.

Platform & email

  • Prefer a static site or a hosted platform with automatic updates; every plugin and theme is more attack surface.
  • Serve the whole site over HTTPS with an automatically renewing certificate, and redirect all HTTP to HTTPS.
  • Keep secrets (API keys, form tokens) out of your code repository; store them in your host's secret manager.
  • Protect your domain from email spoofing with Sender Policy Framework (SPF), DomainKeys Identified Mail (DKIM), and Domain-based Message Authentication, Reporting, and Conformance (DMARC). Domains that never send mail should publish SPF -all and DMARC p=reject.
  • Use a staging copy for changes, and make deployments repeatable (for example, from a Git repository).
Step 2

Harden: tell browsers exactly what your site is allowed to do.

Security headers and modern encryption settings cost nothing and block whole classes of attacks, including cross-site scripting (XSS), clickjacking, and downgrade attacks. They map to OWASP Top 10:2025 A02 (Security Misconfiguration) and A04 (Cryptographic Failures).

Security headers

  • Strict-Transport-Security (HSTS): max-age of at least one year with includeSubDomains; add preload and submit to the preload list once every subdomain is HTTPS-only.
  • Content-Security-Policy (CSP): start from default-src 'none' or 'self', avoid 'unsafe-inline' and 'unsafe-eval', and set frame-ancestors 'none', base-uri, and form-action.
  • X-Content-Type-Options: nosniff.
  • Referrer-Policy: strict-origin-when-cross-origin or stricter.
  • Permissions-Policy: turn off camera, microphone, geolocation, and anything else you don't use.
  • Cross-origin isolation: Cross-Origin-Opener-Policy: same-origin, Cross-Origin-Resource-Policy: same-origin, and Cross-Origin-Embedder-Policy: require-corp where your embeds allow it.
  • Don't send Access-Control-Allow-Origin: * unless other sites truly need to read your content, and remove headers that reveal server software versions.

Encryption, forms & scripts

  • Allow only TLS 1.2 and 1.3, with modern ciphers (ECDHE key exchange with AES-GCM or ChaCha20); turn off TLS 1.0/1.1 and weak ciphers.
  • Turn off TLS 0-RTT (early data) unless you know you need it.
  • Load scripts from your own domain where possible. For any third-party script, use Subresource Integrity (SRI) or remove it; every tag is a supply-chain risk (OWASP Top 10:2025 A03).
  • If you set cookies, mark them Secure, HttpOnly, and SameSite.
  • Validate every form on the server, add bot protection, and rate-limit submissions.
  • Put a web application firewall (WAF) and bot protection in front of the site; most content delivery networks include one.
  • Publish /.well-known/security.txt (RFC 9116) with a security contact and an expiry date, plus a vulnerability disclosure policy.
Step 3

Maintain: security drifts unless someone owns it.

A site that scored well at launch slips as plugins age, staff change, and new scripts get added. Put these on a calendar and give them an owner.

Monthly

  • Rescan with the free tools below and compare against your last results.
  • Apply CMS, plugin, theme, and dependency updates; turn on automated update alerts (for example, Dependabot).
  • Review DMARC reports for anyone spoofing your domain.
  • Check certificate transparency logs for certificates you didn't request.

Quarterly & yearly

  • Quarterly: review who has access to your registrar, DNS, hosting, and CMS, and remove anyone who no longer needs it.
  • Quarterly: inventory third-party scripts, embeds, and forms, and remove what you no longer use.
  • Quarterly: test that you can restore the site from backup.
  • Yearly: renew the Expires date in security.txt, revisit your CSP, and confirm the registrar and certificate auto-renew.
  • Have a short plan for a defaced or compromised site: who takes it offline, who restores it, and who tells customers.
Step 4

Verify: scan it, read the results, fix what's real.

Free scanners turn this checklist into evidence. The skill is less in running them than in reading them: knowing which findings are real, which are false positives, and which fixes have side effects. Budget about an hour for a first pass, then 15 minutes a month. Scan only sites you own or have written permission to test; some of these tools send probes that look like an attack in your logs.

Run the scanners in this order

  • internet.nl on your bare domain (example.com, not www): the widest single test. It covers IPv6, DNSSEC, HTTPS and TLS, security headers, security.txt, and route origin validation (RPKI)[1].
  • Qualys SSL Labs: certificate chain, protocol versions, cipher suites, and how real browsers connect[2].
  • MDN HTTP Observatory: a graded review of your headers and Content Security Policy (CSP), with suggested fixes[3].
  • Security Headers: a quick header report card[4]. Run it on the bare domain with redirect-following turned off, so you see the headers on the redirect itself.
  • hstspreload.org: checks preload eligibility and tells you exactly what's blocking it[5].
  • A broad external scanner (for example, Sitelemetry[6]): probes for exposed files such as /.env and /.git, open cross-origin resource sharing (CORS), missing Certification Authority Authorization (CAA) records, and server banners. Treat its output as leads to confirm, not verdicts.
  • Google CSP Evaluator and crt.sh: a second opinion on your CSP, and a list of every certificate ever logged for your domain[7].

Read results like an auditor

  • Open one ticket per finding, with the evidence, the fix, an owner, and a retest date. Close it only after a rescan shows it fixed.
  • Confirm before you change anything. Reproduce the finding with a second tool or a direct DNS or HTTP check. Scanners disagree, and some are simply wrong.
  • Know the common false positives. A "missing CAA record" on www is fine when the bare domain has CAA records: certificate authorities climb the DNS tree to the parent domain until they find a CAA record set[8]. A Server: cloudflare banner is a default on some hosting platforms[9] and reveals nothing an attacker can't already see from your IP addresses.
  • Check the timestamp. A report may predate your last deployment, and some scanners cache results for several minutes.
  • Accepting a risk is a decision, not a shrug. Write down why, who approved it, and when you'll revisit it.

Traps that cost points

  • Redirect responses get graded too. If your bare domain only redirects to www, scanners such as internet.nl still check the security headers on that redirect[1]. A redirect created by your CDN never passes through your site's header settings, so add a minimal set with a CDN response-header rule[10]: default-src 'none' CSP, X-Frame-Options: DENY, and a Referrer-Policy. Be honest about what it buys: headers such as X-Frame-Options add little real protection on a redirect[11], so this is mostly about clean scores and consistency.
  • HSTS preload wants two hops. http://example.com must go to https://example.com first, on the same host, and only then to www[5][12]. A single jump from HTTP straight to https://www fails eligibility.
  • Preload is close to permanent. hstspreload.org itself recommends HSTS but not preloading for everyone, and list changes take months to reach browsers[5]. Submit only when you're committed to HTTPS on every current and future subdomain.
  • includeSubDomains breaks forgotten hosts. Before you turn it on, list every DNS record. Any subdomain without a valid certificate (an old webmail or vendor CNAME is the usual culprit) becomes unreachable in browsers, and HSTS gives visitors no way to click past the error[13].
  • Hosting defaults leak. Some static hosts add Access-Control-Allow-Origin: * to every response by default[9]. Override it (for example, by detaching the header[14]), then check the live headers, not just your config file.
  • TLS 1.3-only is the fastest fix for cipher findings, because TLS 1.3 removed the legacy cipher suites[15]. The trade-off: clients limited to TLS 1.2, including some older systems and corporate inspection proxies, can't connect, and NIST guidance for government systems still requires TLS 1.2 support[16]. Decide deliberately. While you're there, turn off TLS early data (0-RTT), which can be replayed by an attacker[15].
  • Dropping 'unsafe-inline' from style-src blocks every style= attribute and <style> block[17], including any HTML your scripts generate. Move them into stylesheets first, then add an automated check so they don't creep back.
  • Cross-Origin-Embedder-Policy require-corp blocks cross-origin images and frames that don't opt in; credentialless loads them without cookies instead[18]. Use it as a middle ground, and leave it off pages that embed third-party frames, such as CAPTCHA widgets.
  • security.txt should list a Canonical URL for every address it's served from, the bare domain included if scanners reach it through a redirect; readers are told not to trust a file fetched from a URL it doesn't list[19].

Keep it green

  • Snapshot your DNS and CDN security settings, and compare them daily against a reviewed baseline. Treat any unexplained change as a possible unauthorized change.
  • Make a failing check open a ticket or send an alert. A check that fails silently for a week is the same as no check.
  • Compare live response headers with your intended configuration on a schedule, not just at deployment.
  • Rescan after every platform, hosting, or DNS change, and at least monthly. Keep the reports as evidence for customers, insurers, and auditors.
  • When you add a subdomain, give it a valid certificate before it goes live; preloaded HSTS will enforce HTTPS on it from day one.
  • These steps support OWASP Top 10:2025 A02 (Security Misconfiguration) and A04 (Cryptographic Failures)[20], and the NIST Cybersecurity Framework (CSF) 2.0 Platform Security (PR.PS) and Continuous Monitoring (DE.CM) categories[21].
Sources for Step 4 (last reviewed November 16, 2026)

Primary sources first: standards bodies, browser vendors, and the tools' own documentation. Tool names are trademarks of their owners; Nexus Security Advisors has no affiliation with them and receives nothing for mentioning them.

  1. Internet.nl (Internet Standards Platform), Website test and test explanations, including security options on redirect responses. internet.nl
  2. Qualys, SSL Server Test. ssllabs.com
  3. Mozilla, HTTP Observatory. developer.mozilla.org
  4. Security Headers report. securityheaders.com
  5. Chromium, HSTS Preload List Submission: submission requirements, removal, and "HSTS preloading is not recommended" guidance. hstspreload.org
  6. Sitelemetry, website security audit. sitelemetry.com
  7. Google, CSP Evaluator, and Sectigo, crt.sh certificate transparency search. csp-evaluator.withgoogle.com · crt.sh
  8. IETF, RFC 8659, DNS Certification Authority Authorization (CAA) Resource Record, Section 3 (Relevant Resource Record Set), November 2019. rfc-editor.org
  9. Cloudflare, Serving Pages: default response headers, including Access-Control-Allow-Origin: * and Server: cloudflare. developers.cloudflare.com
  10. Cloudflare, Response Header Transform Rules. developers.cloudflare.com
  11. OWASP, HTTP Security Response Headers Cheat Sheet (X-Frame-Options on redirects). cheatsheetseries.owasp.org
  12. Mozilla, Web Security Guidelines, HTTP redirections: redirect to HTTPS on the same host before redirecting to another host. infosec.mozilla.org
  13. IETF, RFC 6797, HTTP Strict Transport Security (HSTS), Section 12.1 (No User Recourse), November 2012. rfc-editor.org
  14. Cloudflare, Pages headers: the _headers file and detaching a default header. developers.cloudflare.com
  15. IETF, RFC 9846, The Transport Layer Security (TLS) Protocol Version 1.3 (obsoletes RFC 8446), January 2026, including the replay properties of 0-RTT data. rfc-editor.org
  16. NIST, SP 800-52 Rev. 2, Guidelines for the Selection, Configuration, and Use of TLS Implementations, August 2019 (under review in 2026). doi.org · 2026 review notice
  17. MDN Web Docs, Content-Security-Policy: style-src directive. developer.mozilla.org
  18. MDN Web Docs, Cross-Origin-Embedder-Policy (COEP) header. developer.mozilla.org
  19. IETF, RFC 9116, A File Format to Aid in Security Vulnerability Disclosure (security.txt), Section 2.5.2 (Canonical), April 2022. rfc-editor.org
  20. OWASP, OWASP Top 10:2025. owasp.org
  21. NIST, CSWP 29, The NIST Cybersecurity Framework (CSF) 2.0, February 2024. doi.org

Last reviewed November 16, 2026. This checklist is general information, not a guarantee of security or compliance; results depend on your platform and configuration, and the standards above change. Confirm against the official sources.

Targets

What good looks like.

Use these scores as your finish line. They are free to check and easy to show a board, an insurer, or a customer who asks.

Scores to aim for

  • MDN HTTP Observatory: A+, with every test passing.
  • internet.nl website test: 100% (IPv6, DNSSEC, HTTPS, security options, and RPKI).
  • Qualys SSL Labs: A+.
  • Security Headers: A+.
  • hstspreload.org: eligible, then submitted.

Need a second set of eyes?

Nexus Security Advisors reviews and hardens small-business websites as part of our fractional virtual chief information security officer (vCISO) work, and we hold our own sites to this checklist.

Request a Call

Free resources

Benchmarks and free scanners.

These are the standards and tools this checklist is built on. Only scan sites you own or have permission to test.

Standards & guidance

Free scanners

Browse more free tools in the Nexus Resource Library.

Let's Talk

Start with a free 30-minute discovery call.

Tell us your industry, size, and the security or compliance challenge in front of you. We'll tell you plainly whether we're a fit.

We reply within one business day.