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
3−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 (3)
line 4 applovin.com, 4124f7006da8d65bb110383bb25d3ef3, DIRECT
→ sellers_json: https://applovin.com/sellers.json
line 12 google.com, pub-3940256099942544, DIRECT, f08c47fec0942fa0
→ sellers_json: https://realtimebidding.google.com/sellers.json
line 42 google.com, pub-3276267510738498, DIRECT, f08c47fec0942fa0
→ sellers_json: https://realtimebidding.google.com/sellers.json
warning
DIRECT lines inconsistent with public data
1−6 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 12 google.com, pub-3940256099942544, DIRECT, f08c47fec0942fa0
→ observed: the same account is marked DIRECT by 39 different companies
info
Ad systems without a public sellers.json
8
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 (8)
line 1 mopub.com, 2e898693f0174c3db477c400e11c3f4a, DIRECT, 74b46c0ea83967ca
→ sellers_json: HTML or login page instead of JSON
line 3 facebook.com, 766081393512545, DIRECT, c3e20eee3f780d680
→ sellers_json: HTML or login page instead of JSON
line 5 adcolony.com, 5d8cbf6671c93a42, RESELLER, 1ad675c9de6b5176
→ sellers_json: HTML or login page instead of JSON
line 7 openx.com, 540785403, RESELLER, 6a698e2ec38604c6
→ sellers_json: HTTP 403
line 13 loopme.com, 11303, RESELLER, 6c8d5f95897a5a3b
→ sellers_json: HTTP 403
line 21 gamaigroup.com, 423056, RESELLER
→ sellers_json: HTML or login page instead of JSON
line 23 loopme.com, 11424, RESELLER, 6c8d5f95897a5a3b
→ sellers_json: HTTP 403
line 25 openx.com, 559798512, RESELLER, 6a698e2ec38604c6
→ sellers_json: HTTP 403
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.