-
Notifications
You must be signed in to change notification settings - Fork 5
Description
Rumour has it that ICANN is considering another run of the new gTLD program.
Last time around, Google registered .app and runs it with an additional semantic: all domains in that TLD are automatically on the HSTS preload list, effectiely enforcing HTTPS for any server with an .app domain.
What if something similar were done with a privacy focus? For sake of argument, let's say .priv1 is registered, and there's agreement that browsers will not allow any third-party requests from those domains. The registrar might also insert contractual terms that limited first-party tracking as well.
Sites with .priv domains could then beliveably market themselves as privacy-focused, giving them an advantage with privacy-concious users / customers.
This would also provide an opportunity for browsers to try out new techniques for privacy in a 'sandbox' that's already privacy-focused.
Just thinking out loud here - any interest? Obviously it'd need good browser support. Best path forward might be to define an opt-in signal for sites first, just like HSTS did.
Footnotes
-
I suspect
.privis not the right name here, but let's not bikeshed that at the moment ↩