mjem

@wfalaa, thank you for your response.

Honestly when all this happened it shook my trust in Wordfence, but after reading your reply I feel relieved. I am glad that I was previously under the correct impression.

@mountainguy2, @bluebearmedia – thank you for your replies as well. It was just crucial for me to hear a legit response from Wordfence.

@bluebearmedia, thank you for your input as well.

I appreciate that you both took the time and made the effort to share your assessments with me. The matter is being dealt with holistically.

1. The initial question, while somewhat esoteric in nature, is for me crucial to understand correctly. I need to have as thorough a grasp as possible of how much of the website security Wordfence covers and how much troubleshooting information a Gravscan provides, and in all fairness no one can answer that question on the developers behalf. I don’t expect this to be some “magical” futuristic technology, but I do need to understand what it does and does not do.
2. To clarify my reply to MTN; the cause of the breach is not the focus of this topic, to what extent Wordfence prevents breaches in general is and a vague reply like “it does what it does” is really a waste of everyone’s time.
3. No one who posts here has the legal right to provide communication on behalf of Wordfence, except those individuals who have been tasked to do just that, and they operate within a specific framework of what can and cannot be said, as any answer they provide here is public domain. So I know that when I get an answer from them that it is an accurate and well thought-through response that I can base my actions on going forward.

That is the longer version of what I tried to summarize in my previous response.

@mountainguy2, thank you for your input.

I apologize for creating the wrong impression in my initial post. I’ll address any future requests aimed at the Wordfence support team as such to avoid any confusion as to whom I’m talking to.

My bad.

Hi, thanks for the reply. I’m dealer with something nasty here but I’ll post separately about that.