Press and Hold to Confirm You Are a Human: Loop Fixes

The "Press & Hold to confirm you are a human (and not a bot)" page is HUMAN Security's Human Challenge. A site shows it when it has scored your session as possibly automated. Hold the button steadily until it completes. If the check loops, the cause is usually blocked JavaScript or cookies, a browser extension, a flagged IP, or automation software on the device.

What is the "Press & Hold" check?

The "Press & Hold" check is HUMAN Security's interactive bot challenge. HUMAN's documentation (as of October 2026) describes it as "a verification system that displays an interactive challenge to confirm users are human rather than bots. The core interaction involves a Press & Hold mechanism."

The default page uses these strings:

• Header: "Before we continue..."
• Message: "Press & Hold to confirm you are a human (and not a bot)."
• Button: "Press & Hold"
• Failure text: "Please try again"
• A Reference ID printed on the block page

You may know it under an older name. PerimeterX merged with HUMAN in July 2022, and the combined company kept the HUMAN name (Help Net Security, July 28, 2022). People still search "PerimeterX captcha" for the same page. Walmart's block page shows a similar check that reads "Robot or human?" and "Activate and hold the button to confirm that you're human." The fixes below apply to both.

Why does a site show the Press & Hold check?

A site shows the Press & Hold check after its bot detection rated your session as uncertain. The hold is not a puzzle you can fail by being slow. HUMAN does not publish how the hold is scored, but it works as a second look: the page's script is running in your browser the whole time, and the result goes back to the site with whatever it observed.

You pass when the session adds up to a normal browser on a normal connection. If it does not, the button can fill completely and still return "Please try again."

Why does Press & Hold keep looping or failing?

Test the causes in this order. The cheapest checks come first.

1. Releasing too early. The bar resets if you let go, move the pointer off the button, or your finger shifts on a touchscreen.
2. JavaScript or cookies blocked. HUMAN requires both. Without JavaScript the challenge cannot run, and with cookies blocked, expect the check to keep coming back. HUMAN's troubleshooting for blocked users covers disabled JavaScript, browser extensions and cookie support.
3. Extensions. Ad blockers, script blockers and privacy extensions can stop the challenge script or the request it sends back.
4. A VPN or datacenter IP with a poor reputation. Bot-detection systems generally weigh IP reputation. VPN exits and hosting ranges carry a lot of automated traffic, so sessions from them often start with lower trust. This is how the category tends to work, not a documented HUMAN rule.
5. Automation tools on the device. Browser automation frameworks, auto-clickers, macro tools and remote-control software can change what the browser reports during the hold.

How do you get past the Press & Hold check?

You get past the Press & Hold check by holding it correctly from a clean browser on a reputable connection. Work through these steps until one clears it:

1. Hold steadily until it completes. Press and keep pressing. Do not drag. On a trackpad, physically click and hold rather than relying on tap-to-click.
2. Allow JavaScript and cookies for the site. In strict privacy modes, add the site as an exception.
3. Open a private window with extensions disabled and load the page again. If it passes there, turn your extensions back on one at a time to find the one causing it.
4. Try another network. Turn off your VPN. If you are on office or public Wi-Fi, switch your phone or laptop to mobile data. Check what kind of IP you are on before and after the switch:

5. Use the accessible option if the site offers it. When a site turns on HUMAN's Enhanced Accessibility Mode, the challenge supports Tab-key navigation and screen reader messages. It can also offer an email-based alternative with temporary codes, so you do not need to hold anything.
6. Contact the site with the Reference ID. If nothing works, screenshot the block page, including the Reference ID, and send it to the site's support. The ID lets them find your blocked request.

For deeper diagnosis, the Browser Fingerprint Test shows what your browser reports. A different check needs different fixes. If you are stuck on Cloudflare's checkbox instead, see the Cloudflare "Verify you are human" loop. Google's invisible scoring is covered in reCAPTCHA v3 score.

Why does switching to mobile data often clear the loop?

Switching to mobile data is a useful test, and it often clears the loop. Mobile carriers put subscribers behind carrier-grade NAT (CGNAT), so one public IPv4 address serves many phones at once, and a site that hard-blocks a carrier IP blocks real customers along with it. How much weight a given site puts on that is the site's own decision.

The switch helps often, not always. A mobile IP does not fix blocked cookies, a misbehaving extension or automation software. Those signals travel with the browser, whatever the network.

VoidMob's proxy exits work the same way. Every exit, in the shared pool and on dedicated devices, is a real 4G/5G device on a consumer carrier connection. Its public IPv4 address sits behind the carrier's CGNAT and is shared with that carrier's ordinary subscribers.

What if you hit Press & Hold while running automation?

Scrapers, test suites and browser agents hit the Press & Hold check for the same reasons people do, plus the automation signals listed above. The mobile proxy guide to CAPTCHA challenges covers how IP type, fingerprints and request pacing affect challenge rates. If you are choosing infrastructure for a collection job, see mobile proxies for web scraping.