Sample ads.txt and app-ads.txt

ads.txt and app-ads.txt are simple text files a publisher hosts at the domain root (or the developer website for apps) to declare the list of SSPs and resellers authorized to sell its inventory. They are the basic tool against ad fraud (domain spoofing).

💡 Each file's contents are shown below right on the page — copy the lines you need without downloading. For a production file, rename to ads.txt and place at the domain root.
IAB Tech Lab specs: ads.txt 1.1 · app-ads.txt

Sample file: Minimal ads.txt (single DIRECT entry)
Minimal ads.txt (single DIRECT entry)
222 bytes
↓
Sample file: Full ads.txt: DIRECT + RESELLER + comments + CONTACT/SUBDOMAIN
Full ads.txt: DIRECT + RESELLER + comments + CONTACT/SUBDOMAIN
1.0 Kb
↓
Sample file: app-ads.txt for mobile apps (AdMob, AppLovin, IronSource, etc.)
app-ads.txt for mobile apps (AdMob, AppLovin, IronSource, etc.)
732 bytes
↓
Sample file: Multi-SSP template: Google, Magnite, OpenX, PubMatic, Index, Xandr, Criteo, etc.
Multi-SSP template: Google, Magnite, OpenX, PubMatic, Index, Xandr, Criteo, etc.
1.5 Kb
↓

🧠 How ads.txt works

Each line in ads.txt is the publisher's authorization to sell inventory through a specific channel. The file must be hosted strictly at the domain root URL, without redirects, and is read by SSP/DSP crawlers once a day.

📰 Publisher hosts the file domain/ads.txt 📝 Text file DIRECT / RESELLER + variables 🕷️ SSP crawler reads the file once per day ✅ Validation bid request publisher_id ✓ 🛡️ Anti-fraud blocks domain spoofing