Blockchain technology (which powers the Bitcoin) can easily be used to replace CAs, or provide an alternative which browsers acknowledge, provided enough site owners use it.<p>And going by the high issuance&#x2F;maintenance fee the CAs charge for issuing certificates, the industry is a sitting duck for disruption by a <i>Blockchain DNS&#x2F;CA app</i>.<p>I, as a site owner, can just sign my &#x27;certificate&#x27; myself and put it on the blockchain DNS&#x2F;CA app. The certificate will have my domain name, public key. And slso an additional field &#x27;ownership sign&#x27; which is something like <a href="https:&#x2F;&#x2F;&lt;my" rel="nofollow">https:&#x2F;&#x2F;&lt;my</a> domain&gt;.com&#x2F;ownership_sign.pem (which is signed by my private key).<p>So if I am the true owner, I can self issue as many certificates to myself as I please. Or there could be some forced limitation to prevent any scalability (<i>cough</i>) challenges.<p>So, the problem you have pointed out is not really with enforcing&#x2F;encouraging HTTPS, but with the entrenched CA bureaucracy. And I am really surprised, why is it not being disrupted already?