> how do you ensure that they are indeed scraping and not just making up spam? For TLS 1.1 (and supposedly "TLS 1.2+" since https://github.com/tlsnotary/PageSi

> how do you ensure that they are indeed scraping and not just making up spam? For TLS 1.1 (and supposedly "TLS 1.2+" since https://github.com/tlsnotary/PageSigner/commit/4e12573 https://github.com/tlsnotary/PageSigner/commit/4e12573): https://tlsnotary.org/pagesigner https://tlsnotary.org/pagesigner For TLS 1.3 there's also TLS-N from https://eprint.iacr.org/2017/578.pdf https://eprint.iacr.org/2017/578.pdf but it requires a cooperating server: "TLS-N generates non-interactive proofs about the content of a TLS session that can be efficiently verified by third parties and blockchain based smart contracts. As such, TLS-N increases the accountability for content provided on the web and enables a practical and decentralized blockchain oracle for web content. TLS-N is compatible with TLS 1.3 and adds a minor overhead to a typical TLS session. When a proof is generated, parts of the TLS session (e.g., passwords, cookies) can be hidden for privacy reasons, while the remaining content can be verified."