Measured numbers
Counted by the collection, not written by hand. A figure we cannot support is left out rather than shown as zero.
- Pages
- 9
- 18th of 18 measured in Tech/AI, by sitemap URLs
- Page count over time
- 8 → 9 pages measured, 30 Sep to 25 Oct
- Languages
- English
- Deploys
- 3 in the last 30 days
- Last deploy 22 Oct 2026. From the public status feed
- llms.txt
- Published
- llms.txt 1.5 KB · llms-full.txt 25.1 KB
- Sitemap
- Listed in robots.txt
Tech and AI search
Read from the live site on 2026-10-23: its homepage, robots.txt and llms.txt. A line we could not read is left out.
- Built with
- Astro
- Read from the homepage markup
- Structured data
- Organization, SoftwareApplication, WebSite
- schema.org types on the homepage
- AI crawler access
- Allows all 11 major AI crawlers
- From the site’s robots.txt
- llms.txt link depth
- 9 page links
- Markdown links in the site’s llms.txt
How it is built, by role
The same roles apply across the whole collection. Nothing in this block is specific to this site; what the site says about itself is quoted word for word below it.
- 1
Edge network
Visitors reach a site through an edge layer: a content delivery network with a web application firewall in front of it.
- 2
Application host
The edge talks to an application host that serves the site and renders its pages.
- 3
Data
What the pages show comes from a relational database or, for a site pre-rendered at build time, from data files built into its release.
- 4
Scheduled measurement
The collection measures its sites on a schedule: content dates and site health nightly, page counts read from each site’s sitemap weekly. Every reading is kept with its date. A site too large to re-walk is not re-measured, and shows no trend.
- 5
Public status feed
A monitoring panel sends a signed report on uptime, deploys and backups once a day, and the Operations page publishes it. A figure on this page that comes from that report says so.
In the site's own words
Each passage is copied unaltered from a page the site publishes, with the address it was taken from and the date we took it. We add nothing between them.
“294 checks across 11 categories, 66 CLI subcommands.”
“Local. Runs on your machine; there is no hosted scanning service.”
“The vulnerability feed is aggregated nightly from up to 8 public sources (NVD, MITRE, GHSA, OSV, Wordfence, WPVulnerability, Patchstack, CIRCL); per-source counts are published in the feed header.”
“A default (passive) scan can contact third parties beyond the target: crt.sh and other certificate-transparency services, an RDAP service, api.wordpress.org, api.osv.dev, and, when the JSON report is produced, CISA KEV and EPSS (api.first.org). The CVE feed is fetched from GitHub. These receive the target hostname, detected component names or CVE ids, not site secrets.”
“OWASP and MITRE ATT&CK tags are on nearly every check; CWE and D3FEND tags are on about 189 of 294.”
“WPSecScan is an auditing tool: it is not a firewall and does not remove malware.”
“Defensive use only. Use it on sites you own or have written permission to test.”
Screenshots
Timeline
8 → 9 pages measured, 30 Sep to 25 Oct
| Date | Pages |
|---|---|
| 2026-09-30 | 8 |
| 2026-10-10 | 8 |
| 2026-10-18 | 9 |
| 2026-10-25 | 9 |
- 30 Sep 20268 pages
- 10 Oct 20268 pages
- 18 Oct 20269 pages
- 25 Oct 20269 pages