Tech Stack Checkup
A short checklist of what to update, tighten and test going into 2027. You can check your website first: we read only public signals, such as headers, version numbers and email records, and mark the matching items for you.
From the Headless Web & AI Development toolset.
1. Check a website (optional)
Read-only and passive: one visit to your homepage over HTTPS and HTTP, two public files and a DNS lookup. No logins, no forms, no probing.
2. The checklist: update, tighten, test
Update
0 of 4 doneCISA says many software updates are made to fix security risks. Source: CISA, Secure Our World: Update software (opens in a new tab)
How to do it
Install the current release of your CMS or site builder. Ask your host which server and PHP versions you run. Turn on automatic updates where you can.
The WordPress hardening guide says to keep plugins updated and to delete the plugins you do not use. Source: WordPress, Hardening WordPress (opens in a new tab)
How to do it
Open your list of plugins, themes and apps. Update each one. Delete what you do not use. Get add-ons only from sources you trust.
jQuery supports only its latest version, and its 1.x and 2.x branches are no longer supported. Source: jQuery, Version support (opens in a new tab)
How to do it
Ask your developer which libraries the site loads and which versions. Plan an update for each old one, and test the pages that use it.
CISA advises you to patch and update software and operating systems to the latest available versions. Source: CISA, #StopRansomware Guide (opens in a new tab)
How to do it
Think of the old booking tool, the intranet, the shared drive and the server in the closet. For each one, choose: update, replace or shut down.
Tighten
0 of 5 doneCISA advises you to remove accounts you do not need and to check user and admin accounts for inactive ones every quarter. Source: CISA, #StopRansomware Guide (opens in a new tab)
How to do it
List every service your business logs in to: domain, hosting, CMS, email, payments, analytics. Close what you no longer use. Replace shared logins with named accounts.
CISA advises least privilege for all systems and services, and separate admin accounts from everyday user accounts. Source: CISA, #StopRansomware Guide (opens in a new tab)
How to do it
Check who has admin rights in your CMS, hosting, domain and email accounts. Remove admin rights from people who do not need them. Use a separate account for admin work.
CISA says that with MFA, a person who steals a password still cannot meet the second check to get in. Source: CISA, More than a Password (multifactor authentication) (opens in a new tab)
How to do it
Start with email, your domain registrar, hosting, the CMS admin and payment accounts. CISA advises phishing-resistant MFA for all services.
SPF lists the servers allowed to send email as your domain. DMARC tells receivers how you want them to treat mail that fails the checks. Source: IETF, RFC 9989: DMARC (opens in a new tab)
How to do it
Publish one SPF record that ends in -all or ~all. Publish a DMARC record, read the reports, then move from p=none to p=quarantine or p=reject.
For DKIM, MX and the full set of email records, use our Email Deliverability Checker.
OWASP says every page of a site should use HTTPS (TLS), the login page and all the others. Source: OWASP, Transport Layer Security Cheat Sheet (opens in a new tab)
How to do it
Send all HTTP visits to HTTPS. Add the security headers the scan lists. Set the Secure flag on cookies. Take version numbers out of public headers.
Test
0 of 4 doneCISA advises offline, encrypted backups of critical data, and regular tests that the backups are available and intact. Source: CISA, #StopRansomware Guide (opens in a new tab)
How to do it
Pick one backup of your website and one of your key business files. Restore them to a safe test place. Write down how long it took and what was missing.
CISA advises you to understand and take inventory of your organization's IT assets. Source: CISA, #StopRansomware Guide (opens in a new tab)
How to do it
Keep one list: domains, website platform, plugins, outside scripts, vendors, who owns each login and when each part was last updated.
CISA advises a basic incident response plan with a communications plan, and a contact list to fill in before you need it. Source: CISA, #StopRansomware Guide (opens in a new tab)
How to do it
Write down who decides, who fixes and who to call: your developer, host, domain registrar, bank and insurer. Keep a copy that does not depend on your computer.
security.txt (RFC 9116) tells people who find a security problem on your site how to report it to you. Source: IETF, RFC 9116: security.txt (opens in a new tab)
How to do it
Add a plain text file at /.well-known/security.txt with a Contact line and an Expires date less than a year away.
Start with these
The copy is plain text, ready to paste into an email, a ticket or a doc.
What this check does not do
- It does not log in, send forms, guess admin or private addresses, test for weak spots or scan ports. It reads what any visitor's browser can see.
- It reads the homepage only. Other pages, scripts that a tag manager adds after the page opens, and cookies set by scripts are out of view.
- A clean result does not prove a site is safe, and a flag does not mean it was attacked. Logins, admin access, backups and server settings need the checklist.
- We wait up to 10 seconds for the homepage and up to 6 seconds for each file, and we read up to 1.5 MB of the homepage source.
Sources
MDN Web Docs
- Strict-Transport-Security header (opens in a new tab)
- Content-Security-Policy header (opens in a new tab)
- Content-Security-Policy-Report-Only header (opens in a new tab)
- CSP frame-ancestors directive (opens in a new tab)
- X-Content-Type-Options header (opens in a new tab)
- X-Frame-Options header (opens in a new tab)
- Referrer-Policy header (opens in a new tab)
- Permissions-Policy header (opens in a new tab)
- Set-Cookie header (opens in a new tab)
- Mixed content (opens in a new tab)
- Subresource Integrity (opens in a new tab)
- Server header (opens in a new tab)
- Standard metadata names: generator (opens in a new tab)
