Knowledge base

Technical writing for people who have to fix it.

Eight articles on the controls this product measures and the method behind it. Each one is written for a specific question, links to the authoritative standard, and avoids restating the same introduction in different words.

Guides

How the controls work in practice.

Fundamentals, email authentication, DNS, infrastructure and web configuration — each explained from first principles rather than from a vendor checklist.

Editorial standard

What this section will not do.

A knowledge base is only useful if it says something. These are the rules the articles follow.

  • No keyword fillerEvery article answers a question someone would actually ask, and links to the RFC or vendor documentation rather than paraphrasing it loosely.
  • No invented authorityNo fabricated citations, no made-up statistics, no claims of testing that did not happen.
  • No disguised product pitchArticles explain the topic first. Where the product is relevant, the link is explicit.
  • Corrections welcomeIf something here is wrong or out of date, the contact form reaches the maintainer directly.

Where to start

If you are new to this: begin with the external posture assessment definition, then read the SMB exposure survey.

If you are fixing email: go straight to SPF, DKIM and DMARC — it is the highest-value gap in most small businesses.

If you are evaluating the product: read the posture score article, then compare it with the methodology.

Want to see the method applied to a real domain?

The recorded assessment shows every finding with its evidence, score and timestamp.