Waiting room · Queue-it
Queue-it
Difficulty 3/5
A virtual waiting room, not a bot blocker. It does not care what you are — it cares that you wait your turn and hold the token.
- TLS fingerprinting
- JS challenge required
- Behavioural scoring
- IP reputation weight: low
How it decides
-
A pre-origin redirect to a queue page that issues a signed token at a scheduled time.
-
Position is bound to the token; the token is bound to the session.
-
Frequently paired with a real bot vendor behind it — the queue is the outer layer only.
What you see when it stops you
- A redirect to `*.queue-it.net`
- A `Queue-it` or `QueueITAccepted-*` cookie
- A waiting-room page with a position counter
Signatures the detector matches
Publicly observable artefacts Queue-it sends to every visitor. Paste a response into the analyser and these are what it looks for.
| Where | Signal | Weight |
|---|---|---|
| Cookie | Queue-it cookie | 70 |
| Cookie | QueueITAccepted-* token cookie | 75 |
| Page markup | queue-it.net waiting room | 70 |
What actually gets through
-
Static ISP addresses. What matters is holding one identity for the entire wait, not looking like a new visitor.
-
Never rotate mid-queue — you lose the token and rejoin at the back.
-
Long sticky sessions and a stable browser profile per queue slot.
-
Identify what sits behind the queue; that is usually the real obstacle.
Hosts on record running it
From the detector's curated database. Observed, not live — stacks change, and large sites often run different protection per market.
Not sure this is what
is blocking you?
Paste the response you actually got. The detector names the vendor from its own headers, cookies and challenge markup — no account, nothing uploaded.