iOS · The Washington Post Company

Washington Post

Developer URL: https://www.washingtonpost.com
app-ads.txt: https://www.washingtonpost.com/app-ads.txt · 200
Checked: Oct 7, 2026

84/100

271 lines · 208 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

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

line 19     triplelift.com,2936,DIRECT,6c33edb13117fd86
             → sellers_json: https://triplelift.com/sellers.json
line 23     google.com, pub-0231639411043846, DIRECT, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 28     rubiconproject.com, 24732, RESELLER, 0bfd66d529a55807 #ob
             → sellers_json: https://rubiconproject.com/sellers.json
line 43     smaato.com, 1100060509, RESELLER, 07bcf65f187117b4
             → sellers_json: https://smaato.com/sellers.json
line 51     triplelift.com,2936,DIRECT,6c33edb13117fd86
             → sellers_json: https://triplelift.com/sellers.json
line 58     verve.com,2205665,RESELLER
             → sellers_json: https://verve.com/sellers.json
line 169    smartadserver.com, 4012, RESELLER
             → sellers_json: https://smartadserver.com/sellers.json
line 173    smilewanted.com, 4391, RESELLER
             → sellers_json: https://smilewanted.com/sellers.json
line 182    onetag.com, 82bad7d17eccf7c, RESELLER
             → sellers_json: https://onetag.com/sellers.json
line 199    peak226.com, 20120, RESELLER
             → sellers_json: https://peak226.com/sellers.json
line 204    rubiconproject.com, 20086, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 211    video.unrulymedia.com, 2564526802, RESELLER
             → sellers_json: https://video.unrulymedia.com/sellers.json
line 247    rubiconproject.com, 24606, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 248    rubiconproject.com, 25748, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 249    pubmatic.com, 164891, RESELLER, 5d62403b186f2ace
             → sellers_json: https://pubmatic.com/sellers.json
line 256    adelement.com, 48268, RESELLER
             → sellers_json: https://adelement.com/sellers.json
line 270    rubiconproject.com, 17888, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json

warning

DIRECT lines inconsistent with public data

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

line 6      pubmatic.com, 157050, DIRECT, 5d62403b186f2ace
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Washington Post (via EB)  domain in sellers.json: google.com
line 11     rubiconproject.com, 17302, DIRECT, 0bfd66d529a55807
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Google  domain in sellers.json: google.com
line 18     triplelift.com, 3015-EB, DIRECT, 6c33edb13117fd86
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Washington Post (via EB Network)  domain in sellers.json: google.com
line 76     risecodes.com, 5fad0eb54fdc5c00016859b1, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 6 different companies  name in sellers.json: MediaTradecraft  domain in sellers.json: mediatradecraft.com
line 96     tappx.com, 43794, DIRECT, 9f375a07da0318ec
             → observed: the same account is marked DIRECT by 3 different companies
line 160    adsbynimbus.com, 9381145f-8ee6-44bc-817e-e82fce9021a2, DIRECT, dd263a8a859bd0e0
             → observed: the same account is marked DIRECT by 3 different companies  name in sellers.json: Straight Arrow News | SAN  domain in sellers.json: san.com
line 239    themediagrid.com, A7OJMU, DIRECT, 35d5010d7789b49d
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 36 different companies  name in sellers.json: Nimbus Advertising Solutions  domain in sellers.json: adsbynimbus.com

warning

Malformed lines

1 −1 pts

Lines that buyers' crawlers will ignore.

How to fixFix the format: <ad system domain>, <seller id>, DIRECT|RESELLER[, <cert authority id>].

Evidence (1)

line 42     conversantmedia.com, 101272, DIRECT/RESELLER, 03113cd04947736d
             → reason: relationship must be DIRECT or RESELLER, got 'DIRECT/RESELLER'

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 8      districtm.io, 101885, DIRECT, 3fd707be9c4527c3
             → ad_system: districtm.io

info

Duplicate lines

11 −1 pts

Harmless but a sign of copy-paste maintenance.

How to fixRemove duplicates; keep one copy of each line.

Evidence (11)

ad_system: pubmatic.com  seller_id: 156416  relationship: DIRECT
ad_system: rubiconproject.com  seller_id: 12890  relationship: DIRECT
ad_system: openx.com  seller_id: 537154106  relationship: DIRECT
ad_system: aps.amazon.com  seller_id: be6d001d-1c56-4a9c-9dca-7c02b3daa060  relationship: DIRECT
ad_system: google.com  seller_id: pub-3746578658400510  relationship: RESELLER
ad_system: triplelift.com  seller_id: 2936  relationship: DIRECT
ad_system: media.net  seller_id: 8cuj434v8  relationship: DIRECT
ad_system: yieldmo.com  seller_id: 3236491856409731720  relationship: DIRECT
ad_system: kargo.com  seller_id: 8938  relationship: DIRECT
ad_system: xandr.com  seller_id: 15840  relationship: RESELLER
ad_system: rubiconproject.com  seller_id: 26292  relationship: RESELLER

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 (25 of 37)

line 13     openx.com,537154106,DIRECT,6a698e2ec38604c6
             → sellers_json: HTTP 403
line 14     openx.com, 539044014, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 48     openx.com,537154106,DIRECT,6a698e2ec38604c6
             → sellers_json: HTTP 403
line 55     sovrn.com,375328,RESELLER,fafdf38b16bf6b2b
             → sellers_json: HTTP 403
line 70     openx.com, 560678323, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 86     openx.com, 537140488, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 90     loopme.com, 11362, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 100    loopme.com, 11227, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 124    openx.com, 540258065, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 133    appnexus.com, 16007, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 135    freestar.com, 1819, RESELLER
             → sellers_json: HTTP 403
line 142    freewheel.tv, sg1260960, RESELLER
             → sellers_json: HTTP 403
line 143    freewheel.tv, 536419-r-524565, RESELLER
             → sellers_json: HTTP 403
line 144    freewheel.tv, 536419-r-523319, RESELLER
             → sellers_json: HTTP 403
line 153    appnexus.com, 1577, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 165    openx.com, 540274407, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 177    appnexus.com, 12061, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 178    appnexus.com, 12878, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 179    appnexus.com, 14080, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 180    freewheel.tv, 1601349, RESELLER
             → sellers_json: HTTP 403
line 181    freewheel.tv, 1601388, RESELLER
             → sellers_json: HTTP 403
line 197    startapp.com, 143265457, RESELLER
             → sellers_json: HTTP 404
line 209    openx.com, 537149888, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 210    appnexus.com, 3703, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 223    openx.com, 538959099, 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