Android · WEVERSE COMPANY Inc.

Weverse: Connect with Artists

Developer URL: https://www.weverse.io
app-ads.txt: https://weverse.io/app-ads.txt · 200
Checked: Oct 7, 2026

65/100

103 lines · 71 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

5 −18 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 49     teads.tv, 13576, DIRECT, 15a9c44f6d26cbe1
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 65 different companies  name in sellers.json: Premium Publicidade e Marketing Ltda  domain in sellers.json: premiumads.com.br
line 66     onetag.com, 5adaad445a0a050, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 63 different companies  name in sellers.json: Premium Publicidade e Marketing LTDA  domain in sellers.json: premiumads.com.br
line 67     onetag.com, 5adaad445a0a050-OB, DIRECT
             → observed: the same account is marked DIRECT by 63 different companies
line 77     criteo.com, B-064291, DIRECT, 9fac4a4a87c2a44f
             → observed: the same account is marked DIRECT by 67 different companies
line 78     themediagrid.com, DKRL8Y, DIRECT, 35d5010d7789b49d
             → observed: the same account is marked DIRECT by 64 different companies

warning

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

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

line 46     pubmatic.com, 156378, RESELLER, 5d62403b186f2ace
             → sellers_json: https://pubmatic.com/sellers.json
line 51     smartclip.net, 10870, RESELLER
             → sellers_json: https://smartclip.net/sellers.json
line 59     themediagrid.com, 2BYX51, RESELLER, 35d5010d7789b49d
             → sellers_json: https://themediagrid.com/sellers.json
line 61     rubiconproject.com, 15478, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 62     rubiconproject.com, 22824, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 67     onetag.com, 5adaad445a0a050-OB, DIRECT
             → sellers_json: https://onetag.com/sellers.json
line 78     themediagrid.com, DKRL8Y, DIRECT, 35d5010d7789b49d
             → sellers_json: https://themediagrid.com/sellers.json
line 84     improvedigital.com, 1969, RESELLER
             → sellers_json: https://improvedigital.com/sellers.json
line 95     smartadserver.com, 4012, RESELLER
             → sellers_json: https://smartadserver.com/sellers.json
line 96     smartadserver.com, 4071, RESELLER
             → sellers_json: https://smartadserver.com/sellers.json
line 97     smartadserver.com, 4073, RESELLER
             → sellers_json: https://smartadserver.com/sellers.json
line 98     smartadserver.com, 4072, RESELLER
             → sellers_json: https://smartadserver.com/sellers.json

warning

Lines for ad system domains that don't resolve

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

line 56     spotxchange.com,151986,RESELLER,7842df1d2fe2db34
             → ad_system: spotxchange.com

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

line 2      facebook.com, 1351773517098183, DIRECT, c3e20eee3f780d68
             → sellers_json: HTML or login page instead of JSON
line 7      gamaigroup.com, 423056, RESELLER
             → sellers_json: HTML or login page instead of JSON
line 10     loopme.com, 11303, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 11     loopme.com, 11424, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 14     openx.com, 540785403, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 15     openx.com, 559798512, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 50     appnexus.com, 9794, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 54     dynadmic.com,4133288916,RESELLER
             → sellers_json: HTML or login page instead of JSON
line 58     criteo.com, B-059922, RESELLER, 9fac4a4a87c2a44f
             → sellers_json: HTTP 403
line 63     openx.com, 539372716, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 64     openx.com, 539417470, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 65     openx.com, 542117415, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 68     advertising.com, 28246, RESELLER
             → sellers_json: HTTP 403
line 70     freewheel.tv, 20393, RESELLER
             → sellers_json: HTTP 403
line 71     freewheel.tv, 24377, RESELLER
             → sellers_json: HTTP 403
line 73     aol.com, 58905, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 404
line 74     appnexus.com, 13099, RESELLER
             → sellers_json: HTTP 403
line 77     criteo.com, B-064291, DIRECT, 9fac4a4a87c2a44f
             → sellers_json: HTTP 403
line 79     aol.com, 55681, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 404
line 81     aol.com, 55032, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 404
line 87     openx.com, 538959099, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 91     appnexus.com, 1019, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 101    openx.com, 537149888, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 102    appnexus.com, 3703, RESELLER, f5ab79cb980f11d1
             → 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