Each finding lists the exact lines involved. Findings are automated observations of public files as of
Oct 7, 2026. They describe file contents, not the intent or conduct of any company.
warning
Seller IDs not listed in the ad system's sellers.json
2−6 pts
The ad system's current sellers.json doesn't list these accounts, so buyers that validate the chain can't match them. Common causes are closed accounts or former partners.
How to fixAsk each partner whether the account is still active and request their current lines; remove lines for closed accounts.
Evidence (2)
line 18 targetspot.com, 144, RESELLER, feb28ed826dcf532
→ sellers_json: https://www.targetspot.com/sellers.json
line 68 amperwave.net, adan10003, RESELLER
→ sellers_json: https://amperwave.net/sellers.json
warning
DIRECT lines inconsistent with public data
1−3 pts
The ads.txt specification defines DIRECT as an account the publisher directly controls. For these lines, either the ad system's own sellers.json lists the account as INTERMEDIARY, or the same account is marked DIRECT in the files of 3 or more unrelated companies. Either way, the public data does not support the DIRECT label. Buyers that use DIRECT labels in supply-path decisions may treat these lines differently.
How to fixUse DIRECT only for accounts your company controls. Confirm with each partner whether the account is yours; if it isn't, the specification calls for RESELLER.
Evidence (1)
line 44 rubiconproject.com,26232,DIRECT, 0bfd66d529a55807
→ observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Google domain in sellers.json: google.com
info
DIRECT accounts registered to another domain
8−8 pts
Allowed when the domain belongs to the same company; add OWNERDOMAIN to make that explicit. Otherwise these accounts may belong to someone else.
How to fixIf the account is yours under another domain, declare it with OWNERDOMAIN=<that domain>; otherwise mark it RESELLER.
Evidence (8)
line 36 rubiconproject.com,9973,DIRECT, 0bfd66d529a55807
→ domain in sellers.json: deezer-brandsolutions.com name in sellers.json: DEEZER S.A.
line 37 google.com, pub-4770306737042736,DIRECT,f08c47fec0942fa0
→ domain in sellers.json: deezer.com name in sellers.json: DEEZER FRANCE
line 38 tritondigital.com, 3353, DIRECT, 19b4454d0b87b58b
→ domain in sellers.json: deezer.com name in sellers.json: DEEZER S.A.
line 42 smartclip.net, 13107, DIRECT
→ domain in sellers.json: deezer.com name in sellers.json: Deezer S.A.
line 47 targetspot.com, 379, DIRECT, feb28ed826dcf532
→ domain in sellers.json: deezer.com name in sellers.json: Deezer Brazil
line 48 improvedigital.com, 2174_379, DIRECT
→ domain in sellers.json: deezer.com name in sellers.json: Deezer Brazil
line 49 improvedigital.com, 2588, DIRECT
→ domain in sellers.json: deezer.com name in sellers.json: Deezer
line 67 amperwave.net, 782, DIRECT
→ domain in sellers.json: audacy.com name in sellers.json: Audacy
info
Duplicate lines
6−2 pts
Harmless but a sign of copy-paste maintenance.
How to fixRemove duplicates; keep one copy of each line.
The ad system doesn't publish a readable sellers.json, so nobody can verify these lines. That's the ad system's gap, not the app's, so no points are deducted.
How to fixAsk the partner to publish sellers.json; until then buyers can't verify that path.
Evidence (6)
line 12 appnexus.com, 1577, RESELLER, f5ab79cb980f11d1
→ sellers_json: HTTP 403 to automated requests
line 13 appnexus.com, 6924, RESELLER, f5ab79cb980f11d1
→ sellers_json: HTTP 403 to automated requests
line 14 appnexus.com, 7265, RESELLER, f5ab79cb980f11d1
→ sellers_json: HTTP 403 to automated requests
line 35 smartadserver.com, 400, DIRECT, 060d053dcf45cbf3
→ sellers_json: HTTP 404
line 46 appnexus.com, 15873, RESELLER, f5ab79cb980f11d1
→ sellers_json: HTTP 403 to automated requests
line 54 appnexus.com, 7265, RESELLER, f5ab79cb980f11d1
→ sellers_json: HTTP 403 to automated requests
Is this your app?
Get the full evidence list, a cleaned app-ads.txt, and alerts when partners' accounts change.
Think something here is wrong? Request a correction.