About Sitewarden

Sitewarden started as a checklist. Every time a new client site landed on our desk, the first hour went the same way: openssl s_client to see what the certificate really said, dig for the SPF and DMARC records nobody had touched in years, curl -I to find out which security headers were missing, then a slow read of the markup looking for the things that quietly cost traffic.

The hour was never the problem. The problem was that the output lived in a terminal scrollback, and the client needed something they could act on and hand to their own developer. So the checklist became a script, the script grew a scoring model, and eventually it made more sense as a product than as a folder of shell aliases.

That history is why the tool is shaped the way it is. It reports evidence rather than verdicts — the actual header value, the actual DNS record — because the person who has to fix the problem will want to see it. And it is honest about its limits: the accessibility checks are called spot checks because that is what they are, and the performance category carries the smallest weight because measuring one document fetch is not a field performance profile.

It is a small, independent, self-funded business. There is no venture money, no growth team and no plan to be acquired. That means the roadmap is driven by what customers ask for, and that support is answered by the person who wrote the check you are asking about.