recaptcha: Recaptcha v3 always returns a 0.1 score

Would be nice to have an official Google response…

the recaptcha code the end user uses in his browser is always javascript… so that doesn’t really matter now does it… and if you had read entire topic you would also have read it works for two weeks, and then suddenly it doesn’t, and then it does again… and then doesn’t… without changing any code… so the problem more seems to be an unreliable recaptcha solution, than any form of misuse of the code… if it was as easy as using double id’s there wouldn’t be a problem…

https://stackoverflow.com/questions/55521795/google-recaptcha-v3-returns-success-as-false

I read this topic 2 months ago when I really needed help with my recaptcha. There’s an easier way to apply recaptcha with php and javascript. Did you ever think of just rewriting the code? Or changing the format of the code? Perhaps think of a different method to get recaptcha to work because obviously, your first method isn’t. I mean, you’re a programmer. Problem solve. You’re not going to be able to google everything, a lot of this stuff is testing things and figuring it out on your own. Just have to figure out what works best.

With that aside, there has to be a reasonable solution as to why the code is doing that. Been using recatpcha for months and it works fine. When was the last time you tested your code?

Well its happening again. 2 weeks in production and suddenly ReCaptcha keeps returning 0.1 for most of the requests even genuine ones. Customers are complaining. Apparently the machine learning is not good enough yet. I cannot keep creating new keys, just to keep the ReCaptcha performance up to scratch. V3 doesn’t seem ready yet. Also I use actions, but most of the sites do not pick the actions up in the admin panel. Some do, but then just one action of the 4 I use… This is not usable sadly… It looked very promising, but its not delivering at the moment.

same here. It’s still going on right now.

I’ve been using reCAPTCHA v3 since 2019 and have never had it used to work perfectly. We used to get scores of 0.7 or 0.9. However, there was a sudden increase in the number of requests evaluated as 0.1 or 0.3 since April 15. We found that these were normal requests made by humans.

I’ve been using recaptcha V3 now for just over a year and it’s really flaky. At 4am on Thursday (15th April 2021) we started having an influx of users who would normally be getting scores of 0.7 - 0.9 were getting 0.1 - 0.3. The ramp of users getting a low scores has dropped slightly but still getting high numbers. These are genuine users who aren’t using a bot to use the login page.

Does anyone know if there was there some sort of outage which was causing this issue? Just seems like it’s getting worse and no help from Google to guide us to get our customers to 0.9 or the magical 1 score!

Looking at the documentation and the quick video regarding the enterprise offering, the admin console looks worse and it will be the same ML underneath, just get an email address for support that might work…

many people are talking about this problem. but there is no reaction from recaptcha team. what a support! thanks

The comments on here seem like it’s RIP to reCAPTCHA v3. This issue was opened a year ago and it hasn’t been resolved yet. 💀

Closing old issues that are not related to the PHP client code.

We are also seeing strange behaviour on our enterprise recaptcha where legit requests from Iphones are being scored as 0.1 (or 0.3 if users happen to be logged in their google acocunt within the iphone’s browser).

Working perfectly fine for all other OS and browsers…is anybody else seeing this behaviour?

V3 is a marketing tool to get you to also install V2 😉

I feel like going back to V2 if the V3 issue is not resolved for localhost. It’s frustrating to test and fix if there is suddenly a low score. At least with V2 you can make sure you have a high score.

Sort of same problem here. Programmed ReCaptcha v3 into my own build multitenant framework and started implementing ReCaptcha for websites… yesterday it all worked fine; 0.9 for me typing and filling contact form, etc… But today I suddenly, and always, get a 0.1 score… even when using my iPhone instead of my laptop (same wifi IP), or disabling the wifi… (mobile provider IP) and this is when clearly showing i’m human by extensively using the mouse and navigating the website… typing in the forms instead of using the browsers autofill, but nothing helps getting the score up…

No, I didn’t change anything in the code between yesterday and today… And it worked perfectly yesterday… so something happened overnight at google? (additional scoring or tests or something?)

One other thing I noticed yesterday; when there’s a login form at the startpage, and one hasn’t got enough navigating on the website (because the only thing to do is fill in the login form), and the browser uses autofill, the score also always returns 0.1… so really not workable I would say…

I’m clearly human and filling in forms by hand, moving mouse, etc, but still I get a 0.1 ?!?

update; I normally use Edge, but just tried with Chrome to no avail… still the same result… 0.1 score…

update; just used a phone from another person; works fine… so I suggest putting some kind of feature in the admin screen to ‘unblock/reset’ a certain visiting ip address score if needed… so when a costumer comes to me with the message ‘I have someone who cant use my contact form on the website’, I have the possibility to ‘reset’ the build up score of a website visitor… because really… if this happens to legit customers of my costumers than I have a big problem… and meanwhile I cant do anything now! i’m implementing ReCaptcha in all my costumers websites, and cant do anything at the moment really being a bot who isn’t a bot… 😦 So I do not feel confident implementing this ReCaptcha v3 solution is the right thing to do at the moment…

All the tests I have done proves V3 is totally unreliable, not to mention it requires a complete revision of your business logic in many cases. You receive score varying from .9 to .1 over the same connection, same user agent, … When you want to protect a form that requires end-user input it is even worst. You receive timeout - sorry end-user may takes more than 1mn to fill-up their name, address, phone, … Implementing some cleaver logic to address such makes it spammer prone. Some browser are definitly unsupported, the code is negatively impacting performances (loading various fonts, and other third party resources. This code is useless, support non-existent, documentation fuzzy when not misleading…

I’d be quite keen to read some reviews or blog posts on someone who has successfully integrated reCAPTCHA v3 and have released it to production with a positive outcome. It does appear that people are reluctant to deploy this into a production environment at the moment, certainly, I am one of those people.

After change the key, it works at beginning. But i found that the score would continue to drop from 0.9 until 0.1, and then it would have been 0.1.

We also received reports that some frustrated users constantly blocked by reCaptcha V3. I checked their scores and they were receiving beween 0, 0.1 and 0.3. Some had tried different browsers with none success. With the information received so far, I suspect its something to do with the VPN their organisations are using, or the policies configured on their work computer. (One user had indicated that she was blocked by the captcha on her work computer, but was able to progress if using her personal computer.

Same here! suddenly I started getting 0.1 and 0.3 on lots of calls randomly 😕

Not sure if people are still having this issue but changing the action from homepage to submit fixed it for me. My check is not executed until the form is submitted however.

We are experiencing the same issue in production. The automated traffic from the malicious sources (doing constant unlimited request from one IP) got 0.9 scores, meaning, reCaptcha v3 is USELESS. There is no way to at least lower the score if the bot fraud traffic gets 0.9 all the time. What a mess Google!

https://www.hcaptcha.com (specifically the enterprise version, which includes scores and passive modes like v3) is a better idea. You can customize every aspect of the scores.

same here 😦 everything was working perfectly but suddenly 0.1, 0.3

Same issue here. A few months into production and my client’s customers are complaining about the failed captcha check. Legitimate human actions are getting a score of 0.1 and blocking users from doing anything (I was blocking anything under 0.3). I had to reduce it to only block a score of 0 for now which I fear may let some bots through. It seems this should automatically give the user a second chance with an “I’m not a Robot” checkbox if there are going to be so many false positives…

Ya, I ended up implementing both V2 and V3, so those that can use V3 continue to enjoy normal login, and those that are blocked by V3 are then presented with V2 images. 😅

I’m also facing the same issue for the past few days. It returns a low score of 0.1 when I test it in https://www.live.browserstack.com on iOS and iPad. But it returns a high score when I test the same in Google chrome on my windows machine.

The behaviour is very inconsistent. Seriously hope Google fixes it sooner.

I strongly suggest all of you to migrate to hCaptcha, they are highly compatible with reCaptcha but they care about the service.

I am not involved in any manner with hCaptcha, I didn’t know about them since 1 week ago and I’m neither a current hCaptcha customer, just did some experiments.

It’s very sad to notice how much Google ignores reCaptcha service.

Il giorno lun 31 mag 2021 alle ore 04:32 Phan Dat @.***> ha scritto:

Any update for this issue. I’m facing this problem today

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/google/recaptcha/issues/248#issuecomment-851125103, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNKU74M77XHQ5EOD6EKYX3TQLYLJANCNFSM4FPHDB5A .

also, recaptcha not always return 0.1 in my case, few of our users got 0.3. so, i think it’s still working.