Accessing websites via html regularly

I got my website shut down because of suspicious access to a certain file every few hours. I got that server recovered and I do understand that due to the way keybase works that's just how it goes. My suggestion is, just for http verification, when it invalidates, instead of completely invalidating it, publicly mark it as suspicious. May be problematic, but I had to abandon my proof because of that.

Start by tracing the HTTP verification flow that invalidates a Keybase proof after suspicious file access. Clarify whether a suspicious status can be exposed without accepting the proof, then define completion as preserving the security behavior while allowing the reported verification use case.

Written by the indexing model from the issue text.