App Supply Index Monitor my app
iOS · Pinger, Inc.

Text Free: Second Phone Number

Developer URL
http://www.pinger.com
app-ads.txt
http://www.pinger.com/app-ads.txt · 200
Checked
Oct 7, 2026
B
87/100

148 lines · 115 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

11 −8 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 (11) 
line 33     improvedigital.com, 2720, RESELLER
             → sellers_json: https://improvedigital.com/sellers.json
line 42     smaato.com, 1100001601, DIRECT, 07bcf65f187117b4
             → sellers_json: https://smaato.com/sellers.json
line 63     google.com, pub-3940256099942544, DIRECT, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 76     telaria.com, h1g6u-sjtzr, DIRECT, 1a4e959a1b50034a
             → sellers_json: https://telaria.com/sellers.json
line 79     tremorhub.com, h1g6u-sjtzr, DIRECT, 1a4e959a1b50034a
             → sellers_json: https://tremorhub.com/sellers.json
line 131    ushareit.com, LC98ffe3f38a46423e, RESELLER
             → sellers_json: https://ushareit.com/sellers.json
line 139    media.net, 8CUC0721K, RESELLER
             → sellers_json: https://media.net/sellers.json
line 157    spinx.biz, 1373698867, RESELLER
             → sellers_json: https://spinx.biz/sellers.json
line 172    rhebus.works, 3852728940, RESELLER
             → sellers_json: https://rhebus.works/sellers.json
line 178    algorix.co, 604680, Direct, 5b394c12fea27a1d
             → sellers_json: https://algorix.co/sellers.json
line 193    thunder-monetize.com, 9630185716, RESELLER
             → sellers_json: https://thunder-monetize.com/sellers.json
warning

DIRECT lines inconsistent with public data

3 −2 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 (3) 
line 43     smaato.com, 1100004890, DIRECT, 07bcf65f187117b4
             → observed: the same account is marked DIRECT by 163 different companies  name in sellers.json: Smaato Managed  domain in sellers.json: smaato.com
line 63     google.com, pub-3940256099942544, DIRECT, f08c47fec0942fa0
             → observed: the same account is marked DIRECT by 38 different companies
line 178    algorix.co, 604680, Direct, 5b394c12fea27a1d
             → observed: the same account is marked DIRECT by 5 different companies
warning

Malformed lines

1 −1 pts

Lines that buyers' crawlers will ignore.

How to fixFix the format: <ad system domain>, <seller id>, DIRECT|RESELLER[, <cert authority id>].
Evidence (1) 
line 167    gitberry.com, RESELLER, 816110171
             → reason: relationship must be DIRECT or RESELLER, got '816110171'
info

Duplicate lines

4 −1 pts

Harmless but a sign of copy-paste maintenance.

How to fixRemove duplicates; keep one copy of each line.
Evidence (4) 
ad_system: programmaticx.ai  seller_id: 6845438  relationship: RESELLER
ad_system: video.unrulymedia.com  seller_id: 2148207460  relationship: RESELLER
ad_system: smartadserver.com  seller_id: 4625  relationship: RESELLER
ad_system: triplelift.com  seller_id: 12158  relationship: RESELLER
info

DIRECT accounts registered to another domain

1 −1 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 99     applovin.com, 4fdb1b89aba988d33d26f276085a012e, DIRECT
             → domain in sellers.json: textfree.us  name in sellers.json: Pinger
info

Ad systems without a public sellers.json

18

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 (18) 
line 7      facebook.com, 10152633923977910, RESELLER, c3e20eee3f780d68
             → sellers_json: returns a web page, not a sellers.json file
line 8      facebook.com, 1066141964038159, RESELLER, c3e20eee3f780d68
             → sellers_json: returns a web page, not a sellers.json file
line 9      facebook.com, 949760131750117, RESELLER, c3e20eee3f780d68
             → sellers_json: returns a web page, not a sellers.json file
line 10     facebook.com, 174781446055971, RESELLER, c3e20eee3f780d68
             → sellers_json: returns a web page, not a sellers.json file
line 21     mopub.com, b6d5242bd93f48dcae548e23103a51a0, DIRECT, 74b46c0ea83967ca
             → sellers_json: returns a web page, not a sellers.json file
line 35     alaska-gaming.com, 17116, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 36     zetaglobal.net, 808, RESELLER
             → sellers_json: HTTP 404
line 90     aol.com, 1120, DIRECT, e1a5b5b6e3255540
             → sellers_json: HTTP 404
line 102    vungle.com, 62b9ac4282628b001b5ab74a, DIRECT, c107d686becd2d77
             → sellers_json: HTTP 403 to automated requests
line 110    startapp.com, 190658257, DIRECT
             → sellers_json: HTTP 404 (served over plain HTTP only)
line 120    zetaglobal.net, 633, RESELLER
             → sellers_json: HTTP 404
line 127    yieldmo.com, 3590879766707642794, RESELLER
             → sellers_json: bot-check or captcha page (HTTP 202)
line 134    bematterfull.com, 792278057361, RESELLER
             → sellers_json: bot-check or captcha page (HTTP 202)
line 136    onlinemediasolutions.com, 43234, RESELLER, b3868b187e4b6402
             → sellers_json: bot-check or captcha page (HTTP 202)
line 143    sabio.us, 100201, RESELLER, 96ed93aaa9795702
             → sellers_json: HTTP 404
line 158    lunamedia.io, 193bca549318aed0434226d4d73e13f3, RESELLER, 524ecb396915caaf
             → sellers_json: bot-check or captcha page (HTTP 202)
line 171    onlinemediasolutions.com, 29559, RESELLER
             → sellers_json: bot-check or captcha page (HTTP 202)
line 204    gamaigroup.com, 423059, RESELLER
             → sellers_json: file is not valid JSON
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 61     google.com, pub-3285741363974337, 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