iOS · South China Morning Post Publishers Limited

South China Morning Post: News

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

83/100

51 lines · 27 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

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

line 14     rubiconproject.com, 18832, DIRECT, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 29     themediagrid.com, DXW9CT, RESELLER, 35d5010d7789b49d
             → sellers_json: https://themediagrid.com/sellers.json
line 65     video.unrulymedia.com, 2564526802, RESELLER
             → sellers_json: https://video.unrulymedia.com/sellers.json

warning

DIRECT lines inconsistent with public data

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

line 24     triplelift.com, 6476-EB, Direct, 6c33edb13117fd86
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: South China Morning Post (via EB Network)  domain in sellers.json: google.com
line 38     Media.net, 8CUL0V7OR, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: South China Morning Post (via OB)  domain in sellers.json: google.com
line 73     google.com, pub-9685734445476814, DIRECT, f08c47fec0942fa0
             → observed: the same account is marked DIRECT by 3 different companies  name in sellers.json: Sharethrough Inc

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

line 17     openx.com, 540964127, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 19     openx.com, 564135948, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 21     openx.com, 561453557, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 30     appnexus.com, 17535, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 33     openx.com, 558595797, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 34     freewheel.tv, 1585055, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 35     freewheel.tv, 1585058, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 46     loopme.com, 11498, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403 to automated requests
line 48     smartadserver.com, 4839, RESELLER, 060d053dcf45cbf3
             → sellers_json: HTTP 404
line 51     smartadserver.com, 5922, DIRECT, 060d053dcf45cbf3
             → sellers_json: HTTP 404
line 53     smartadserver.com, 5922-OB, RESELLER, 060d053dcf45cbf3
             → sellers_json: HTTP 404
line 58     openx.com, 537149888, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 59     appnexus.com, 3703, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 60     loopme.com, 5679, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403 to automated requests
line 61     smaato.com, 1100044045, RESELLER, 07bcf65f187117b4
             → sellers_json: HTTP 403 to automated requests
line 68     ogury.com, ede8d6ba-5a3f-4dfa-85aa-8cfb3c42f970, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 69     xad.com, 958, RESELLER, 81cbf0a75a5e0e9a
             → sellers_json: HTTP 403 to automated requests
line 70     pubnative.net, 1006576, RESELLER, d641df8625486a7b
             → sellers_json: HTTP 403 to automated requests
line 71     verve.com, 15503, RESELLER, 0c8f5958fc2d6270
             → sellers_json: HTTP 403 to automated requests

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