Flat vector illustration of a website security checklist with a shield

A useful website security checklist covers six layers: domain and DNS, email authentication, TLS, headers and cookies, application and CMS, and accounts and operations. Most small-site breaches start in one of those six places, not in exotic exploit code. Work through the 30 items below in order; the first ten take minutes and close the widest gaps.

Why this matters for your website

Attackers scan the whole internet continuously. They are not choosing you; they are matching your site against a list of known-vulnerable plugin versions, expired certificates, open ports and forgotten subdomains.

That is good news, because generic attacks are stopped by generic hygiene. A checklist beats intuition here: it is repeatable, it can be delegated, and it produces evidence you can show a customer or an insurer. For background on the moving parts, see our website security guide.

The 30-point website security checklist

Each item is one action plus how to verify it. Assign an owner to every group before you start.

Diagram of six website security layers from domain and DNS up to accounts and operations
The checklist works upward: fix the domain layer before the application layer.

Domain and DNS (1-5)

  • 1. Turn on registrar lock. Confirm WHOIS shows clientTransferProhibited. Domain theft redirects every service you run.
  • 2. Check auto-renew and billing. An expired domain is a total outage and an easy hijack. Verify the renewal date and the card on file.
  • 3. Remove dangling DNS records. Resolve every CNAME target; records pointing at deleted cloud apps allow subdomain takeover.
  • 4. Restrict DNS access. Named accounts with MFA only. Remove ex-staff and old agency logins from the registrar and DNS panel.
  • 5. Publish a CAA record. It limits which certificate authorities may issue for your domain. Verify with dig CAA example.com.

Email authentication (6-10)

  • 6. Publish exactly one SPF record. One TXT record, under ten DNS lookups, ending in -all or ~all. Two records break validation.
  • 7. Sign outbound mail with DKIM. Check that the selector key resolves and that received mail shows a passing signature.
  • 8. Set a DMARC policy. Start at p=none with rua=, then move to quarantine and reject as defined in RFC 7489.
  • 9. Lock down non-sending domains. Parked and legacy domains need v=spf1 -all plus DMARC p=reject.
  • 10. Read your DMARC reports. Aggregate reports reveal spoofing and forgotten senders. Route rua to a mailbox someone checks.

TLS and certificates (11-15)

  • 11. Redirect all HTTP to HTTPS. Test the apex, www and a deep path; each should return a 301 to the HTTPS version.
  • 12. Automate certificate renewal. Alert at least 14 days before expiry and confirm the chain serves intermediate certificates.
  • 13. Disable legacy protocols and ciphers. TLS 1.2 minimum, 1.3 preferred; SSLv3, TLS 1.0 and 1.1 off.
  • 14. Enable HSTS. Send Strict-Transport-Security with a max-age of at least 31536000 once every hostname serves HTTPS.
  • 15. Cover every hostname. The certificate must match apex, www, staging and API hostnames; mismatches train users to ignore warnings.

Headers and cookies (16-20)

  • 16. Deploy a Content-Security-Policy. Start in report-only mode, fix the violations, then enforce. It is your best defence against injected scripts.
  • 17. Send `X-Content-Type-Options: nosniff`. One line that stops browsers guessing content types.
  • 18. Block framing. Use CSP frame-ancestors or X-Frame-Options: DENY to prevent clickjacking on login and checkout pages.
  • 19. Set Referrer-Policy and Permissions-Policy. Stop URL leakage to third parties and switch off camera, microphone and geolocation you do not use.
  • 20. Flag session cookies. Every session cookie needs Secure, HttpOnly and SameSite=Lax or stricter.

Application and CMS (21-25)

  • 21. Patch core, plugins and themes weekly. Set a fixed day. Most WordPress and WooCommerce compromises use a patched flaw.
  • 22. Delete unused plugins and themes. Deactivated code still ships files that remain reachable over HTTP.
  • 23. Cross-check components against advisories. Match your installed versions against WPScan and the NVD.
  • 24. Remove exposed files. Request /.git/config, /.env, /phpinfo.php and old backup archives; all should return 404.
  • 25. Harden admin endpoints. Rate-limit wp-login.php and xmlrpc.php, and disable the built-in theme and plugin file editor.

Accounts and operations (26-30)

  • 26. Enforce MFA on every admin account. Hosting, CMS, registrar, payment gateway and email. No shared logins.
  • 27. Apply least privilege and remove dormant users. Review the user list monthly; contributors do not need administrator roles.
  • 28. Rotate API keys and integration tokens. Especially after staff changes or an agency handover. Scope keys to what they actually need.
  • 29. Test a restore, not just a backup. Keep offsite, versioned backups and restore one to a staging site each quarter.
  • 30. Write a one-page incident plan and keep logs. Name who to call, where backups live, and retain access and error logs for 90 days.

Items 16 to 25 map closely to the OWASP Top 10, which is the reference list your developer should already be working from.

Printable summary: how to check and who owns it

  • Items 1-5, domain and DNS - check with WHOIS and dig, plus your registrar console. Owner: whoever pays the domain bill.
  • Items 6-10, email authentication - check with a DMARC lookup and a test send. Owner: IT or email admin.
  • Items 11-15, TLS - check with a TLS audit tool and a browser. Owner: hosting provider or developer.
  • Items 16-20, headers and cookies - check response headers in browser developer tools. Owner: developer.
  • Items 21-25, application and CMS - check the updates screen, plugin list and direct file requests. Owner: site maintainer or agency.
  • Items 26-30, accounts and operations - check user lists, MFA status and a real restore test. Owner: business owner.
Decision tree showing which checklist items free tools, a passive scan and an active scan cover
Free tools cover headers and email; passive scanning adds DNS and TLS; only active scanning reaches the application layer.

How to check your own site

You can run most of this manually; see how to check your website security for the command-line route. If you would rather automate it, that is what we build.

Scantinel (scantinel.ai) is an automated website security assessment platform that runs OSINT, network, and OWASP Top 10 web vulnerability tests against ownership-verified assets and delivers actionable, business-owner-legible reports. Here is the honest mapping to this checklist:

  • Free tools, no account: items 16-20 with the check your headers free tool, and items 6-10 when you check your DMARC record.
  • The Essential scan (minutes, passive): items 1-20 plus CMS version, known-vulnerable plugin detection and exposed common files.
  • The Full scan (hours, verified ownership): the rest of items 21-25 through active OWASP Top 10 testing, WPScan-based CMS depth, supply-chain checks and subdomain takeover detection.
  • The Premium AI scan: authenticated testing and business-logic flaws such as IDOR chains, with analyst validation.

Items 26 to 30 are process, not scanning: no tool can test your restore for you. Scans only run against ownership-verified assets and are never destructive, and a scan is not a penetration test. If you want the technical two-thirds handled on a schedule, you can run the whole checklist automatically.

Key takeaways

  • Six layers cover almost all routine risk: domain and DNS, email authentication, TLS, headers and cookies, application and CMS, accounts and operations.
  • Items 1-10 are the highest return for the least effort and need no developer.
  • Every item needs a named owner, otherwise it is checked once and forgotten.
  • Patching and MFA prevent more real incidents than any single header.
  • A backup you have never restored is not a backup.

Frequently asked questions

What should a website security checklist include?

It should include domain and DNS controls, email authentication (SPF, DKIM, DMARC), TLS configuration, security headers and cookie flags, CMS and plugin patching, and account and backup hygiene. Each line needs a verification method and an owner. Without those two columns, a checklist is just a wish list.

How often should I go through a website security checklist?

Patching and user reviews belong on a weekly or monthly cycle. Run the full 30 items quarterly, and always after a site rebuild, a migration, or an agency handover. Automated scanning can cover the technical items continuously between manual passes.

What is the first thing to check for website security?

Check that multi-factor authentication is enabled on your registrar, hosting and CMS administrator accounts. Credential compromise gives an attacker everything at once, so no header or certificate compensates for a weak admin login. Registrar lock is the close second.

Published January 2026 by the Scantinel Security Research Team. Security guidance changes; verify specifics against primary sources such as OWASP, the NVD and WPScan.