security.txt (RFC 9116) in Browser automation and web data
It tells a researcher where to report a vulnerability instead of guessing.
7 of 26 vendors we measured here publish it, that is 27%. Last checked 2026-09-06.
27% here against 12% across every category we measure. Browser automation and web data sits above the overall share for this criterion.
Back to security.txt (RFC 9116) across all categories, or to Browser automation and web data.
Published
Served at /.well-known/security.txt.
No security.txt found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| Anchor Browser | 1 address checked |
| Axiom | 1 address checked |
| Bright Data | 1 address checked |
| Browser Use | 1 address checked |
| Browserless | 1 address checked |
| Hyperbrowser | 1 address checked |
| Oxylabs | 1 address checked |
| ScrapeGraph | 1 address checked |
| ScraperAPI | 1 address checked |
| Scrapfly | 1 address checked |
| ScrapingAnt | 1 address checked |
| ScrapingBee | 1 address checked |
| Scrapingdog | 1 address checked |
| ScreenshotAPI | 1 address checked |
| ScreenshotOne | 1 address checked |
| Scrnify | 1 address checked |
| Steel | 1 address checked |
| Thum.io | 1 address checked |
| Zyte | 1 address checked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
None. Every vendor here was measured for this criterion.
Found something we missed? Tell us and the next run picks it up.