App Supply Index Monitor my app
iOS · SHANTANU PTE. LTD.

Peachy - AI Face & Body Editor

Developer URL
http://inshot.cc/
app-ads.txt
https://inshot.cc/app-ads.txt · 200
Checked
Oct 7, 2026
C
61/100

2,977 lines · 2,156 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

38 −17 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 (25 of 38) 
line 1      google.com, pub-3940256099942544, DIRECT, f08c47fec0942fa0
             → observed: the same account is marked DIRECT by 39 different companies
line 14     33across.com, 0015a00003DKg9ZAAT, DIRECT
             → observed: the same account is marked DIRECT by 10 different companies  name in sellers.json: BetweenX  domain in sellers.json: betweendigital.com
line 22     adriver.ru, 1009202, DIRECT
             → observed: the same account is marked DIRECT by 10 different companies
line 29     algorix.co, 60337, DIRECT
             → observed: the same account is marked DIRECT by 10 different companies
line 39     betweendigital.com, 44229, DIRECT
             → observed: the same account is marked DIRECT by 10 different companies  name in sellers.json: MGL MY.COM (CYPRUS) LIMITED  domain in sellers.json: my.com
line 41     betweendigital.com, 46880, DIRECT
             → observed: the same account is marked DIRECT by 10 different companies
line 48     bigo.sg, 880, DIRECT
             → observed: the same account is marked DIRECT by 11 different companies
line 69     ignitemediatech.com, pub_63615, DIRECT
             → observed: the same account is marked DIRECT by 10 different companies  name in sellers.json: Game Maker Ltd.  domain in sellers.json: gmaker.top
line 88     madex.world, 544b4c02-bccb-47eb-a8c2-0a6be081778b, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 68 different companies  name in sellers.json: Madex  domain in sellers.json: madex.world
line 89     mangomob.net, 5000671969, DIRECT
             → observed: the same account is marked DIRECT by 10 different companies  name in sellers.json: betweendigital  domain in sellers.json: betweendigital.com
line 92     mediasniper.ru, 273000370, DIRECT
             → observed: the same account is marked DIRECT by 10 different companies
line 108    orbrx.ai, 8000869124, DIRECT
             → observed: the same account is marked DIRECT by 10 different companies
line 162    yabbi.me, 675d9254-4032-47ed-9074-b6ef4dbab522, DIRECT
             → observed: the same account is marked DIRECT by 68 different companies
line 216    smaato.com, 1100004890, DIRECT, 07bcf65f187117b4
             → observed: the same account is marked DIRECT by 165 different companies  name in sellers.json: Smaato Managed  domain in sellers.json: smaato.com
line 246    pubmatic.com, 160832, DIRECT, 5d62403b186f2ace
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 4 different companies  name in sellers.json: Hangzhou Inshot Tech Co.,Ltd (via EB)  domain in sellers.json: google.com
line 521    mars.media, 107876, DIRECT, 8624339f102fb076
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 47 different companies  name in sellers.json: Smaato Inc.  domain in sellers.json: smaato.com
line 525    pubmatic.com, 159856, DIRECT, 5d62403b186f2ace
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 22 different companies  name in sellers.json: Google LLC (via EB)  domain in sellers.json: google.com
line 536    zeststack.com, 396, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 5 different companies  name in sellers.json: kprofiles.com  domain in sellers.json: kprofiles.com
line 548    onetag.com, 72b20ec05ea6e86, DIRECT
             → observed: the same account is marked DIRECT by 24 different companies
line 590    airnowmedia.com, ANM013, DIRECT
             → observed: the same account is marked DIRECT by 16 different companies
line 593    betweendigital.com, 44197, DIRECT
             → observed: the same account is marked DIRECT by 15 different companies  name in sellers.json: Estetik Yayincilik AS  domain in sellers.json: www.sozcu.com.tr
line 813    xandr.com,12745,DIRECT,f5ab79cb980f11d1
             → observed: the same account is marked DIRECT by 10 different companies
line 844    soloway.ru, 2791629, DIRECT
             → observed: the same account is marked DIRECT by 3 different companies
line 1508   google.com, pub-3990748024667386, DIRECT, f08c47fec0942fa0
             → observed: the same account is marked DIRECT by 85 different companies
line 1558   opera.com, pub8625217480640, DIRECT, 55a0c5fd61378de3
             → observed: the same account is marked DIRECT by 10 different companies
warning

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

355 −13 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 (25 of 355) 
line 1      google.com, pub-3940256099942544, DIRECT, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 5      google.com, pub-7914773627795837, DIRECT, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 10     google.com, pub-1840996108607928, DIRECT, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 19     admanmedia.com, 1009, RESELLER
             → sellers_json: https://admanmedia.com/sellers.json
line 21     admixer.net, 2878f07c-cc3f-4f8a-a26c-8e6033a539a6, RESELLER
             → sellers_json: https://admixer.net/sellers.json
line 25     adview.com, 53849096, RESELLER
             → sellers_json: https://adview.com/sellers.json
line 26     adwmg.com, 14037806, RESELLER
             → sellers_json: https://adwmg.com/sellers.json
line 28     algorix.co, 60322, RESELLER
             → sellers_json: https://algorix.co/sellers.json
line 29     algorix.co, 60337, DIRECT
             → sellers_json: https://algorix.co/sellers.json
line 33     axonix.com, 56222, RESELLER
             → sellers_json: https://axonix.com/sellers.json
line 34     betweendigital.com, 43092, RESELLER
             → sellers_json: https://betweendigital.com/sellers.json
line 41     betweendigital.com, 46880, DIRECT
             → sellers_json: https://betweendigital.com/sellers.json
line 44     bidease.com, 14037806, DIRECT
             → sellers_json: https://bidease.com/sellers.json
line 51     chocolateplatform.com, 14630, RESELLER
             → sellers_json: https://chocolateplatform.com/sellers.json
line 58     e-planning.net, 949b688810cb7439, RESELLER
             → sellers_json: https://e-planning.net/sellers.json
line 59     e-planning.net, b9165ad221c51225, RESELLER
             → sellers_json: https://e-planning.net/sellers.json
line 67     ignitemediatech.com, 14037806, RESELLER
             → sellers_json: https://ignitemediatech.com/sellers.json
line 94     mintegral.com, 14037806, DIRECT
             → sellers_json: https://mintegral.com/sellers.json
line 98     onetag.com, 59d216e971852f2, RESELLER
             → sellers_json: https://onetag.com/sellers.json
line 113    pubmatic.com, 14037806, RESELLER
             → sellers_json: https://pubmatic.com/sellers.json
line 118    pubmatic.com, 159668, RESELLER
             → sellers_json: https://pubmatic.com/sellers.json
line 126    pubnative.net, 1007803, RESELLER
             → sellers_json: https://pubnative.net/sellers.json
line 133    rubiconproject.com, 19724, RESELLER
             → sellers_json: https://rubiconproject.com/sellers.json
line 139    smaato.com, 1100042823, RESELLER
             → sellers_json: https://smaato.com/sellers.json
line 151    triplelift.com, 8446, RESELLER
             → sellers_json: https://triplelift.com/sellers.json
warning

Lines for ad system domains that don't resolve

38 −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 (25 of 38) 
line 43     bid.mindtos, 14037806, DIRECT
             → ad_system: bid.mindtos
line 63     gamoshi.io, 267-b4800, RESELLER
             → ad_system: gamoshi.io
line 78     lacunaads.com, 14037806, DIRECT
             → ad_system: lacunaads.com
line 187    spotxchange.com, 117872, RESELLER, 7842df1d2fe2db34
             → ad_system: spotxchange.com
line 195    reforge.in, 107, RESELLER
             → ad_system: reforge.in
line 227    engagebdr.com, 16, RESELLER
             → ad_system: engagebdr.com
line 284    engagebdr.com,10181,reseller
             → ad_system: engagebdr.com
line 285    engagebdr.com,10252,reseller
             → ad_system: engagebdr.com
line 286    engagebdr.com,7,reseller
             → ad_system: engagebdr.com
line 287    engagebdr.com,84,reseller
             → ad_system: engagebdr.com
line 332    spotxchange.com,234183,reseller,7842df1d2fe2db34
             → ad_system: spotxchange.com
line 333    spotxchange.com,99441,reseller,7842df1d2fe2db34
             → ad_system: spotxchange.com
line 364    pubwheel.com,32076181,reseller,1b2cc038a11ea319
             → ad_system: pubwheel.com
line 382    districtm.io,101649,reseller,3fd707be9c4527c3
             → ad_system: districtm.io
line 408    spotxchange.com,283422,reseller,7842df1d2fe2db34
             → ad_system: spotxchange.com
line 440    reforge.in,353,reseller
             → ad_system: reforge.in
line 508    spotxchange.com,82068,reseller,7842df1d2fe2db34
             → ad_system: spotxchange.com
line 540    engagebdr.com, 10417, RESELLER # EngageDBR
             → ad_system: engagebdr.com
line 563    reforge.in,83, DIRECT
             → ad_system: reforge.in
line 564    reforge.in,409, DIRECT
             → ad_system: reforge.in
line 569    engagebdr.com, 10181, RESELLER
             → ad_system: engagebdr.com
line 587    spotxchange.com,108706, RESELLER, 7842df1d2fe2db34 #EBDA
             → ad_system: spotxchange.com
line 591    engagebdr.com, 10352, DIRECT
             → ad_system: engagebdr.com
line 736    spotxchange.com,283422,RESELLER,7842df1d2fe2db34
             → ad_system: spotxchange.com
line 737    spotxchange.com,82068,RESELLER,7842df1d2fe2db34
             → ad_system: spotxchange.com
warning

Malformed lines

6 −1 pts

Lines that buyers' crawlers will ignore.

How to fixFix the format: <ad system domain>, <seller id>, DIRECT|RESELLER[, <cert authority id>].
Evidence (6) 
line 554    yahoo.com, 58905, RESELLER e1a5b5b6e3255540
             → reason: relationship must be DIRECT or RESELLER, got 'RESELLER e1a5b5b6e3255540'
line 1553   engagemedia.tv, 1063 RESELLER, cb58d2185b16309a
             → reason: relationship must be DIRECT or RESELLER, got 'cb58d2185b16309a'
line 2250   trustedstack, TSTKQ5827, RESELLLER
             → reason: invalid ad system domain
line 2255   trustedstack, TSTKQ5827, RESELLER
             → reason: invalid ad system domain
line 2379   eyeconicspot.com, 4843,  RESELLER 2cec374be7db7217
             → reason: relationship must be DIRECT or RESELLER, got 'RESELLER 2cec374be7db7217'
line 2386   smaato.com, 1100004890,  RESELLER  07bcf65f187117b4
             → reason: relationship must be DIRECT or RESELLER, got 'RESELLER  07bcf65f187117b4'
info

Duplicate lines

424 −3 pts

Harmless but a sign of copy-paste maintenance.

How to fixRemove duplicates; keep one copy of each line.
Evidence (25 of 424) 
ad_system: adagio.io  seller_id: 1522  relationship: RESELLER
ad_system: adcolony.com  seller_id: 1efc6603710003ea  relationship: RESELLER
ad_system: adcolony.com  seller_id: 29b7f4a14dc689eb  relationship: RESELLER
ad_system: admixer.net  seller_id: 2878f07c-cc3f-4f8a-a26c-8e6033a539a6  relationship: RESELLER
ad_system: adyoulike.com  seller_id: f78b24039641337f06634ab9a3da4b48  relationship: RESELLER
ad_system: appnexus.com  seller_id: 13817  relationship: RESELLER
ad_system: appnexus.com  seller_id: 8178  relationship: RESELLER
ad_system: axonix.com  seller_id: 56222  relationship: RESELLER
ad_system: betweendigital.com  seller_id: 43092  relationship: RESELLER
ad_system: contextweb.com  seller_id: 562499  relationship: RESELLER
ad_system: contextweb.com  seller_id: 562827  relationship: RESELLER
ad_system: contextweb.com  seller_id: 563521  relationship: RESELLER
ad_system: conversantmedia.com  seller_id: 100246  relationship: RESELLER
ad_system: conversantmedia.com  seller_id: 100886  relationship: RESELLER
ad_system: e-planning.net  seller_id: 949b688810cb7439  relationship: RESELLER
ad_system: e-planning.net  seller_id: b9165ad221c51225  relationship: RESELLER
ad_system: emxdgt.com  seller_id: 2047  relationship: RESELLER
ad_system: eskimi.com  seller_id: eas-2020000005  relationship: RESELLER
ad_system: google.com  seller_id: pub-2843405949989126  relationship: RESELLER
ad_system: improvedigital.com  seller_id: 1532  relationship: RESELLER
ad_system: improvedigital.com  seller_id: 2525  relationship: RESELLER
ad_system: indexexchange.com  seller_id: 191332  relationship: RESELLER
ad_system: indexexchange.com  seller_id: 192806  relationship: RESELLER
ad_system: inmobi.com  seller_id: 22e5354e453f49348325184e25464adb  relationship: RESELLER
ad_system: inmobi.com  seller_id: 791b84bdd791470faa8dca5f04e6a83b  relationship: RESELLER
info

DIRECT accounts registered to another domain

10 −2 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 (10) 
line 8      google.com, pub-4033211073363733, DIRECT, f08c47fec0942fa0
             → domain in sellers.json: inshot.com  name in sellers.json: SHANTANU PTE.LIMITED
line 154    ushareit.com, 14037806, DIRECT
             → domain in sellers.json: inshot.dev  name in sellers.json: InShot Inc.
line 175    unity3d.com, 1530740, DIRECT, 96cabb5fbdde37a7
             → domain in sellers.json: inshotapp.com  name in sellers.json: JohnsonPUnity
line 177    unity.com, 1530740, DIRECT, 96cabb5fbdde37a7
             → domain in sellers.json: inshotapp.com  name in sellers.json: JohnsonPUnity
line 526    applovin.com, b6fc3902573780e1e3e011c30f60ff21, DIRECT
             → domain in sellers.json: inshotapp.com  name in sellers.json: SHANTANU PTE. LIMITED
line 1926   tradplusad.com,88dcddeb1cc5645d,DIRECT
             → domain in sellers.json: inshot.com  name in sellers.json: SHELMO PTE. LTD.
line 2031   pangleglobal.com, 5021344, DIRECT
             → domain in sellers.json: inshot.app  name in sellers.json: Linkdesks Pte. Ltd.
line 2032   pubmatic.com, 166038, DIRECT, 5d62403b186f2ace
             → domain in sellers.json: shelmo.app  name in sellers.json: SHELMO PTE LTD
line 2067   pangleglobal.com, 5021396, DIRECT
             → domain in sellers.json: inshot.com  name in sellers.json: SHELMO PTE. LTD.
line 2442   fyber.com,236745,DIRECT,1ad675c9de6b5176
             → domain in sellers.json: inshot.com  name in sellers.json: HARDSTONE PTE. LTD.
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

480

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 480) 
line 16     adcolony.com, 1efc6603710003ea, RESELLER
             → sellers_json: HTML or login page instead of JSON
line 17     adcolony.com, 29b7f4a14dc689eb, RESELLER
             → sellers_json: HTML or login page instead of JSON
line 22     adriver.ru, 1009202, DIRECT
             → sellers_json: HTTP 404
line 23     ads.sber.ru, 14037806, DIRECT
             → sellers_json: HTML or login page instead of JSON
line 30     appnexus.com, 1356, RESELLER
             → sellers_json: HTTP 403
line 31     appnexus.com, 13817, RESELLER
             → sellers_json: HTTP 403
line 32     appnexus.com, 8178, RESELLER
             → sellers_json: HTTP 403
line 42     betweendigital.ru, 14037806, DIRECT
             → sellers_json: HTTP 404
line 50     byyd.me, 14037806, DIRECT
             → sellers_json: HTTP 404
line 62     eskimi.com, eas-2020000005, RESELLER
             → sellers_json: HTTP 403
line 65     hybrid.ai, 14037806, DIRECT
             → sellers_json: HTTP 404
line 66     hyperad.tech, 41, RESELLER
             → sellers_json: HTML or login page instead of JSON
line 82     loopme.com, 11278, RESELLER
             → sellers_json: HTTP 403
line 83     loopme.com, 11322, RESELLER
             → sellers_json: HTTP 403
line 84     loopme.com, 11352, RESELLER
             → sellers_json: HTTP 403
line 85     loopme.com, 11424, RESELLER
             → sellers_json: HTTP 403
line 91     mediasniper.ru, 14037806, DIRECT
             → sellers_json: HTTP 404
line 92     mediasniper.ru, 273000370, DIRECT
             → sellers_json: HTTP 404
line 95     mts.ru, 14037806, DIRECT
             → sellers_json: HTTP 404
line 100    openx.com, 537152826, RESELLER
             → sellers_json: HTTP 403
line 101    openx.com, 540298543, RESELLER
             → sellers_json: HTTP 403
line 102    openx.com, 540543195, RESELLER
             → sellers_json: HTTP 403
line 103    openx.com, 540838151, RESELLER
             → sellers_json: HTTP 403
line 104    openx.com, 541031350, RESELLER
             → sellers_json: HTTP 403
line 105    openx.com, 541177349, RESELLER
             → sellers_json: HTTP 403
info

DIRECT accounts marked confidential

9

Buyers can't see who owns these accounts.

How to fixAsk the ad system to publish your seller entry with name and domain.
Evidence (9) 
line 2      google.com, pub-8272683055562823, DIRECT, f08c47fec0942fa0
line 3      google.com, pub-1035430350173898, DIRECT, f08c47fec0942fa0
line 6      google.com, pub-5434446882525782, DIRECT, f08c47fec0942fa0
line 7      google.com, pub-6738973514076600, DIRECT, f08c47fec0942fa0
line 9      google.com, pub-6498566310439822, DIRECT, f08c47fec0942fa0
line 11     google.com, pub-7771773420593429, DIRECT, f08c47fec0942fa0
line 24     ads.vk.com, 14037806, DIRECT
line 149    target.vk.ru, 14037806, DIRECT
line 840    target.my.com, 2791629, DIRECT

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