SaaS Ranking

security.txt (RFC 9116) in SEO tools

It tells a researcher where to report a vulnerability instead of guessing.

4% here against 23% across every category we measure. SEO tools sits below the overall share for this criterion.

Back to security.txt (RFC 9116) across all categories, or to SEO tools.

Published

Served at /.well-known/security.txt.

VendorWhat we found
Moz https://moz.com/.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.

VendorWhat we found
AccuRanker 1 address checked
Advanced Web Ranking 1 address checked
Ahrefs 1 address checked
Botify 1 address checked
BrightEdge 1 address checked
Clearscope 1 address checked
Conductor 1 address checked
Dragon Metrics 1 address checked
Frase 1 address checked
Linkody 1 address checked
Majestic 1 address checked
Mangools 1 address checked
MarketMuse 1 address checked
Nightwatch 1 address checked
Ryte 1 address checked
Screaming Frog 1 address checked
Semrush 1 address checked
Seobility 1 address checked
seoClarity 1 address checked
Serpstat 1 address checked
Similarweb 1 address checked
Sistrix 1 address checked
Sitebulb 1 address checked
Sitechecker 1 address checked
SpyFu 1 address checked
Surfer 1 address checked
Wincher 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.

VendorWhat we found
OnCrawl The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.
SE Ranking The vendor’s server blocked or rate-limited our crawler, so this was not measured.

Found something we missed? Tell us and the next run picks it up.