Android · Bloomberg LP CM

Bloomberg: Finance Market News

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

84/100

99 lines · 54 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

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

line 7      aps.amazon.com, c317c4b2-d88e-4a30-8aa4-9b27ceff6e2f, DIRECT
             → sellers_json: https://aps.amazon.com/sellers.json
line 12     google.com, pub-4374325730921577, DIRECT, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 16     rubiconproject.com, 12728, DIRECT, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 53     video.unrulymedia.com, 1770453816, RESELLER
             → sellers_json: https://video.unrulymedia.com/sellers.json
line 93     video.unrulymedia.com , 2564526802, RESELLER, 6f752381ad5ec0e5
             → sellers_json: https://video.unrulymedia.com/sellers.json

warning

DIRECT lines inconsistent with public data

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

line 17     rubiconproject.com, 21418, DIRECT, 0bfd66d529a55807
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Google  domain in sellers.json: google.com
line 21     triplelift.com, 1066-EB, DIRECT, 6c33edb13117fd86
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: bloomberg (via EB Network)  domain in sellers.json: google.com
line 33     tritondigital.com, 7943, DIRECT, 19b4454d0b87b58b
             → observed: the same account is marked DIRECT by 3 different companies  name in sellers.json: iHeartMedia  domain in sellers.json: iheart.com
line 72     freewheel.tv, 531516, DIRECT
             → observed: the same account is marked DIRECT by 4 different companies
line 111    applovin.com, 2713cc543ecb0969b83e3fdbf9ff011f, DIRECT
             → observed: the same account is marked DIRECT by 19 different companies  name in sellers.json: Wurl, Inc  domain in sellers.json: wurl.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 8      engagebdr.com, 16, RESELLER
             → ad_system: engagebdr.com
line 31     spotxchange.com, 233403, RESELLER, 7842df1d2fe2db34
             → ad_system: spotxchange.com

info

DIRECT accounts registered to another domain

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

line 18     telaria.com, ctmc5-qsxn1, DIRECT, 1a4e959a1b50034a
             → domain in sellers.json: bloombergmedia.com  name in sellers.json: Bloomberg
line 19     tremorhub.com, ctmc5-qsxn1, DIRECT, 1a4e959a1b50034a
             → domain in sellers.json: bloombergmedia.com  name in sellers.json: Bloomberg
line 77     telaria.com, ctmc5-nyisd, DIRECT, 1a4e959a1b50034a
             → domain in sellers.json: bloombergmedia.com  name in sellers.json: Bloomberg
line 78     tremorhub.com, ctmc5-nyisd, DIRECT, 1a4e959a1b50034a
             → domain in sellers.json: bloombergmedia.com  name in sellers.json: Bloomberg
line 81     telaria.com  , ctmc5-gayqk, DIRECT, 1a4e959a1b50034a
             → domain in sellers.json: bloombergmedia.com  name in sellers.json: Bloomberg
line 82     tremorhub.com , ctmc5-gayqk, DIRECT, 1a4e959a1b50034a
             → domain in sellers.json: bloombergmedia.com  name in sellers.json: Bloomberg

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 (25 of 30)

line 4      adcolony.com, 496220845654deec, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTML or login page instead of JSON
line 5      appnexus.com, 8355, DIRECT
             → sellers_json: HTTP 403
line 9      groundtruth.com, 241, RESELLER, 81cbf0a75a5e0e9a
             → sellers_json: HTTP 403
line 15     rhythmone.com, 4201299756, RESELLER, a670c89d4a324e47
             → sellers_json: HTTP 403
line 27     freewheel.tv, 1522610, RESELLER
             → sellers_json: HTTP 403
line 28     freewheel.tv, 1522818, RESELLER
             → sellers_json: HTTP 403
line 36     appnexus.com, 1577, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 47     appnexus.com, 13779, RESELLER
             → sellers_json: HTTP 403
line 49     freewheel.tv, 1119233, RESELLER
             → sellers_json: HTTP 403
line 58     freewheel.tv, 1598940, RESELLER
             → sellers_json: HTTP 403
line 59     lgads.tv, 475902, RESELLER
             → sellers_json: HTTP 403
line 62     freewheel.tv, sg1256375, DIRECT
             → sellers_json: HTTP 403
line 63     freewheel.tv, 533599-d-523319, DIRECT
             → sellers_json: HTTP 403
line 64     freewheel.tv, 533599, DIRECT
             → sellers_json: HTTP 403
line 65     freewheel.tv, 533599-523319, DIRECT
             → sellers_json: HTTP 403
line 66     freewheel.tv, 533599-524565, DIRECT
             → sellers_json: HTTP 403
line 67     freewheel.tv, 533599-539372, DIRECT
             → sellers_json: HTTP 403
line 68     freewheel.tv, 533599-512029, DIRECT
             → sellers_json: HTTP 403
line 69     freewheel.tv, 539372, RESELLER
             → sellers_json: HTTP 403
line 72     freewheel.tv, 531516, DIRECT
             → sellers_json: HTTP 403
line 73     freewheel.tv, 531516, RESELLER
             → sellers_json: HTTP 403
line 79     openx.com, 564215253, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 80     openx.com, 540158162, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 83     freewheel.tv, 533599-d-524565, DIRECT
             → sellers_json: HTTP 403
line 89     openx.com , 537149888, RESELLER, 6a698e2ec38604c6
             → 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