scan Failed
The scan has failed because we were unable to contact the Wordfence servers. Some sites may need adjustments to run scans reliably
The error returned was:There was an error connecting to the Wordfence scanning servers: cURL error 6: Could not resolve host: noc1.wordfence.com
Plugin Support
wfphil
(@wfphil)
Hi @scratchy101
It appears that you haven’t set up correct IP detection in our plugin yet.
Please send your Wordfence diagnostics report.
Update to the latest version of Wordfence if you haven’t already done so.
Go to the top of the “Diagnostics” tab on the Wordfence “Tools” page. There will be a “SEND REPORT BY EMAIL” button to send the diagnostics report. Enter wftest [at] wordfence [dot] com as the email and scratchy101 as the forum username please.
Once you have emailed me the diagnostics report can you reply here to let me know that it has been sent. This is important in the unlikely event that your installation of WordPress is having an issue with sending mail
Hi @editordev as per forum guidelines please open your own support topic.
Thanks for this reply. I know my WP installation can send email from your plugin as I just received this:
This email was sent from your website “West Coast Radio Sailing Club” by the Wordfence plugin at Wednesday 24th of June 2026 at 10:52:45 AM
The Wordfence administrative URL for this site is: https://westcoastradiosailing.ca/wp-admin/admin.php?page=Wordfence
A user with IP address 109.158.95.22 has been locked out from signing in or using the password recovery form for the following reason: Used an invalid username ‘gfdsagfds’ to try to sign in.
The duration of the lockout is 12 hours.
User IP: 109.158.95.22
User hostname: host109-158-95-22.range109-158.btcentralplus.com
User location: Ivybridge, United Kingdom
I’ve never received one like this before, despite the log showing many invalid username login attempts.
The diagnostics report has been sent as requested.
Plugin Support
wfphil
(@wfphil)
Hi @scratchy101
I tested it and I am locked out after three attempts for the username in your screenshot so it is working.
This suggests that either the Enable brute force protection switch was set to OFF at the time, or the IP address was added to the IP address allowlist.
