Mix Honeypot and Regcheck module?
While it probably will do no harm, there is not much point in using both.

Regcheck is a small and super simple module that will add an invible (to humans) checkbox on your registration form. Bots will check this, and when the bot submits the form, it can be rejected.

Honeypot is a larger and more complex beast that do several thing to block 'bots. One of these thing is to let you add an invisible (honeypot) field to any form - including the registration form.  From the Honeypot docs:


  Honeypot form protection means that an invisible field is added to a form. If this invisible field is filled out (bots will usually put in a value), then the form will return an error. Normal users (read: human beings) won't ever see the field, so they won't fill it out.


If you install both, your registration form will have two invisble (to humans) fields.  There is little harm in that (having both installed will consume slightly more resources), but not much benefit either .

So I suggest you install Regcheck if you want a simple solution with minimal configuration just to stop 'bots from registering, and Honeypot if you want a more comprehensive anti-spam solution.

However, if you're looking for a solution that stops bots before they hit the registration form submit button, neither Regcheck nor Honeypot will help.  Both work by automatically dismissing registrations after they've been submitted.

If you want to block bots from trying to register, you can't do this by Drupal alone, but need to use webserver access rules.

There are projects, such as Project Honeypot (no relation to the Honeypot module) and Fail2ban  that will do this for you.

To set up a Drupal site to use the Project Honeypot blacklist of IP-addresses, there is also a Drupal module, http:BL.  AFAIK, there is no Drupal module for Fail2ban, but since it work directly with the the server, you don't need one.