Website security is not a product you buy; it is eight layers you keep in order, from the domain name down to the backup you have actually restored. Most incidents on small sites are not clever exploits. They are an expired certificate, a missing DMARC record, an abandoned plugin with a public CVE, or an admin login with no second factor. This guide gives you one concrete failure, a check you can run in five minutes and a fix for every layer.
Why this matters for your website
Your public website is the one asset you invite strangers to interact with. The traffic that finds its weak points is almost entirely automated: scanners walk address ranges and certificate transparency logs looking for known versions, exposed files and open services.
That is good news, because automated attacks look for known problems. Fix the known problems and you drop out of the easy-target pool. The layers below are ordered from the outside in, which is the same order an attacker sees them.
Layer 1: Domain and DNS
- What goes wrong: a CNAME still points at a cancelled hosting account, so somebody else claims that hostname and serves content on your subdomain.
- Check (2 minutes): confirm registrar lock and registrar 2FA are on, then run
dig CAA example.comanddig DS example.comto see whether CAA and DNSSEC exist. - Fix: enable registrar lock and DNSSEC, publish a CAA record naming your certificate authority, and delete DNS records that point to services you no longer use.
Layer 2: Email authentication
- What goes wrong: without DMARC enforcement, anyone can send an invoice that appears to come from your domain, and your customer pays it.
- Check (2 minutes): use the free SPF/DMARC checker to confirm you publish exactly one SPF record and a
_dmarcTXT record. - Fix: keep one SPF record ending in
-all, enable DKIM signing at your mail provider, then move DMARC fromp=nonetop=quarantineand on top=rejectonce reports are clean.
Layer 3: TLS and certificates
- What goes wrong: a manually renewed certificate expires on a Saturday and every visitor meets a browser warning until Monday.
- Check (1 minute): open the padlock in your browser to read the expiry date, and confirm
http://requests redirect tohttps://. - Fix: automate renewal with ACME, disable TLS 1.0 and 1.1, send a permanent redirect to HTTPS, and add
Strict-Transport-Security: max-age=31536000; includeSubDomains.
Layer 4: HTTP security headers and cookies
- What goes wrong: no Content-Security-Policy, so an injected script runs with full access to the page and its session cookie.
- Check (1 minute): check your security headers free for CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy.
- Fix: set the headers at your CDN or web server, and mark session cookies
Secure; HttpOnly; SameSite=Lax.
Layer 5: The application layer
The OWASP Top 10 is the shared vocabulary for application risk. Five categories cause most of the damage on small sites:
- Broken access control: changing an order ID in a URL shows another customer's invoice. Test by opening one account's object as another account.
- Security misconfiguration: debug mode, directory listing or a default admin account left enabled in production.
- Vulnerable and outdated components: a library or plugin with a published CVE that you never updated.
- Injection: unsanitised input reaching a SQL query or rendered as HTML, including cross-site scripting.
- Authentication failures: no rate limiting, no 2FA, and passwords reused from another breach.
Layer 6: CMS, plugins and third-party scripts
- What goes wrong: an abandoned WooCommerce add-on carries a known flaw, or a marketing tag loaded from someone else's server is modified.
- Check (5 minutes): list installed plugins and themes against WPScan and NVD, and list every script tag you do not control.
- Fix: remove what you do not use, enable automatic minor updates, self-host or pin third-party scripts with subresource integrity, and restrict origins with CSP.
Layer 7: Admin access and login
- What goes wrong:
/wp-adminis reachable from anywhere and gets credential-stuffed with passwords leaked elsewhere. - Check (3 minutes): count admin-level accounts, confirm every one has 2FA, and check whether failed logins are rate limited.
- Fix: enforce 2FA, delete dormant accounts, downgrade editors who do not need admin, rate-limit or lock login endpoints, and restrict admin paths by IP or SSO where you can.
Layer 8: Backups and incident readiness
- What goes wrong: backups run nightly to the same server as the site, so an attacker with server access destroys both.
- Check (5 minutes): find the date of your last successful test restore, and confirm one copy is off-site and immutable.
- Fix: follow 3-2-1 (three copies, two media, one off-site), test a restore quarterly, and keep a one-page plan listing host, registrar, CA and developer contacts.
Which layer, which test
- Domain and DNS: free with
digor your registrar dashboard; deeper with an automated DNS and takeover audit. - Email authentication: free with an SPF/DMARC checker; deeper with DMARC aggregate report analysis.
- TLS: free in the browser; deeper with a protocol and cipher audit.
- Headers and cookies: free with a headers checker; deeper with an authenticated crawl of every template.
- Application layer: free with OWASP ZAP or nuclei if you can run them; deeper with a verified active scan.
- CMS and plugins: free with WPScan and NVD lookups; deeper with a full WPScan or droopescan run.
- Admin access: free by reviewing your user list; deeper with authenticated testing using test credentials.
- Backups: free by restoring to a staging site; no tool replaces the drill.
How to check your own site
Testing runs on a spectrum from passive to active. Start passive, then go deeper only on assets you own.
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. Begin with the free website security check, which needs no account.
- Essential scan (minutes, passive): DNS, SPF/DKIM/DMARC, TLS, headers, cookie flags, exposed files, CMS version and known-vulnerable plugins.
- Full scan (hours, ownership verified): subdomain and origin-IP discovery, port and service fingerprinting with CVE correlation, active OWASP Top 10 2025 testing, CMS deep scan and supply-chain checks.
- Premium AI scan (1-3 business days): an autonomous agent probing business-logic flaws, IDOR chains and multi-step auth bypasses, plus authenticated scanning and human analyst validation.
Scans are non-destructive and only run against verified assets. A scan is not a penetration test; it finds known and testable issues, and a tester reasons about your business. See how the scan works or run a full website security scan.
Key takeaways
- Work from the outside in: domain, email, TLS, headers, application, CMS, admin, backups.
- Most real incidents exploit known, published weaknesses, so patching and configuration beat exotic defences.
- Every check above takes five minutes or less; the hard part is doing them on a schedule.
- A backup you have never restored is a plan, not a backup.
- Passive checks are free and continuous; active testing belongs on assets you can prove you own.
Frequently asked questions
How do I know if my website is secure?
You cannot prove a site is secure, but you can prove the common failures are absent. Walk the eight layers in this guide and record the result of each check, then re-run them after every major change. Automated scanning covers the known-issue portion quickly; business-logic flaws need authenticated or manual testing.
How often should I check website security?
Run passive checks monthly, and after any plugin, theme, DNS or hosting change. Schedule a deeper active scan quarterly, or monthly if you take payments or store personal data. Certificate expiry and backup restores deserve their own calendar reminders.
Is HTTPS enough to secure a website?
No. HTTPS encrypts traffic between browser and server; it says nothing about your plugins, admin passwords, access controls or DNS. A fully patched HTTPS site can still be taken over through an outdated plugin or a reused admin password. Treat TLS as one layer of eight.
Published February 2026 by the Scantinel Security Research Team; verify security-critical details against primary sources such as OWASP, NVD and WPScan.
Comments
No comments yet.