• Resolved islp

    (@islp)


    In the Settings (All options) there’s a section labelled

    Immediately block the IP of users who try to sign in as these usernames

    This is very useful, but I receive lots of attempts from a unique domain, with different usernames, eg.

    [email protected]
    [email protected]
    [email protected]
    etc.

    Is there any way to block users from a particular domain?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support wfpeter

    (@wfpeter)

    Hi @islp, thanks for your question.

    As we don’t allow wildcards in “Immediately block the IP or users who try to sign in as these usernames” to configure something like *@domain.com, you’d have to pick specific ones that don’t exist as valid users.

    The catch-all would be enabling “Immediately lock out invalid usernames”, although bear in mind something as simple as a mistype would result in a block. We generally dissuade customers with forums, e-commerce stores, etc. from using this setting as it’ll increase legitimate users being blocked. It may be suitable if only you and/or a few other administrators have access though.

    If you think this would be a valuable feature for the rest of the Wordfence community, by all means highlight your use-case to feedback @ wordfence . com.

    Thanks,
    Peter.

    Thread Starter islp

    (@islp)

    @wfpeter Thanks for your kind reply. I understand this can be a very specific case. I see there are lots of plugin extending other plugins. Would it be possible to extend WF with this functionality? I can eventually code it myself, but I wanted to know if there’s some kind of hook or filter available in WF.

    Plugin Support wfpeter

    (@wfpeter)

    Hi @islp,

    At the moment, we only provide documentation for hooking into importSettings() and whitelistIP()https://www.wordfence.com/help/advanced/wordfence-api/

    Other developers may have written custom solutions to operations they’d like to hook into and may have documented or blogged about them. However, we’re unable to provide any support for custom code because our own future plugin updates may cause some to break and we’re unable to follow-up on potential fixes.

    Thanks again,
    Peter.

    Thread Starter islp

    (@islp)

    @wfpeter ok, thank you

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.