Android · Bandai Namco Entertainment Inc.

DRAGON BALL LEGENDS

Developer URL: https://www.bandainamcoent.co.jp/english/
app-ads.txt: https://www.bandainamcoent.co.jp/app-ads.txt · 200
Checked: Oct 7, 2026

66/100

150 lines · 66 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

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

line 4      rubiconproject.com, 12286, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 5      webeyemob.com, 70096, RESELLER
             → sellers_json: https://www.webeyemob.com/sellers.json
line 9      video.unrulymedia.com, 123476257, RESELLER
             → sellers_json: https://video.unrulymedia.com/sellers.json
line 45     rubiconproject.com, 21526, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 47     rubiconproject.com, 14334, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 63     kidoz.net, 19692013, RESELLER
             → sellers_json: https://kidoz.net/sellers.json
line 65     lemmatechnologies.com, 552, RESELLER, 7829010c5bebd1fb
             → sellers_json: https://lemmatechnologies.com/sellers.json
line 66     lemmatechnologies.com, 144, RESELLER, 7829010c5bebd1fb
             → sellers_json: https://lemmatechnologies.com/sellers.json
line 75     video.unrulymedia.com, 3630748062, RESELLER, a670c89d4a324e47
             → sellers_json: https://video.unrulymedia.com/sellers.json
line 87     Improvedigital.com, 912, DIRECT
             → sellers_json: https://improvedigital.com/sellers.json
line 88     Improvedigital.com, 1887, RESELLER
             → sellers_json: https://improvedigital.com/sellers.json
line 99     quantumdex.io, EXU5984, RESELLER
             → sellers_json: https://quantumdex.io/sellers.json
line 101    sonobi.com, 783272317b, RESELLER, d1a215d9eb5aee9e
             → sellers_json: https://sonobi.com/sellers.json
line 107    google.com, pub-3003745923834998, RESELLER
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 109    tremorhub.com, rwd19-2474532, RESELLER, 1a4e959a1b50034a
             → sellers_json: https://tremorhub.com/sellers.json
line 110    google.com, pub-3563430191325467, RESELLER
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 112    tremorhub.com, rwd19-1260154, RESELLER, 1a4e959a1b50034a
             → sellers_json: https://tremorhub.com/sellers.json
line 113    applovin.com, 07cfdfad16500b7f2e50b87e50e37e08, DIRECT
             → sellers_json: https://applovin.com/sellers.json
line 150    google.com, pub-1151726480167007, DIRECT, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json

warning

DIRECT lines inconsistent with public data

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

line 15     pubmatic.com, 160565, DIRECT, 5d62403b186f2ace
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 42 different companies  name in sellers.json: Tapjoy  domain in sellers.json: tapjoy.com
line 16     pangleglobal.com, 9898, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 40 different companies  name in sellers.json: Tapjoy, Inc.  domain in sellers.json: fingersoft.com
line 20     synacor.com, 82460, DIRECT, e108f11b2cdf7d5b
             → observed: the same account is marked DIRECT by 47 different companies
line 29     pubmatic.com, 159078, DIRECT, 5d62403b186f2ace
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 9 different companies  name in sellers.json: Adtarget Medya AS  domain in sellers.json: adtarget.com.tr
line 58     admixer.net, 4ca083cd-412f-49fe-b832-5b66ee490d9a, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 4 different companies  name in sellers.json: Unity (B)  domain in sellers.json: unity3d.com
line 87     Improvedigital.com, 912, DIRECT
             → observed: the same account is marked DIRECT by 8 different companies
line 103    adtarget.com.tr, 306742, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 4 different companies  name in sellers.json: Admixer EU GmbH  domain in sellers.json: admixer.com
line 104    admatic.com.tr, adm-pub-185375301865, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 11 different companies  name in sellers.json: AdTarget Teknoloji A.Ş.  domain in sellers.json: adtarget.biz
line 105    adform.com, 2600, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 11 different companies  name in sellers.json: ADTARGET MEDYA A.S.  domain in sellers.json: adtarget.com.tr
line 106    stroeer.com, 17938, DIRECT
             → observed: the same account is marked DIRECT by 11 different companies  name in sellers.json: AdTarget Medya A.Ş.  domain in sellers.json: adtarget.com.tr

warning

Lines for ad system domains that don't resolve

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

line 48     reforge.in, 107, RESELLER
             → ad_system: reforge.in
line 49     reforge.in, 353, RESELLER
             → ad_system: reforge.in
line 78     districtm.io, 102098, RESELLER, 3fd707be9c4527c3
             → ad_system: districtm.io
line 79     districtm.io, 102058, RESELLER, 3fd707be9c4527c3
             → ad_system: districtm.io

info

No OWNERDOMAIN declared

1 −2 pts

app-ads.txt 1.1 recommends OWNERDOMAIN so buyers can match DIRECT accounts to the owner.

How to fixAdd OWNERDOMAIN=<your company domain> to the file.

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 64)

line 1      facebook.com, 834100976609029, DIRECT, c3e20eee3f780d68
             → sellers_json: returns a web page, not a sellers.json file
line 3      tapjoy.com, 5908adf550bb4836a3d90f8def60d13f, DIRECT, 29e595b1aeb5904d
             → sellers_json: returns a web page, not a sellers.json file
line 6      openx.com, 540679900, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 7      adcolony.com, 801e49d1be83b5f9, RESELLER, 1ad675c9de6b5176
             → sellers_json: returns a web page, not a sellers.json file
line 11     appnexus.com, 6849, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 13     rhythmone.com, 123476257, RESELLER, a670c89d4a324e47
             → sellers_json: HTTP 403 to automated requests
line 19     smartadserver.com, 4052, RESELLER
             → sellers_json: HTTP 404
line 21     aol.com, 58935, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 404
line 22     yahoo.com, 58935, RESELLER, e1a5b5b6e3255540oper
             → sellers_json: HTTP 429 to automated requests
line 25     loopme.com, 9621, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403 to automated requests
line 26     adcolony.com, 0a0f72cd66122f31, RESELLER, 1ad675c9de6b5176
             → sellers_json: returns a web page, not a sellers.json file
line 38     spotx.tv, 117872, RESELLER, 7842df1d2fe2db34
             → sellers_json: HTTP 403 to automated requests
line 39     spotx.tv, 85519, RESELLER, 7842df1d2fe2db34
             → sellers_json: HTTP 403 to automated requests
line 40     openx.com, 540871654, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 41     openx.com, 540838151, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 42     openx.com, 541031350, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 52     appnexus.com, 7353, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 53     appnexus.com, 2764, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 54     appnexus.com, 10617, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 55     appnexus.com, 9393, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 60     smartadserver.com, 3564, RESELLER
             → sellers_json: HTTP 404
line 61     pubnative.net, 1006955, RESELLER, d641df8625486a7b
             → sellers_json: HTTP 403 to automated requests
line 62     pubnative.net, 1007040, RESELLER, d641df8625486a7b
             → sellers_json: HTTP 403 to automated requests
line 74     rhythmone.com, 3630748062, RESELLER, a670c89d4a324e47
             → sellers_json: HTTP 403 to automated requests
line 89     aol.com, 57992, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 404

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