provide blocking pages with correct statuses

I got this feedback from my hosting provider related to an issue with how CleanTalk Security is handling errors, can you please review and update the plugin so this issue does not happen anymore?

======

Jordan, I see the problem here with plugin itself.
I’ve logged in and blocked my IP and then when I opened your website I’ve got blocking page – the problem here is that your website (or plugin security-malware-firewall) returns blocking page with Status 200 OK which is incorrect.

All blocking pages should be returned with 403 Status code – Permission denied, or 429 or some kind another status.
These statuses are not cached by our system.

Status 200 means okay and become cached.
So this is how the plugin works.

So my recommendation here is contact with plugin’s dev team and ask them to provide blocking pages with correct statuses – for example 403 which will not be cached by our system and only blocked user will get it,

Also as a solution for blocked visitors they can return http header below on blocking pages:
cache-control: no-store, no-cache, must-revalidate
but the correct solution is  return correct status code for blocked visitors