What the standard files check tells you
A few small files at well-known addresses say a lot about how a site is run. A security.txt tells researchers who to contact about a vulnerability. An ads.txt lists who may sell the site's ad space. A humans.txt credits the people behind it. This check reads them all, validates the ones with a standard, and looks at a few things every home page should get right: mixed content, compression and caching.
What we check
security.txt (RFC 9116). We look at /.well-known/security.txt first and fall back to the older
/security.txt. We check that there is at least one Contact as a proper address, exactly one Expires date
in the right format that hasn't passed and isn't more than a year away, that the file is served over HTTPS as
plain text, that every line follows the Field: value form, and that a Canonical line lists the address we
found it at. A file signed with PGP is recognised and its signed text read; the signature itself isn't
verified.
ads.txt and app-ads.txt (IAB 1.1). We count the seller records, split them into direct and reseller,
read variables such as contact=, and list any line that doesn't follow the format.
humans.txt. Whether it exists. It's optional, so a missing one is only noted.
Soft errors. Many sites answer every missing address with their home page and a success status. We notice when a text file comes back as a web page and treat it as missing, so you don't get a false "found".
Mixed content. On an HTTPS home page, scripts, stylesheets, frames and forms loaded over plain HTTP are active mixed content, which browsers block. Images and media over plain HTTP are passive mixed content, which browsers upgrade or block. If your Content-Security-Policy asks browsers to upgrade insecure requests, we lower passive mixed content to information.
Compression and caching. For the home page and up to five of its own scripts, styles and images we check whether text responses over 1 KB are compressed with gzip, Brotli or zstd, and which caching headers they carry. Static files cached for less than an hour, or not at all, are noted.
Reading the result
The security.txt card starts with a verdict, such as "Valid, expires in 198 days", then shows where the file was found, how it was served and each field with its values. A smaller card covers ads.txt, app-ads.txt and humans.txt. The home page section lists any mixed content with the element and address, and a table with each response's encoding, size, Cache-Control and validators. Findings explain each problem, and the ones with fix guides link to them.
If some files couldn't be fetched, for example because the site was briefly busy, the result is marked partial and says which part is missing. The check is an error, and free, only when nothing on the site answered at all.
How we fetch
We fetch as DNSSuperBot, from our own servers, about a dozen requests at most, four at a time. When the site has no HTTPS, we read the files over plain HTTP and tell you security.txt should move to HTTPS. Every request counts toward a shared limit per host across all our users, so a site is never flooded.
Writing a good security.txt
Keep it short. Two lines are enough to start: a Contact with an email address, and an Expires date less than a year ahead. Add Preferred-Languages, a link to your disclosure policy, and a Canonical line with the file's own address. Put a reminder in your calendar before the expiry date; an expired file is worse than a missing one, because it suggests nobody reads the contact anymore.