Domain "may be at risk of removal" when using the same configuration as it was accepted with

[jamieweb]

When entering one of my preloaded domains into the removal form, it returns with:

Status: jamieweb.net is currently preloaded, but no longer meets the requirements. It may be at risk of removal.

I have seen in #142 that there are known inaccuracies with this error message, however from reading the thread it is still not clear as to whether my domains are at risk of removal or not.

I am using exactly the same web server configuration and header as when the domains were originally accepted onto the list, and I have manually checked my domains against the submission requirements and continued requirements.

My config includes the header: Strict-Transport-Security: "max-age=63072000; includeSubDomains; preload", as well as serving a valid certificate, redirecting from HTTP to HTTPS on the same host, etc.

I've also queried the API, and as far as I can see there are no known problems with my domains:

$ curl https://hstspreload.org/api/v2/preloadable?domain=jamieweb.net
{
  "errors": [],
  "warnings": []
}

Is there really anything wrong with my domains, or is the error message simply inaccurate as discussed in #142?

Just to clarify, I am not trying to remove my domains from the preload list. I was just looking around the site, tried the form, and it has been showing the "risk of removal" message for a few months now.

Thank you!

[lgarron]

I believe this is a dupe of #142.

[jamieweb]

It could be, although #142 was originally about the location that the error message is displayed, rather than the meaning of it:

This message is clearly for the preload page rather than the removal page.

My issue is purely about the meaning of the error message, and whether it's an inaccurate error or not.

Thank you.