Thanks for your question. > Let's Encrypt together with tools like Cerbot have brought easy to use proof of domain ownership to countless sites. Why wouldn't s

Thanks for your question. > Let's Encrypt together with tools like Cerbot have brought easy to use proof of domain ownership to countless sites. Why wouldn't services that want to verify domain ownership use that? I think the answer to this question, is the same as the answer to: "Why don't service providers already use LE and Certbot to verify domains, instead of DNS TXT records?" I don't immediately see how it would be possible for a service provider like Google or Facebook to use Certbot or LE to verify domains for users. Could you explain that? I see how they could use the same methods (HTTP-01 and DNS-01) but that's what service providers are already doing. If it's possible in some way I haven't considered, I'd guess it's not used because by service providers because it creates more friction than current methods. > Even if centralization of domain validation is something you care about Could you explain how you consider this centralised when these records are stored in DNS? > I wouldn't want that centralization to happen by a project for a company focused on collecting data about businesses. I think you're talking about my company NUM Technology Ltd [1] and our laughably ambitious plan to organise all public data about all businesses into machine-readable format via DNS. You're right this involves collecting data, but only public data on the web. Consider it as a way to fetch a particular piece of data from Common Crawl in 15ms. 1. https://www.num.uk https://www.num.uk 2. https://www.numprotocol.com https://www.numprotocol.com Both sites in urgent need of an update.