garypayne

Just to update you, since moving to 4.0.3, and making a few other settings changes in Wordfence (happy to explain what these are if asked to), not having the 255.255.255.255. any more and brute force attempts have dropped to a virtual zero – wonderful! Thank you.

Updated and will see what happens. Cheers

Yes, I do think that it would be a useful asset to web administrators and indeed marketing/sales teams, that as the data is being collected by the definition that it appears on the page anyway, that if this was also captured into a table within the database, this would give access to that data, beyond the current period.

So my suggestion to enhance the Wordfence plugin is:

1. Create a data table to capture the detail currently shown on the all hits pages;
2. Give web administrators the option of whether to capture ‘all hits’ or ‘only humans’ or ‘Login and Logouts’, etc.;
3. Give web administrators the option of collecting up to a maximum quantity of records or maximum number of days, i.e. say up to 10,000 records or up to 3 days, I think the former limit to 10,000 would be better.

A button to export the data to a CSV or Text File could be given for the web administrator to take the data out of the database for analysis, etc.

This would help web administrators, marketeers, sales, understand where both positive and negative hits are coming from, could be very useful.

Hope this helps and that you might consider it?

Cheers, Gary

I understand that however, could this make use of rolling database stored log too?

The page still limited but the log on the database not limited or restricted by the administrator to a set number of days records?

That would be really useful when interrogating and deciding to block or not networks.

Your thoughts?

I still need guidance on whether to block or not? Anyone any views?

I guess that it is not valid however, it is the one that is reported by Wordfence.

30 invalid username login attempts by the user at this ID address and the system is not locking them out despite the setting being checked to immediately lock out invalid usernames and for 10 days.

Reluctant to block it as it is also a private network (internal) IP address.

Thanks for your help.