Each finding lists the exact lines involved. Findings are automated observations of public files as of
Nov 16, 2026. They describe file contents, not the intent or conduct of any company.
warning
DIRECT lines inconsistent with public data
4
The IAB ads.txt specification: "A value of ‘DIRECT’ indicates that the Publisher (content owner) directly controls the account." 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 companies with different owner domains. 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.
Full guide →
Evidence (4)
line 22 google.com, pub-7171208642811509, DIRECT, f08c47fec0942fa0
→ partner block: Adx observed: the same account is marked DIRECT by 4 different companies
line 25 rubiconproject.com, 22884, DIRECT, 0bfd66d529a55807
→ partner block: Magnite-App observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 86 different companies name in sellers.json: Google domain in sellers.json: google.com
line 28 pubmatic.com, 159856, DIRECT, 5d62403b186f2ace
→ partner block: Pubmatic-App observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 31 different companies name in sellers.json: Google LLC (via EB) domain in sellers.json: google.com
line 31 media.net, 8CA7SY66I, DIRECT
→ partner block: Media.net - App observed: sellers.json lists the account as INTERMEDIARY name in sellers.json: Al Jazeera (via OB) domain in sellers.json: google.com
info
Ad systems whose sellers.json we couldn't read
4
We couldn't read a sellers.json for these ad systems at crawl time (no file, invalid JSON, empty, or automated access refused), so these lines weren't verified. No points are deducted.
How to fixAsk the partner to publish sellers.json; until then buyers can't verify that path.
Full guide →
Evidence (4)
line 6 facebook.com, 10153660741773690, RESELLER, c3e20eee3f780d68
→ partner block: Facebook sellers_json: robots.txt of facebook.com disallows crawlers
line 9 indexexchange.com, 185052, DIRECT, 50b1c356f2c5c8fc
→ partner block: Index Exchange sellers_json: robots.txt of cdn.indexexchange.com disallows crawlers
line 12 appnexus.com, 2127, Reseller, f5ab79cb980f11d1
→ partner block: GroupM -UK sellers_json: HTTP 403 to automated requests
line 13 appnexus.com, 3310, Reseller, f5ab79cb980f11d1
→ partner block: GroupM -UK sellers_json: HTTP 403 to automated requests
info
Too few verifiable lines to grade
4
A grade says how well a file holds up against the ad systems' public sellers.json files. Fewer than {min} of this file's seller lines could be checked that way (short file, or ad systems whose sellers.json we couldn't read or that look incomplete), so it isn't graded. Findings are still listed.
How to fixMake sure the file lists every partner you sell through. Lines for ad systems without a readable sellers.json can't be verified by buyers either.
info
No OWNERDOMAIN declared
1
app-ads.txt 1.1 recommends OWNERDOMAIN so buyers can match DIRECT accounts to the owner.
How to fixAdd OWNERDOMAIN=<your company domain> to the file.
Full guide →