Handle removal requests entirely through the site. about hstspreload.org HOT 4 CLOSED

Will you be performing the verification manually or automated for the removal of domains from the preload list? If you are going to automate the process, will it perform email verification to one of the following email addresses: [email protected], [email protected], [email protected] and [email protected]?

The current removal procedure is easy to automate without an email check: verify that the site is sending an HSTS header without preload.

As for the future, TBD. I don't want to reimplement entire parts of domain validation.

Are you going to allow this method for API use to selected domains like cloud.infinitude.me.uk?

Probably not. The preload list is basically still experimental, and non-canonical layers of abstractions are problematic for us right now (a major reasons sites need to be removed is because they were following third-party advice). It's better to encourage stateful interactions with the preload list to go through hstspreload.appspot.com .

from hstspreload.org.

Will you be performing the verification manually or automated for the removal of domains from the preload list? If you are going to automate the process, will it perform email verification to one of the following email addresses: [email protected], [email protected], [email protected] and [email protected]?

Are you going to allow this method for API use to selected domains like cloud.infinitude.me.uk?

from hstspreload.org.

This will probably be obsoleted by #50.

from hstspreload.org.

We've automated as much as we can, for now.

from hstspreload.org.