In short. A Hostinger CDN client must run the JavaScript check and retain the verification cookie to reach website content.
Definition: Hostinger CDN browser verification is a short browser-side check shown as “Checking your browser” before the CDN allows access to a website. A client must run the JavaScript check, allow the verification cookie to be stored, and send that cookie on later requests during the verification period.
Key facts
- Hostinger says the page checks browser capabilities and risk signals, runs automatically, and usually takes a few seconds. It protects against DDoS attacks, scrapers, and malicious bots in the browser verification documentation.
- A successful check stores a verification cookie. The visitor then continues to the website without seeing the page again for the duration of the verification.
- A client that fails the check remains on the verification page, leaving website content inaccessible. Hostinger gives most automated bots as an example.
- MDN describes a cookie as data that a server sends to a browser, which can store it and send it back to the same server with later requests in its guide to using HTTP cookies.
What does the client have to do?
The client first has to load the verification page as a browser that can execute JavaScript. Hostinger describes the test as a short JavaScript check that evaluates browser capabilities and risk signals. The check runs automatically, so a normal visitor lets it run without solving a visible puzzle or submitting a form.
Hostinger's visitor instructions reduce the practical requirements to three checks: enable JavaScript, allow cookies for the website, and reload the page. A privacy extension that blocks the check can therefore prevent completion even when the browser otherwise supports JavaScript. Hostinger says that strict privacy extensions may require an exception for the website.
What does the verification cookie change?
The verification cookie records that the check succeeded for the browser. Hostinger says the visitor continues to the website without seeing the verification page again for the duration of the verification. The page gives no cookie name or fixed duration, so both values remain unspecified.
MDN explains the HTTP state involved. A server can send a Set-Cookie response header, and a browser usually returns stored cookies for the current domain in a Cookie request header. The general exchange has this form:
Set-Cookie: <cookie-name>=<cookie-value>
Cookie: yummy_cookie=chocolate; tasty_cookie=strawberry
Hostinger's verification cookie is the product-specific result of the JavaScript check. The generic HTTP mechanism explains why a client that accepts the cookie can continue on subsequent requests, while a client that discards it can be challenged again.
What happens when a client fails the check?
Hostinger states that clients unable to complete the check remain on the verification page, with website content out of reach. This behavior applies to clients with JavaScript execution disabled, clients that discard the verification cookie, or clients prevented from completing the browser interaction by a strict privacy extension. The first two conditions follow from Hostinger's documented requirements; the extension case is explicitly listed in its visitor guidance.
The result is different from the documented treatment of verified search engine crawlers. Hostinger says Googlebot and Bingbot are identified separately and bypass the browser verification page under normal settings. A generic automated client therefore cannot assume that sending an ordinary HTTP request will produce the same result as a browser that completes the check.
How can a stuck visitor test the client?
The documented sequence is short: enable JavaScript, allow cookies for the site, and reload. If the page keeps reappearing, Hostinger recommends trying another browser or network and contacting the website owner when the issue continues. These steps test whether the client can execute the check and preserve its result.
Related terms
- How do I check whether a CDN blocked an AI crawler?
- Can JavaScript Detections be turned off while Cloudflare Bot Fight Mode is enabled?
- Is a bot name in a server log enough to identify its operator?
FAQ
Does a client need to click a button?
No visible action is required for a regular visitor. Hostinger says the check runs automatically and usually takes a few seconds. A client still needs JavaScript and cookies enabled.
What if cookies are blocked?
A client that discards the verification result described by Hostinger can see the verification page again. Allowing cookies for the website is one of Hostinger's stated checks for a stuck visitor.
Does every automated client receive the same treatment as Googlebot?
No. Hostinger documents separate identification for verified crawlers such as Googlebot and Bingbot under normal settings. It says clients that fail the check remain on the verification page.
Sources
- Hostinger, "Hostinger CDN: The browser verification page", 15 September 2026
- MDN, "Using HTTP cookies", 17 September 2026
Check how a page reads to answer engines. Open the GEO score analyzer