iOS · Societe Editrice du Monde

Le Monde, Live News

Developer URL: https://www.lemonde.fr/en/
app-ads.txt: https://www.lemonde.fr/app-ads.txt · 200
Checked: Oct 7, 2026

81/100

110 lines · 79 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

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

line 16     triplelift.com, 5765-EB, DIRECT, 6c33edb13117fd86 #OB-TL
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Le Monde (via EB Network)  domain in sellers.json: google.com
line 19     rubiconproject.com, 19360, DIRECT, 0bfd66d529a55807 #OB-MAGNITE
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Google  domain in sellers.json: google.com
line 103    xandr.com, 4009, DIRECT, f5ab79cb980f11d1
             → observed: the same account is marked DIRECT by 21 different companies  name in sellers.json: Seedtag Advertising SL  domain in sellers.json: seedtag.com
line 104    smartadserver.com, 3050, DIRECT
             → observed: the same account is marked DIRECT by 22 different companies  name in sellers.json: Seedtag  domain in sellers.json: seedtag.com
line 105    rubiconproject.com, 17280, DIRECT, 0bfd66d529a55807
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 20 different companies  name in sellers.json: Seedtag Advertising SL  domain in sellers.json: seedtag.com
line 106    pubmatic.com, 157743, DIRECT, 5d62403b186f2ace
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 22 different companies  name in sellers.json: Seedtag Advertising, S.L.  domain in sellers.json: seedtag.com
line 135    yieldlab.net, 495507, DIRECT #instream video by outbrain
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 5 different companies  name in sellers.json: audienzz AG  domain in sellers.json: audienzz.com

warning

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

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

line 20     smartadserver.com, 690-OB, RESELLER, 060d053dcf45cbf3 #OB-Equativ
             → sellers_json: https://smartadserver.com/sellers.json
line 21     sharethrough.com, 690-OB, RESELLER, d53b998a7bd4ecd2
             → sellers_json: https://sharethrough.com/sellers.json
line 32     smartadserver.com, 690-OB, RESELLER, 060d053dcf45cbf3
             → sellers_json: https://smartadserver.com/sellers.json
line 76     themediagrid.com,NB56PT,RESELLER,9fac4a4a87c2a44f
             → sellers_json: https://themediagrid.com/sellers.json
line 130    xandr.com, 7445, RESELLER #instream video by outbrain
             → sellers_json: https://xandr.com/sellers.json
line 137    xandr.com, 12279,RESELLER #instream video by outbrain
             → sellers_json: https://xandr.com/sellers.json
line 142    stroeer.com, 18840, RESELLER #instream video by outbrain
             → sellers_json: https://stroeer.com/sellers.json

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 112    spotxchange.com, 225721, RESELLER # Premium video demand
             → ad_system: spotxchange.com
line 139    spotxchange.com, 113481, RESELLER, 7842df1d2fe2db34 #instream video by outbrain
             → ad_system: spotxchange.com

info

Duplicate lines

1 −1 pts

Harmless but a sign of copy-paste maintenance.

How to fixRemove duplicates; keep one copy of each line.

Evidence (1)

ad_system: smartadserver.com  seller_id: 690-ob  relationship: RESELLER

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 9      appnexus.com, 8499, DIRECT, f5ab79cb980f11d1 #PB-Xandr
             → sellers_json: HTTP 403
line 17     appnexus.com, 1314, RESELLER #OB-TL
             → sellers_json: HTTP 403
line 36     openx.com, 537149888, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 37     appnexus.com, 3703, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 38     loopme.com, 5679, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 50     ogury.com, 4b8e1c28-161f-446c-8b6c-3a16c3f88453, DIRECT #OGURY
             → sellers_json: HTTP 403
line 51     appnexus.com, 11470, RESELLER #OGURY
             → sellers_json: HTTP 403
line 70     appnexus.com,1608,RESELLER,f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 71     appnexus.com,3500,RESELLER,f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 72     appnexus.com,8494,RESELLER,f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 87     appnexus.com, 8233, RESELLER
             → sellers_json: HTTP 403
line 99     facebook.com, 901507522935668, DIRECT, c3e20eee3f780d68
             → sellers_json: HTML or login page instead of JSON
line 107    openx.com, 558758631, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 111    appnexus.com, 7597, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 115    openx.com, 540393169, RESELLER, 6a698e2ec38604c6 # Premium video demand
             → sellers_json: HTTP 403
line 123    vi.ai, g-00d823dcf45be4df80b0c478ec66dbf00e, DIRECT #instream video by outbrain
             → sellers_json: HTTP 404
line 125    rhythmone.com, 1014191143, RESELLER, a670c89d4a324e47 #instream video by outbrain
             → sellers_json: HTTP 403
line 127    openx.com, 540362347, RESELLER, 6a698e2ec38604c6 #instream video by outbrain
             → sellers_json: HTTP 403
line 141    openx.com, 537148817, RESELLER,6a698e2ec38604c6 #instream video by outbrain
             → 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