SaaS Ranking

security.txt (RFC 9116) in E-signature

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

33% here against 23% across every category we measure. E-signature sits above the overall share for this criterion.

Back to security.txt (RFC 9116) across all categories, or to E-signature.

Published

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

VendorWhat we found
Adobe Acrobat Sign https://www.adobe.com/.well-known/security.txt
Skribble https://www.skribble.com/.well-known/security.txt
Yousign https://youtrust.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
DocSend 1 address checked
DocuSign 1 address checked
Dropbox Sign 1 address checked
eversign 1 address checked
Sign.com 1 address checked
Signaturit 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
PandaDoc The vendor’s server blocked or rate-limited our crawler, so this was not measured.
signNow The vendor’s server blocked or rate-limited our crawler, so this was not measured.
SignRequest The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.

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