App Supply Index Monitor my app
Android · The Philadelphia Inquirer, LLC

The Philadelphia Inquirer

Developer URL
http://www.inquirer.com
app-ads.txt
https://www.inquirer.com/app-ads.txt · 200
Checked
Oct 7, 2026
B
80/100

67 lines · 33 verified against sellers.json

Findings

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

4 −10 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 (4) 
line 34     risecodes.com, 64230763ef16c40001db2f0a, DIRECT
             → sellers_json: https://risecodes.com/sellers.json
line 54     rubiconproject.com, 17574, DIRECT, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 74     gumgum.com, 11645, RESELLER, ffdef49475d318a9
             → sellers_json: https://gumgum.com/sellers.json
line 81     pubmatic.com, 156700, RESELLER, 5d62403b186f2ace
             → sellers_json: https://pubmatic.com/sellers.json
warning

DIRECT lines inconsistent with public data

4 −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 (4) 
line 26     Media.net, 8CUPO1235, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Philadelphia Media Network (via OB)  domain in sellers.json: google.com
line 32     pubmatic.com, 157576, DIRECT, 5d62403b186f2ace
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Philadelphia Media Network (via EB)  domain in sellers.json: google.com
line 68     smaato.com, 1100004890, DIRECT, 07bcf65f187117b4
             → observed: the same account is marked DIRECT by 160 different companies
line 75     lijit.com, 243337-eb, DIRECT, fafdf38b16bf6b2b
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Philadelphia Media Network (via Google EB)  domain in sellers.json: google.com
warning

Lines for ad system domains that don't resolve

1 −1 pts

These ad system domains don't resolve (the domain may be retired, merged or misspelled). The lines can't be validated, and if the domain is registered again, its new holder would appear authorized.

How to fixRemove these lines. If the domain is registered again, its new holder would appear authorized by your file.
Evidence (1) 
line 63     engagebdr.com, 16, RESELLER
             → ad_system: engagebdr.com
info

No OWNERDOMAIN declared

1 −2 pts

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.
info

DIRECT accounts registered to another domain

1 −1 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 (1) 
line 53     rubiconproject.com, 10035, DIRECT, 0bfd66d529a55807
             → domain in sellers.json: philly.com  name in sellers.json: Philadelphia Media Network Newspapers LLC
info

Ad systems without a public sellers.json

24

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 (24) 
line 6      appnexus.com,10188,DIRECT,f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 10     rhythmone.com, 2305882417, DIRECT, a670c89d4a324e47
             → sellers_json: HTTP 403 to automated requests
line 11     rhythmone.com, 2432108893, DIRECT, a670c89d4a324e47
             → sellers_json: HTTP 403 to automated requests
line 13     appnexus.com, 11236, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 16     openx.com, 540773939, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 23     liveintent.com, 70287, DIRECT
             → sellers_json: HTTP 403 to automated requests
line 29     openx.com, 539306169, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 30     openx.com, 540928197, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 43     loopme.com, 11362, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403 to automated requests
line 45     smartadserver.com, 4284, RESELLER
             → sellers_json: HTTP 404
line 48     freewheel.tv, 1590601, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 49     freewheel.tv, 1590606, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 50     openx.com, 537140488, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 58     adcolony.com, 496220845654deec, RESELLER, 1ad675c9de6b5176
             → sellers_json: returns a web page, not a sellers.json file
line 65     openx.com, 540421297, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 67     rhythmone.com, 4201299756, RESELLER, a670c89d4a324e47
             → sellers_json: HTTP 403 to automated requests
line 68     smaato.com, 1100004890, DIRECT, 07bcf65f187117b4
             → sellers_json: HTTP 403 to automated requests
line 69     smaato.com, 1100036563, DIRECT, 07bcf65f187117b4
             → sellers_json: HTTP 403 to automated requests
line 70     startapp.com, smt, RESELLER
             → sellers_json: HTTP 404
line 71     xad.com, 241, RESELLER, 81cbf0a75a5e0e9a
             → sellers_json: HTTP 403 to automated requests
line 73     appnexus.com, 1360, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 77     openx.com, 538959099, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 78     openx.com, 539924617, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 83     sovrn.com, 243337, DIRECT, fafdf38b16bf6b2b
             → 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.

Monitor this app