> TELEGRAPH MEDIA GROUP HOLDINGS LIMITED publishes 1 app in this index that use the app-ads.txt at telegraph.co.uk; the file scores 79/100 (B). Every seller line checked against the ad systems' sellers.json.

Source: https://appsupplyindex.com/publisher/telegraph-co-uk · Updated: 2026-11-16 · License: CC BY 4.0 (App Supply Index)

---
B79 / 100

# TELEGRAPH MEDIA GROUP HOLDINGS LIMITED

telegraph.co.uk/app-ads.txt · 1 app
· Android + iOS · 87 seller lines · checked Nov 16, 2026

**19 lines to fix.** Three steps take this file from
B 79 to A 99.

87 seller lines in [www.telegraph.co.uk/app-ads.txt](https://www.telegraph.co.uk/app-ads.txt);
55 could be checked against the ad systems' sellers.json. Main finding: Seller IDs not listed in the ad system's sellers.json.

app-ads.txtLines from steps 1–3

86districtm.io, 101995, DIRECT, 3fd707be9c4527c3 # Primarily non-UK #WW #BANNERRemove: districtm.io doesn't resolve. No partner contact needed.

40media.net, 8CU6PG23S, DIRECT, 818f58666cabc936 # Media.net - DFP/EDBA #WW #BANNER, #NATIVE, #INSTREAM, #OUTSTREAMConfirm with the partner: sellers.json lists the account as INTERMEDIARY. If the account isn't yours, use RESELLER.

58pubmatic.com, 157010, DIRECT, 5d62403b186f2ace # Pubmatic - EBDA #WW #BANNERConfirm with the partner: sellers.json lists the account as INTERMEDIARY. If the account isn't yours, use RESELLER.

64smartadserver.com, 4011, DIRECT # Smart AdServer (via Ozone) #WW #BANNERConfirm with the partner: sellers.json lists the account as INTERMEDIARY. If the account isn't yours, use RESELLER.

+ 6 more DIRECT lines to confirm

13triplelift.com, 3117, DIRECT, 6c33edb13117fd86 # Amazon - Triplelift #WW #BANNERAsk the partner: this ID isn't in triplelift.com's sellers.json.

51smaato.com, 1100048704, RESELLER, 07bcf65f187117b4 # Premium video demand from Outbrain #WW #BANNER, #NATIVEAsk the partner: this ID isn't in smaato.com's sellers.json.

61rubiconproject.com, 20692, DIRECT, 0bfd66d529a55807 # EBDA #WW #BANNERAsk the partner: this ID isn't in rubiconproject.com's sellers.json.

+ 6 more seller IDs to ask about

## What to change

Easiest first. Points are estimates, assuming every line in a step is fixed.

1. Remove 1 line for ad system domains that didn't resolve. No partner contact needed.+1 → 80
2. Confirm 9 DIRECT lines with the partners that supplied them (5 partner blocks: WW #BANNER, Media.net - DFP/EDBA #WW #BANNER, #NATIVE, #INSTREAM, #OUTST, Pubmatic - EBDA #WW #BANNER, Smart AdServer (via Ozone) #WW #BANNER, …); use RESELLER where the account isn't yours.+6 → 86
3. Ask partners about 9 seller IDs missing from their sellers.json (4 partner blocks: WW #BANNER, Amazon - Triplelift #WW #BANNER, Premium video demand from Outbrain #WW #BANNER, #NATIVE, EBDA #WW #BANNER); remove lines for closed accounts.+13 → A 99
4. Add OWNERDOMAIN, or confirm 2 DIRECT accounts registered to another domain.+1 → A 100

[Re-check now](https://appsupplyindex.com/check?app=https%3A//apps.apple.com/us/app/id388947468)

## Findings

Each finding lists the exact lines involved. Findings are automated observations of public files as of
Nov 16, 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

9
−13 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 fix**Ask each partner whether the account is still active and request their current lines; remove lines for closed accounts.
[Full guide →](https://appsupplyindex.com/fix/seller-id-not-in-sellers-json)

Evidence (9)

```
line 13     triplelift.com, 3117, DIRECT, 6c33edb13117fd86 # Amazon - Triplelift #WW #BANNER
             → partner block: Amazon - Triplelift #WW #BANNER  sellers_json: https://triplelift.com/sellers.json
line 51     smaato.com, 1100048704, RESELLER, 07bcf65f187117b4 # Premium video demand from Outbrain #WW #BANNER, #NATIVE
             → partner block: Premium video demand from Outbrain #WW #BANNER, #NATIVE  sellers_json: https://smaato.com/sellers.json
line 61     rubiconproject.com, 20692, DIRECT, 0bfd66d529a55807 # EBDA #WW #BANNER
             → partner block: EBDA #WW #BANNER  sellers_json: https://rubiconproject.com/sellers.json
line 66     smartadserver.com, 4012, DIRECT # #WW #BANNER
             → partner block: #WW #BANNER  sellers_json: https://smartadserver.com/sellers.json
line 67     smartadserver.com, 4071, DIRECT # #WW #BANNER
             → partner block: #WW #BANNER  sellers_json: https://smartadserver.com/sellers.json
line 68     smartadserver.com, 4073, DIRECT # #WW #BANNER
             → partner block: #WW #BANNER  sellers_json: https://smartadserver.com/sellers.json
line 69     smartadserver.com, 4074, DIRECT # #WW #BANNER
             → partner block: #WW #BANNER  sellers_json: https://smartadserver.com/sellers.json
line 85     improvedigital.com, 1451, DIRECT # #WW #BANNER
             → partner block: #WW #BANNER  sellers_json: https://improvedigital.com/sellers.json
line 109    improvedigital.com, 2429, DIRECT # #WW #BANNER
             → partner block: #WW #BANNER  sellers_json: https://improvedigital.com/sellers.json
```

warning

### DIRECT lines inconsistent with public data

9
−6 pts

The IAB ads.txt specification: "A value of ‘DIRECT’ indicates that the Publisher (content owner) directly controls the account." 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 companies with different owner domains. 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 fix**Use 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.
[Full guide →](https://appsupplyindex.com/fix/inconsistent-direct)

Evidence (9)

```
line 40     media.net, 8CU6PG23S, DIRECT, 818f58666cabc936 # Media.net - DFP/EDBA #WW #BANNER, #NATIVE, #INSTREAM, #OUTSTREAM
             → partner block: Media.net - DFP/EDBA #WW #BANNER, #NATIVE, #INSTREAM, #OUTST  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 58     pubmatic.com, 157010, DIRECT, 5d62403b186f2ace # Pubmatic - EBDA #WW #BANNER
             → partner block: 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 64     smartadserver.com, 4011, DIRECT # Smart AdServer (via Ozone) #WW #BANNER
             → partner block: 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 65     smartadserver.com, 4016, DIRECT # #WW #BANNER
             → partner block: #WW #BANNER  observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 84 different companies  name in sellers.json: SmartPGMarketplace  domain in sellers.json: dynadmic.com
line 66     smartadserver.com, 4012, DIRECT # #WW #BANNER
             → partner block: #WW #BANNER  observed: the same account is marked DIRECT by 79 different companies
line 67     smartadserver.com, 4071, DIRECT # #WW #BANNER
             → partner block: #WW #BANNER  observed: the same account is marked DIRECT by 95 different companies
line 68     smartadserver.com, 4073, DIRECT # #WW #BANNER
             → partner block: #WW #BANNER  observed: the same account is marked DIRECT by 78 different companies
line 69     smartadserver.com, 4074, DIRECT # #WW #BANNER
             → partner block: #WW #BANNER  observed: the same account is marked DIRECT by 79 different companies
line 73     triplelift.com, 3256-EB, DIRECT, 6c33edb13117fd86 # TripleLift Direct #WW #BANNER
             → partner block: 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
```

warning

### Ad system domains that didn't resolve at crawl time

1
−1 pts

These ad system domains returned no DNS address at crawl time, checked twice (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 fix**Remove these lines. If the domain is registered again, its new holder would appear authorized by your file.
[Full guide →](https://appsupplyindex.com/fix/ad-system-domain-does-not-resolve)

Evidence (1)

```
line 86     districtm.io, 101995, DIRECT, 3fd707be9c4527c3 # Primarily non-UK #WW #BANNER
             → partner block: Primarily non-UK #WW #BANNER  ad_system: districtm.io
```

info

### DIRECT accounts registered to another domain

2
−1 pts

The IAB ads.txt specification: "A value of ‘DIRECT’ indicates that the Publisher (content owner) directly controls the account." For these DIRECT lines, the ad system's own sellers.json lists the account under another company's domain. Allowed when that domain belongs to the same company; add OWNERDOMAIN to make that explicit.

**How to fix**If the account is yours under another domain, declare it with OWNERDOMAIN=<that domain>; otherwise mark it RESELLER.
[Full guide →](https://appsupplyindex.com/fix/direct-account-other-domain)

Evidence (2)

```
line 84     adform.com, 2657, DIRECT, 9f5210a2f0999e32 # #WW #BANNER
             → partner block: #WW #BANNER  domain in sellers.json: the-ozone-project.com  name in sellers.json: The Ozone Project
line 103    openx.com, 540731760, DIRECT, 6a698e2ec38604c6 # Direct - Ozone - PMP #WW #BANNER
             → partner block: Direct - Ozone - PMP #WW #BANNER  domain in sellers.json: the-ozone-project.com  name in sellers.json: Ozone Project Ltd
```

info

### Ad systems whose sellers.json we couldn't read

20

We couldn't read a sellers.json for these ad systems at crawl time (no file, invalid JSON, empty, or automated access refused), so these lines weren't verified. No points are deducted.

**How to fix**Ask the partner to publish sellers.json; until then buyers can't verify that path.
[Full guide →](https://appsupplyindex.com/fix/sellers-json-not-available)

Evidence (20)

```
line 21     sharethrough.com, 4854, DIRECT, d53b998a7bd4ecd2 # Equativ #WW #BANNER,#NATIVE, #INSTREAM
             → partner block: Equativ #WW #BANNER,#NATIVE, #INSTREAM  sellers_json: robots.txt of sharethrough.com disallows crawlers
line 27     indexexchange.com, 184744, DIRECT, 50b1c356f2c5c8fc # IndexExch - DFP/EDBA Bidder #WW #BANNER
             → partner block: IndexExch - DFP/EDBA Bidder #WW #BANNER  sellers_json: robots.txt of cdn.indexexchange.com disallows crawlers
line 28     indexexchange.com, 184224, DIRECT, 50b1c356f2c5c8fc # IndexExch - Wrapper #WW #BANNER
             → partner block: IndexExch - Wrapper #WW #BANNER  sellers_json: robots.txt of cdn.indexexchange.com disallows crawlers
line 29     indexexchange.com, 188607, DIRECT, 50b1c356f2c5c8fc # IndexExch - Prebid #WW #BANNER
             → partner block: IndexExch - Prebid #WW #BANNER  sellers_json: robots.txt of cdn.indexexchange.com disallows crawlers
line 30     indexexchange.com, 206221, DIRECT, 50b1c356f2c5c8fc # IndexExch - Ozone #WW #BANNER
             → partner block: IndexExch - Ozone #WW #BANNER  sellers_json: robots.txt of cdn.indexexchange.com disallows crawlers
line 31     indexexchange.com, 213934, DIRECT, 50b1c356f2c5c8fc # IndexExch - TAM
             → partner block: IndexExch - TAM  sellers_json: robots.txt of cdn.indexexchange.com disallows crawlers
line 37     zetaglobal.net, 989, RESELLER # Nativo
             → partner block: Nativo  sellers_json: HTTP 404
line 52     vi.ai, g-005b778b60d86e93b08cc968758f6ac863, DIRECT # instream video by outbrain #WW #BANNER, #NATIVE
             → partner block: instream video by outbrain #WW #BANNER, #NATIVE  sellers_json: no sellers.json
line 53     indexexchange.com, 193091, RESELLER, 50b1c356f2c5c8fc # Premium video demand from Outbrain #WW #BANNER, #NATIVE
             → partner block: Premium video demand from Outbrain #WW #BANNER, #NATIVE  sellers_json: robots.txt of cdn.indexexchange.com disallows crawlers
line 56     appnexus.com, 7597, RESELLER, f5ab79cb980f11d1 # #WW #BANNER, #NATIVE
             → partner block: #WW #BANNER, #NATIVE  sellers_json: HTTP 403 to automated requests
line 75     appnexus.com, 1314, RESELLER, f5ab79cb980f11d1 # TripleLift Reseller #WW #BANNER
             → partner block: TripleLift Reseller #WW #BANNER  sellers_json: HTTP 403 to automated requests
line 77     appnexus.com, 9979, DIRECT, f5ab79cb980f11d1 # #WW #BANNER
             → partner block: #WW #BANNER  sellers_json: HTTP 403 to automated requests
line 78     appnexus.com, 2542, DIRECT, f5ab79cb980f11d1 # #WW #BANNER, #INSTREAM
             → partner block: #WW #BANNER, #INSTREAM  sellers_json: HTTP 403 to automated requests
line 80     yieldmo.com, 4001862299450024670, DIRECT # Yieldmo - TAM #WW #BANNER
             → partner block: Yieldmo - TAM #WW #BANNER  sellers_json: bot-check or captcha page (HTTP 202)
line 89     yahoo.com, 60170, DIRECT, e1a5b5b6e3255540 # #WW #BANNER
             → partner block: #WW #BANNER  sellers_json: HTTP 429 to automated requests
line 93     yieldmo.com, 3337992342509396649, DIRECT # Yieldmo Ozone #WW #BANNER
             → partner block: Yieldmo Ozone #WW #BANNER  sellers_json: bot-check or captcha page (HTTP 202)
line 101    appnexus.com, 2758, RESELLER, f5ab79cb980f11d1 # #WW #BANNER
             → partner block: #WW #BANNER  sellers_json: HTTP 403 to automated requests
line 102    contextweb.com, 558355, RESELLER, 89ff185a4c4e857c # #WW #BANNER
             → partner block: #WW #BANNER  sellers_json: robots.txt of projects.contextweb.com disallows crawlers
line 107    sharethrough.com, 4011, RESELLER, 060d053dcf45cbf3
             → partner block: Other (via Ozone)  sellers_json: robots.txt of sharethrough.com disallows crawlers
line 111    appnexus.com, 13099, RESELLER, f5ab79cb980f11d1 # #WW #BANNER
             → partner block: #WW #BANNER  sellers_json: HTTP 403 to automated requests
```

info

### Ad system domains that look mistyped

1

These lines name an ad system domain that has no readable sellers.json and is one character away from a domain at least ten times as many companies list (or that domain written twice). Buyers match lines by the exact domain, so a mistyped line authorizes no one. No points are deducted.

**How to fix**Check the line against the one your partner gave you and correct the domain.

Evidence (1)

```
line 38     smaato.con, 1100057947, RESELLER, 07bcf65f187117b4 # Nativo
             → partner block: Nativo  did you mean: smaato.com
```

## Apps

1 app in this index; they all list a developer website on telegraph.co.uk, so buyers read this
app-ads.txt for all of them. 1 is in this week's US charts.

| App | Genre | Store | In the charts |
| --- | --- | --- | --- |
| [The Telegraph: UK & World News](https://appsupplyindex.com/app/ios-388947468) | News | iOS + Android | #47 |

## About this file

app-ads.txt
:   <https://www.telegraph.co.uk/app-ads.txt> · 200

Score
:   B 79/100 · 87 lines · 55 checked against sellers.json

Grouping
:   One file: every app whose store listing points to telegraph.co.uk.
    Store names alone never group publishers.

Checked
:   Nov 16, 2026

### Is this your file?

Changed it? Check any of these apps live; this page updates weekly.
Think something here is wrong? [Request a correction](https://appsupplyindex.com/methodology#corrections).

[Check an app](https://appsupplyindex.com/check)
