Download websites that use Queue-it

About Queue-it

A waiting room is a confession about traffic. Nobody integrates one unless they expect, at some point, more demand in a minute than their checkout can absorb, so finding Queue-it on a domain tells you something quite specific about the business behind it. The site sells things that sell out, or it opens registrations at a fixed hour, or it has already been knocked over once and does not intend to repeat the experience.

Queue-it comes from Queue-it ApS and is licensed as Proprietary software, delivered as JavaScript in the visitor's browser and integrated at the server or the edge where a site needs it deeper in the stack. The product goes back to 2010. Our catalogue files it under Performance, which is less a judgement than an admission that traffic shaping for scarcity events does not fit the usual buckets of analytics, commerce or hosting.

As of October 2026 we match the fingerprint on 87 sites. Queue-it is harder to observe than an ordinary tag, for a structural reason: a waiting room is dormant almost all of the time. On a normal day the site behaves like any other, and depending on how the integration was built the browser side evidence can be absent entirely until an event begins. Edge and server side connectors leave nothing at all in the delivered page. Our count therefore leans toward installations that keep a visible snippet in place between events, and the customer base is larger than the visible footprint.

What makes the file worth downloading is not the total but the composition. Domains that pay for queueing fall into recognisable groups, ticketing and live events, limited release retail, exam and appointment booking, public sector registration, and anything else where supply is fixed and the announcement time is known in advance. A list of them is close to a list of businesses whose revenue arrives in spikes, which is a population that sellers of capacity, bot mitigation, payment scaling and fraud screening all want and none of them can assemble by checking domains one at a time.

Repeat exports supply the other half of the picture. A domain that appears once and vanishes was probably covering a single campaign, while a domain that persists across snapshots has built queueing into how it operates. Separating the campaign users from the permanent ones is only possible with dated copies of the whole list, and the difference matters, because the two groups buy very differently.