I guess that's a case for: "That's not a bug, it's a feature!" .
You could create filters to check for gibberish patterns, but what if someone really has an email that looks like that?
For instance, if you try to create an email like this "dufgfjfhfhfh@outlook.com" on Google or Hotmail, you could still create one, and it would be a "real" email address.
As suggested by @sitouzani and I've also mentioned this before somewhere, the best way of dealing with spam registrations would be to have Social Media logins only, and remove the Q2A registration field. Let the big dogs handle the spam, as they have teams for it.
But if you want to keep the Q2A registration field in, you could use a combination of plugins like:
Q2A Honeypot Question2Answer AntiBot Captcha SRS - SPAM Registration Stopper
As suggested on this quetion: Stop spam with registration field.
Welcome to the Q&A site for Question2Answer.
If you have a question about Q2A, please ask here, in English.
To report a bug, please create a new issue on Github or ask a question here with the bug tag.
If you just want to try Q2A, please use the demo site.