Not Stopping @i.ua

Blocking that domain works on a clean test site, so most likely you have a plugin or a theme feature that’s preventing it from running OR the bots are getting around the registration form.

You can test by going to your own site, logged one and try to register as [email protected]

Then you’ll have to look through your plugins and see if any work with registrations and disable them to test.

I also use CM E-Mail Registration Blacklist plugin to stop free email account from registering.

Then the issue is likely that these two plugins aren’t playing well together.

I deactivated the other plugin. I’ll let you know if I still get them.

Just checked emails and there is still registrations going through for that domain. What else can I do?

Did YOU test?

That is did YOU try to create an account with the domain?

No, I have not as that won’t stop the bots from creating accounts. I get notifications every time an account is created with their credentials. It is still happening.

The point of YOU testing is for YOU to see if it’s actually bots using the registration form at all.

There are, after all, other ways to register accounts, and if your install has left one of those open or has a backdoor, then the plugin doesn’t matter.

So please, humor me. Log out, go to the registration page, and try to make an account a [email protected] and see what happens.

I just tested it and the registration went through without a hitch with an email using @i.ua

I can’t reproduce this ?? It works on a clean machine, so I can only say that you have ‘something’ conflicting. You’ll have to debug it the usual way

1) Disable everything and change your theme to 2017
2) Enable this plugin and see if works
3) Keep enabling plugins one and a time and test

It sucks, I know, but I can’t be expected to read minds ??

Rude. No one is asking you to read minds, just fix your plugin.

If it only works on CLEAN sites with zero other plugins, then your plugin is useless to most people. I’m uninstalling.

The plugin works, its just conflicting with something special that you have. Which YOU have to test to determine what, since I don’t know what you have installed.

Again, I know it sucks, but that’s how you debug WordPress conflicts. Best of luck.