How AllRank collects and checks data

What gets collected, and how

Several passes run over the same list of boards, and they do not overwrite each other.

1. The seed. The census starts from outoutbid.lol’s public directory export, used under CC BY 4.0. That gives an address, a category, an entry price and, for most boards, a figure the board publishes about itself. Everything taken from it is labelled third-party sourced on the board’s page — never presented as this site’s own reading.
2. The sweep. Every address is then fetched from here directly, with a two-attempt retry and an http fallback before anything is written off. What comes back gives the status, the page title, the meta description, the payment provider loaded in the page source, and any money printed on the page. These are labelled first-party or automated observed.
3. The registry. Domains without a registration date are looked up in RDAP — the public record that replaced WHOIS — through each registry’s own service, using IANA’s bootstrap file. That took the coverage from 51% to 97% of the census. These are labelled registry verified.
4. The rendered read. A plain fetch sees nothing on a board that builds its page in the browser, and a third of this wave does. Every board that answers is then opened in a real browser, which reads the page as a visitor would, follows at most two of its own rules or pricing pages when no payment provider was visible, and photographs the boards with a complete file. Where the browser saw more than the fetch did, the board’s page says so and gives both character counts.
5. The mark. The board’s own icon is copied from the apple-touch-icon or rel="icon" it publishes, falling back to /favicon.ico on the same origin, and stored as a 128-pixel PNG. A bot challenge or a parking page is not used as a source — the same rule as the photographs.

The seven source types

Every value on every board page carries one of these, with a timestamp and a confidence mark. Where two sources disagree about the same field, both stay on the page. The newer one does not silently replace the older one — that disagreement is usually the most interesting thing on the page.

Reading a board's own counter

Most totals here come from the upstream directory. For the boards it cannot read — and for boards this site listed itself — the figure is read here instead, directly off the board's page, and marked first-party rather than third-party.

That reading is deliberately narrow, because a wrong figure lands in the total on the front page. It has to be a number the board itself labels as a total. A bid is not a total. A cap is not a total — “maximum $999,999 in total” is a limit on what one bidder may spend. A goal is not a total. And a figure a directory quotes about a board it tracks belongs to that board, not to the directory: “outbid.lol made $175K” printed on someone else's page is a fact about outbid.lol. Every one of those was a real reading this site made and then rejected.

What the money figures are, and are not

Every money figure on this site is what a board publishes about itself. It is not audited revenue, it has not been through anyone’s books, and a board that inflates its own counter is reported here at its inflated figure. That is why the field is called reported total everywhere and never verified revenue.

These four things are different, and this site keeps them apart:

• Publicly reported total — a number printed on the board’s own page.
• Observed board total — a floor summed from the rows a page happens to show.
• Owner-confirmed revenue — a figure whoever runs the board has stood behind, after a domain check.
• Payment-verified revenue — nobody has this, including this site. No board on file carries it.

Null is never zero. 215 boards publish no readable figure at all. They are excluded from totals and medians rather than counted as having taken nothing — treating them as zeros would understate the wave and libel the boards.

Totals only go up. Most of these boards let a bid stand forever, so a cumulative total says nothing about whether anyone is still bidding this week. A board reporting $6,000 may have taken all of it on day one and nothing since.

Currency

Boards price themselves in dollars, euros, rupees, reais, SOL, ETH and satoshis. Each figure is kept in the currency the board published it in — the raw string appears on every page. A rough fixed-rate conversion exists only so lists can be ordered and totals summed, and it is deliberately not shown as a converted figure anywhere:

1 USD = $1 · 1 USDC = $1 · 1 EUR = $1.08 · 1 GBP = $1.27 · 1 INR = $0.012 · 1 BRL = $0.19 · 1 SOL = $190 · 1 ETH = $3400 · 1 BTC = $62000 · 1 SATS = $0.00062

These rates are fixed, not live. Any board priced in crypto should be read as approximate on the sorting axis and exact only in its own currency.

How a board is called live or dead

Status is measured here rather than relayed. Each address is requested with a normal browser user-agent, following at most four redirects, with every hop re-checked, and a hard cap on how much of the response is read. A board is only written off after two failed attempts and an http fallback.

How rules get classified

A board’s own words — tagline, page title, meta description and the first several thousand characters of visible copy, taken from the rendered page where one exists — are matched against a published list of phrases per mechanic. A match records the phrase that triggered it, and that phrase is printed in the board’s evidence ledger, so a classification can be argued with rather than trusted.

Where nothing matches, a board is filed under single highest bid — the default shape of this wave — and the field is marked estimated, at low confidence. Around a third of the census sits in that bucket. That is a guess, and it is labelled as one on every page it appears.

How the trending order is calculated

The directory and trending page use this score, rounded to one decimal place:

2 × log10(1 + reported USD total) + 1.5 × log10(1 + source-directory clicks) + log10(1 + top bid in USD) + 0.5 if a bidder count is present + completeness ÷ 5.

Missing monetary values count as zero in this formula. Completeness measures available profile fields. The score measures prominence in the current dataset, not recent growth or advertiser returns. Sponsorship is not an input.

How profile scores are calculated

Each is a formula over the data, scored 0–5. None of them is an opinion about whether a board is good.

• Originality — 5 × (1 − similarity to the nearest other board in the corpus), where similarity is the overlap of distinctive words across every board’s copy. A board whose page reads like a copy of another board scores low by construction.
• Transparency — one point each for publishing a total, a top bid, a bidder count, an entry price, and at least two readable rules.
• Activity — two points for answering, one for being in the top quartile of clicks out of the upstream directory, one for reporting more than $100, one for showing a leaderboard at all.
• Survival — days since registration, capped, and only counted while the board still answers.
• Data confidence — how many independent kinds of source stand behind the board’s fields.

They are deliberately not combined into one score. A single number would hide exactly the disagreement this site exists to show.

Why some pages are not indexed

A page with a name, a URL and nothing else helps nobody. Boards are sorted into three tiers, and only the first is offered to search engines:

• 120 full files — a registration date, a rule, money or an entry price, a complete evidence ledger, and either a page this site could read or a stated reason it could not. Indexed and in the sitemap.
• 401 thin files — listed, browsable, linked, and marked noindex until the record fills in.
• 9 held back — parked domains, boards that redirect somewhere else entirely, and pages that are not pay-to-rank at all.

The archive, and why it exists

Every sweep is stored as a dated snapshot and nothing is ever overwritten. That is the whole point: a board's own counter is a single number on a page, replaced in place each time it changes. What a board said it had taken last Tuesday is not recoverable from the board. It exists here, or it does not exist.

The change tape is the difference between the last two snapshots. The curves and the uptime strips on each board's page are every snapshot replayed. Identical consecutive readings are collapsed — a flat line of the same figure says nothing — but the first and last of any run are kept, so the dates stay honest. There are 45 sweeps on file so far, the first from 27 Aug 2026.

This is also why boards that die keep their pages. A dead board's last reading is the only record that it ever had rules, a price and a top bid.

Fetching addresses safely

Anyone can submit a URL, so nothing is fetched blindly. Only http and https are allowed; credentials in URLs are rejected; hostnames are resolved before the request and refused if they point at loopback, link-local, private or cloud-metadata addresses; every redirect hop is re-checked the same way; redirects are capped; and response bodies are truncated.

The rendered pass does execute a board’s JavaScript — that is the whole point of it — so it runs in a throwaway headless browser, off the machine that serves this site, with every address re-checked through the same guard before it is opened, dialogs auto-dismissed, and nothing kept but text and a picture.

Logos

Where a board publishes an icon, this site keeps a copy of it. The file served here is always a 128-pixel PNG, taken from the mark the board itself declared — not from a third-party favicon service — so a dead board still has its own face on the catalogue after the address stops answering. The alt text on every one is the board’s name plus the word “logo”.

Addresses go through the same SSRF guard as the rest of the sweep. Nothing is read from a challenge page or a domain-sale placeholder, because copying Cloudflare’s icon and captioning it as the board would be a false statement about what the board is.

Screenshots

Boards with a complete file are photographed when they are rendered, and the picture is dated on the page. It is a record of what the board looked like on that day, kept for the same reason the rest of the archive is: most of these addresses will not be there in a year.

The renderer runs with a software rasteriser, because a good number of these boards are WebGL — 3D scenes, maps, canvases — and without one they photograph as a loading spinner. It waits for the page to stop changing rather than for a fixed delay before it shoots.

A few boards cannot be photographed by machine at all: they answer this site's sweep with a bot challenge. Where a picture of one exists here it was captured by hand, and the caption under it says so rather than claiming the sweep took it. Figures legible in such a picture are recorded in the evidence ledger, dated, and marked as read by eye — they sit beside the machine's readings instead of replacing them, so the picture above and the figures below can be checked against each other.

What this site records about you

Two things. Google Analytics counts page views, which is why a googletagmanager.com script loads on every page — block it and nothing here breaks. And a click on an outbound link to a board is counted once per visitor per day, so a board's page can say how much traffic this site sends it. That count is a one-way hash of the address, the browser string and the date; no address is stored, and the hash cannot be turned back into one. Only requests that present as a browser are counted — a figure a board operator is going to be shown has to be people, not crawlers.

Two click counts appear on a board's page and they are never added together. Clicks sent from here is this site's own, counted as above. Clicks out of outoutbid.lol comes from the upstream directory's export and is their traffic, not this site's. The ordering formula scores on the upstream figure, because this site's own is days old and too small to rank anything by.

Submissions and claims keep what you type, including an email if you give one, so a correction can be checked and a question asked. Nothing is sold and nothing is passed on.

Links out

Every link to a board goes through /go/, which counts the click and then redirects. Nothing about that is paid placement, so the links carry nofollow rather than sponsored — the exception is anything labelled Sponsored, which carries both.

Two things travel with the visitor, so that the board can see where its traffic came from:

• Campaign tags — utm_source=allrank.lol, utm_medium=referral, utm_campaign=pay-to-rank-wiki. A board whose own link already carries campaign tags keeps them; only the missing ones are filled in. A handful of boards route on an exact address and break on an extra parameter — those are linked to clean, and the click is still counted.
• The origin, and only the origin. The redirect sends Referrer-Policy: origin, so a board learns that allrank.lol sent someone and does not learn which page of it they were reading. That is also why the campaign tags do not name the page: putting the path back in the query would undo the point of the policy.

Report a data error

Some of this is certainly wrong. Rules are inferred from marketing copy, categories come from someone else, and money is self-reported by parties with an obvious interest. Corrections are free, they do not require an account, and if you run a board, claiming it is the fastest way to fix your own file.