App Supply Index Monitor my app
Android · Telegraph Media Group Holdings Limited

The Telegraph UK Latest News

Developer URL
https://editionapp-website.platforms-prod-gcp.telegraph.co.uk/faq/
app-ads.txt
https://www.telegraph.co.uk/app-ads.txt · 200
Checked
Oct 7, 2026
C
72/100

80 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

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

12 −17 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 (12) 
line 13     triplelift.com, 3117, DIRECT, 6c33edb13117fd86 # Amazon - Triplelift #WW #BANNER
             → sellers_json: https://triplelift.com/sellers.json
line 21     google.com, pub-3033197808145916, DIRECT, f08c47fec0942fa0 # Google - AdX - LocalMediaConsortium #WW #BANNER
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 23     google.com, pub-4015880282924246, DIRECT, f08c47fec0942fa0 # Google - Adsense #WW #BANNER
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 42     smaato.com, 1100048704, RESELLER, 07bcf65f187117b4 # Premium video demand from Outbrain #WW #BANNER, #NATIVE
             → sellers_json: https://smaato.com/sellers.json
line 52     rubiconproject.com, 20692, DIRECT, 0bfd66d529a55807 # EBDA #WW #BANNER
             → sellers_json: https://rubiconproject.com/sellers.json
line 57     smartadserver.com, 4012, DIRECT # #WW #BANNER
             → sellers_json: https://smartadserver.com/sellers.json
line 58     smartadserver.com, 4071, DIRECT # #WW #BANNER
             → sellers_json: https://smartadserver.com/sellers.json
line 59     smartadserver.com, 4073, DIRECT # #WW #BANNER
             → sellers_json: https://smartadserver.com/sellers.json
line 60     smartadserver.com, 4074, DIRECT # #WW #BANNER
             → sellers_json: https://smartadserver.com/sellers.json
line 76     improvedigital.com, 1451, DIRECT # #WW #BANNER
             → sellers_json: https://improvedigital.com/sellers.json
line 84     yieldmo.com, 3337992342509396649, DIRECT # Yieldmo Ozone #WW #BANNER
             → sellers_json: https://yieldmo.com/sellers.json
line 100    improvedigital.com, 2429, DIRECT # #WW #BANNER
             → sellers_json: https://improvedigital.com/sellers.json
warning

DIRECT lines inconsistent with public data

10 −8 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 (10) 
line 31     media.net, 8CU6PG23S, DIRECT, 818f58666cabc936 # Media.net - DFP/EDBA #WW #BANNER, #NATIVE, #INSTREAM, #OUTSTREAM
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Telegraph Media Group Holdings Limited (via OB)  domain in sellers.json: google.com
line 49     pubmatic.com, 157010, DIRECT, 5d62403b186f2ace # Pubmatic - EBDA #WW #BANNER
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: The Telegraph Mediagroup (EMEA) (via EB)  domain in sellers.json: google.com
line 55     smartadserver.com, 4011, DIRECT # Smart AdServer (via Ozone) #WW #BANNER
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Ozone Project Ltd  domain in sellers.json: the-ozone-project.com
line 56     smartadserver.com, 4016, DIRECT # #WW #BANNER
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 47 different companies  name in sellers.json: SmartPGMarketplace  domain in sellers.json: dynadmic.com
line 57     smartadserver.com, 4012, DIRECT # #WW #BANNER
             → observed: the same account is marked DIRECT by 45 different companies
line 58     smartadserver.com, 4071, DIRECT # #WW #BANNER
             → observed: the same account is marked DIRECT by 59 different companies
line 59     smartadserver.com, 4073, DIRECT # #WW #BANNER
             → observed: the same account is marked DIRECT by 43 different companies
line 60     smartadserver.com, 4074, DIRECT # #WW #BANNER
             → observed: the same account is marked DIRECT by 43 different companies
line 64     triplelift.com, 3256-EB, DIRECT, 6c33edb13117fd86 # TripleLift Direct #WW #BANNER
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Telegraph (via EB Network)  domain in sellers.json: google.com
line 83     onetag.com, 816bbec9a34cdbf-OB, DIRECT # Onetag Direct - EBDA #WW #BANNER
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Telegraph Media Group Limited-OB  domain in sellers.json: google.com
warning

Lines for ad system domains that don't resolve

2 −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 (2) 
line 74     avct.cloud, 5f1eae01f8d3c61b3e37a382, DIRECT # #WW #BANNER
             → ad_system: avct.cloud
line 77     districtm.io, 101995, DIRECT, 3fd707be9c4527c3 # Primarily non-UK #WW #BANNER
             → ad_system: districtm.io
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 75     adform.com, 2657, DIRECT, 9f5210a2f0999e32 # #WW #BANNER
             → domain in sellers.json: the-ozone-project.com  name in sellers.json: The Ozone Project
info

Ad systems without a public sellers.json

10

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 15     criteo.com, B-062523, DIRECT, 9fac4a4a87c2a44f # Criteo #WW #BANNER
             → sellers_json: HTTP 403
line 40     openx.com, 540393169, RESELLER, 6a698e2ec38604c6 # Premium video demand #WW #BANNER, #NATIVE
             → sellers_json: HTTP 403
line 43     vi.ai, g-005b778b60d86e93b08cc968758f6ac863, DIRECT # instream video by outbrain #WW #BANNER, #NATIVE
             → sellers_json: HTTP 404
line 47     appnexus.com, 7597, RESELLER, f5ab79cb980f11d1 # #WW #BANNER, #NATIVE
             → sellers_json: HTTP 403
line 66     appnexus.com, 1314, RESELLER, f5ab79cb980f11d1 # TripleLift Reseller #WW #BANNER
             → sellers_json: HTTP 403
line 68     appnexus.com, 9979, DIRECT, f5ab79cb980f11d1 # #WW #BANNER
             → sellers_json: HTTP 403
line 69     appnexus.com, 2542, DIRECT, f5ab79cb980f11d1 # #WW #BANNER, #INSTREAM
             → sellers_json: HTTP 403
line 92     appnexus.com, 2758, RESELLER, f5ab79cb980f11d1 # #WW #BANNER
             → sellers_json: HTTP 403
line 94     openx.com, 540731760, DIRECT, 6a698e2ec38604c6 # Direct - Ozone - PMP #WW #BANNER
             → sellers_json: HTTP 403
line 102    appnexus.com, 13099, RESELLER, f5ab79cb980f11d1 # #WW #BANNER
             → 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