App Supply Index Monitor my app
Android · Times Media Limited

The Times: UK & World News

Developer URL
http://www.thetimes.com/subscribe
app-ads.txt
https://www.thetimes.com/ads.txt · 200
Checked
Oct 7, 2026
A
91/100

66 lines · 36 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

2 −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 (2)
line 89     themediagrid.com, DXW9CT, RESELLER, 35d5010d7789b49d
             → sellers_json: https://themediagrid.com/sellers.json
line 104    blis.com, 212, DIRECT, 61453ae19a4b73f4 #TAM
             → sellers_json: https://blis.com/sellers.json
warning

DIRECT lines inconsistent with public data

2 −2 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 130    katzdigital.com, 318, DIRECT
             → observed: the same account is marked DIRECT by 9 different companies
line 131    katzdigital.com, 80, DIRECT
             → observed: the same account is marked DIRECT by 10 different companies
warning

Lines for ad system domains that don't resolve

1 −2 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 57     avct.cloud, 5f1eade2303de5fb4fe30bc5, RESELLER
             → ad_system: avct.cloud
info

DIRECT accounts registered to another domain

2 −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 (2)
line 87     dianomi.com, 1512, DIRECT, 61e7d0a6019f7cfc
             → domain in sellers.json: thetimes.co.uk  name in sellers.json: The Times
line 120    durationmedia.net, 23330820613, DIRECT #TAM
             → domain in sellers.json: thesun.co.uk  name in sellers.json: News UK
info

Ad systems without a public sellers.json

15

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 (15)
line 14     openx.com, 539722942, RESELLER, 6a698e2ec38604c6 #OB
             → sellers_json: HTTP 403
line 22     appnexus.com, 3819, DIRECT
             → sellers_json: HTTP 403
line 35     openx.com, 539714782, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 36     openx.com, 540757494, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 37     openx.com, 540097092, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 38     openx.com, 558342684, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 52     appnexus.com, 9979, RESELLER
             → sellers_json: HTTP 403
line 53     openx.com, 540731760, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 63     appnexus.com, 2127, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 64     appnexus.com, 3310, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 82     criteo.com, B-058360, DIRECT, 9fac4a4a87c2a44f
             → sellers_json: HTTP 403
line 130    katzdigital.com, 318, DIRECT
             → sellers_json: HTTP 403
line 131    katzdigital.com, 80, DIRECT
             → sellers_json: HTTP 403
line 132    katzdigital.com, 318, RESELLER
             → sellers_json: HTTP 403
line 133    katzdigital.com, 80, RESELLER
             → 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