Android · BBC Studios Distribution Ltd.

BBC: World News & Stories

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

93/100

47 lines · 30 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

4 −4 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 31     pubmatic.com, 157339, DIRECT, 5d62403b186f2ace # Open Bidding
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: BBC EMEA (via EB)  domain in sellers.json: google.com
line 35     rubiconproject.com, 17264, DIRECT, 0bfd66d529a55807 # Open Bidding
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Google  domain in sellers.json: google.com
line 49     triplelift.com, 918-EB, DIRECT, 6c33edb13117fd86 # Open Bidding
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: BBC (via EB Network)  domain in sellers.json: google.com
line 55     katzdigital.com, 80, DIRECT # BBC # Audio
             → observed: the same account is marked DIRECT by 10 different companies

warning

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

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

line 51     triplelift.com, 14807-EB, DIRECT, 6c33edb13117fd86 # World Service # Open Bidding
             → sellers_json: https://triplelift.com/sellers.json

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 5      bbc.com, 1, DIRECT
             → sellers_json: HTTP 404
line 7      appnexus.com, 12067, DIRECT, f5ab79cb980f11d1 # Ozone Prebid
             → sellers_json: HTTP 403
line 27     openx.com, 540222416, DIRECT, 6a698e2ec38604c6 # Open Bidding
             → sellers_json: HTTP 403
line 28     openx.com, 557333401, DIRECT, 6a698e2ec38604c6 # Ozone Prebid
             → sellers_json: HTTP 403
line 29     openx.com, 563701590, DIRECT, 6a698e2ec38604c6 # BBC FAST Channels via SpringServe
             → sellers_json: HTTP 403
line 54     katzdigital.com, 157, DIRECT # BBC # Audio
             → sellers_json: HTTP 403
line 55     katzdigital.com, 80, DIRECT # BBC # Audio
             → sellers_json: HTTP 403
line 63     openx.com, 537153564, RESELLER, 6a698e2ec38604c6 # Undertone SSP seat
             → sellers_json: HTTP 403
line 69     appnexus.com, 9979, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 70     openx.com, 540731760, 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