See who is really selling your inventory
Look up any domain's ads.txt or sellers.json, see which exchanges are authorized, and find the resellers sitting in between — from a dataset crawled continuously across the programmatic ecosystem.
Free, no account needed. Try pubmatic.com, theguardian.com or taboola.com.
What we hold right now
Counts from the live crawl, refreshed continuously. Every file we fetch is also snapshotted, so its history accumulates from the day we first see it.
Three roles, one chain
Publishers
Own the inventory and declare, in ads.txt, which exchange accounts may sell it.
Intermediaries
Resell other people's inventory. Each one is another hop, and another place the two files can disagree.
Ad tech vendors
Exchanges and networks that sell into the auction, declaring in sellers.json who each account belongs to.
What a lookup tells you
Authorization, with evidence
Not just whether a seller is authorized, but the matching ads.txt line and the exchange's own record — so the answer can be checked rather than trusted.
The full chain
Publisher to reseller to exchange, drawn as a map. An ads.txt line names an account; that account often belongs to someone else entirely.
What changed
Relationships flipping DIRECT to RESELLER, sellers going confidential, lines disappearing. Only visible if something is watching continuously.
How it works
Explore the dataset
Ad tech vendors, by sellers declared:
Publishers whose ads.txt changed most recently:
Plans
- 3 monitors
- No API access
- Dashboard only
- 25 monitors
- 1,000 API calls/day
- Change alerts
- 200 monitors
- 10,000 API calls/day
- Change alerts
- 2,000 monitors
- 100,000 API calls/day
- Change alerts
Crawl freshness is identical on every plan — plans gate how much you can watch and how much you can pull, never how current the data is.
From the Lumorrow blog
Background reading on the files this product crawls and the chain it resolves.
ads.txt and sellers.json explained
The files that authorize the supply chain — what each one declares, and how a buyer uses them to verify who may sell a publisher's inventory.
Read on lumorrow.com →SupplyChain 1.1: the hops that don't get paid
IAB Tech Lab's schain 1.1 proposal formally adopts hp=0 nodes, closing a years-old blind spot in the chain.
Read on lumorrow.com →Who's really selling this impression?
The 2026 state of supply-chain transparency: a transaction-ID fracture, a curation fight, and a new IAB Tech Lab count.
Read on lumorrow.com →Supply path optimization explained
The same impression can reach a buyer through a dozen routes, at a dozen prices. SPO is how buyers pick fewer, cleaner ones.
Read on lumorrow.com →Ad fraud in 2026
CTV schemes up 140%, automated traffic past humans, and a new question: is it a bot, or an agent?
Read on lumorrow.com →Made-for-advertising sites explained
Sites built to harvest ad revenue rather than serve readers — how to recognise them and why they drain budgets.
Read on lumorrow.com →All 67 articles on the Lumorrow blog →
Common questions
What is ads.txt?
A plain-text file a publisher puts at /ads.txt listing every exchange account authorized to sell its inventory. Each line names an exchange, an account ID at that exchange, and whether the relationship is DIRECT or RESELLER. A buyer can check it to confirm the inventory they are bidding on is genuinely the publisher's to sell.
What is sellers.json?
The other half of the same picture, published by exchanges rather than publishers. It declares who each account ID actually belongs to, and whether that seller is a PUBLISHER, an INTERMEDIARY (a reseller) or BOTH. Where ads.txt says who is authorized, sellers.json says who they are.
What is the difference between DIRECT and RESELLER?
DIRECT means the publisher is paid by that exchange directly. RESELLER means someone else sits in between. Neither is wrong, but a line quietly changing from DIRECT to RESELLER means the money path changed — which is exactly the kind of thing worth being told about.
What is an intermediary?
A company that resells other people's inventory. They appear in an exchange's sellers.json declared as INTERMEDIARY or BOTH. Every intermediary in a chain is another hop between the publisher and the buyer, and another place for the two files to disagree.
How current is this data?
sellers.json files are re-checked daily. Publisher ads.txt files are checked weekly, or daily once someone is monitoring them. Re-checks use conditional requests, so an unchanged file costs one cheap round trip and the full parse only runs when something actually moved.
Is the lookup really free?
Yes, and no account is needed. What a free lookup shows is the current state of a file. What is sold is continuity — being told when it changes again, monitoring across many domains at once, and API access.
Do you keep old versions of these files?
No. We keep the current version of each file and re-check it on a schedule. When something changes you are alerted at that moment; we do not retain an archive of previous versions, and unwatched domains that publish nothing are not re-crawled at all.
Start with one domain
A free account monitors up to three domains and tells you the moment an ads.txt line flips, a seller goes confidential, or a file disappears.
Create a free account →