App Supply Index Monitor my app
Android · Lonsen Electronics Limited

Seeing

Developer URL
https://www.seeing.store/
app-ads.txt
https://seeing.store/app-ads.txt · 200
Checked
Oct 7, 2026
C
70/100

38 lines · 32 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

1 −20 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 (1)
line 1      google.com, pub-9710615273138410, DIRECT, f08c47fec0942fa0
             → observed: the same account is marked DIRECT by 3 different companies
info

DIRECT accounts registered to another domain

1 −8 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 (1)
line 2      applovin.com, 165e4a7a6318a24c0ac18909c491d03d, DIRECT
             → domain in sellers.json: kement.cc  name in sellers.json: WIT ELECTRONICS LIMITED
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

5

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 (5)
line 5      gamaigroup.com, 423056, RESELLER
             → sellers_json: HTML or login page instead of JSON
line 8      loopme.com, 11303, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 9      loopme.com, 11424, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 12     openx.com, 540785403, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 13     openx.com, 559798512, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
info

DIRECT accounts marked confidential

1

Buyers can't see who owns these accounts.

How to fixAsk the ad system to publish your seller entry with name and domain.
Evidence (1)
line 1      google.com, pub-9710615273138410, DIRECT, f08c47fec0942fa0

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