Android · VSCO

VSCO: Photo Editor

Developer URL: https://vsco.co
app-ads.txt: https://vsco.co/app-ads.txt · 200
Checked: Oct 7, 2026

87/100

72 lines · 58 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

DIRECT lines inconsistent with public data

2 −7 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 (2)

line 15     Media.net, 8CU378764, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: VSCO (via OB)  domain in sellers.json: google.com
line 23     pubmatic.com, 166035, DIRECT, 5d62403b186f2ace
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: VSCO_OB (via EB)  domain in sellers.json: google.com

warning

Seller IDs not listed in the ad system's sellers.json

3 −4 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 5      google.com, pub-9148923416628006, DIRECT, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 12     rubiconproject.com, 26914, DIRECT, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 27     risecodes.com, 6825c8df2c969d00011edd2f, DIRECT
             → sellers_json: https://risecodes.com/sellers.json

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

Ad systems without a public sellers.json

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 (10)

line 34     facebook.com, 1096492088998348, RESELLER, c3e20eee3f780d68
             → sellers_json: HTML or login page instead of JSON
line 35     gamaigroup.com, 423056, RESELLER
             → sellers_json: HTML or login page instead of JSON
line 40     loopme.com, 11303, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 41     loopme.com, 11362, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 42     loopme.com, 11424, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 43     loopme.com, 11498, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 47     openx.com, 537100188, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 48     openx.com, 537140488, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 49     openx.com, 540785403, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 50     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.

Monitor this app