iOS · TapMedia Ltd

QR Reader for iPhone

Developer URL: http://www.tapmedia.co.uk
app-ads.txt: https://tapmedia.co.uk/app-ads.txt · 200
Checked: Oct 7, 2026

68/100

128 lines · 75 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

16 −17 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 (16)

line 2      smaato.com, 1100009186, DIRECT, 07bcf65f187117b4
             → sellers_json: https://smaato.com/sellers.json
line 24     pubmatic.com, 156389, RESELLER, 5d62403b186f2ace
             → sellers_json: https://pubmatic.com/sellers.json
line 25     pubmatic.com, 156424, RESELLER, 5d62403b186f2ace
             → sellers_json: https://pubmatic.com/sellers.json
line 61     aps.amazon.com,da926c23-05be-477f-a006-f425dfe4f99a,DIRECT
             → sellers_json: https://aps.amazon.com/sellers.json
line 62     aps.amazon.com,447231,DIRECT
             → sellers_json: https://aps.amazon.com/sellers.json
line 63     aps.amazon.com,447231,RESELLER
             → sellers_json: https://aps.amazon.com/sellers.json
line 71     unity.com, 3074687, DIRECT, 96cabb5fbdde37a7
             → sellers_json: https://unity.com/sellers.json
line 72     unity3d.com, 3074687, DIRECT, 96cabb5fbdde37a7
             → sellers_json: https://unity3d.com/sellers.json
line 87     rubiconproject.com, 21526, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 98     kidoz.net, 19692013, RESELLER
             → sellers_json: https://kidoz.net/sellers.json
line 105    video.unrulymedia.com, 3630748062, RESELLER, a670c89d4a324e47
             → sellers_json: https://video.unrulymedia.com/sellers.json
line 106    telaria.com, rwd19-3074687, RESELLER, 1a4e959a1b50034a
             → sellers_json: https://www.telaria.com/sellers.json
line 107    tremorhub.com, rwd19-3074687, RESELLER, 1a4e959a1b50034a
             → sellers_json: https://tremorhub.com/sellers.json
line 121    improvedigital.com,2050,RESELLER
             → sellers_json: https://improvedigital.com/sellers.json
line 123    sonobi.com,24f603762e,RESELLER,d1a215d9eb5aee9e
             → sellers_json: https://sonobi.com/sellers.json
line 125    themediagrid.com, RIX2M5, DIRECT, 35d5010d7789b49d
             → sellers_json: https://themediagrid.com/sellers.json

warning

DIRECT lines inconsistent with public data

3 −10 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 3      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 108    rubiconproject.com, 22884, DIRECT, 0bfd66d529a55807
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 42 different companies  name in sellers.json: Google  domain in sellers.json: google.com
line 125    themediagrid.com, RIX2M5, DIRECT, 35d5010d7789b49d
             → observed: the same account is marked DIRECT by 31 different companies

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 15     engagebdr.com, 16, RESELLER
             → ad_system: engagebdr.com
line 50     spotxchange.com, 234183, RESELLER, 7842df1d2fe2db34
             → ad_system: spotxchange.com
line 82     spotxchange.com, 117872, RESELLER, 7842df1d2fe2db34
             → ad_system: spotxchange.com
line 89     reforge.in, 107, RESELLER
             → ad_system: reforge.in

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

line 4      adcolony.com, 496220845654deec, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTML or login page instead of JSON
line 6      appnexus.com, 1752, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 7      appnexus.com, 4052, RESELLER
             → sellers_json: HTTP 403
line 8      appnexus.com, 8790, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 16     gammassp.com, 1516331892, RESELLER, 31ac53fec2772a83
             → sellers_json: HTML or login page instead of JSON
line 21     openx.com, 540421297, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 29     rhythmone.com, 4201299756, RESELLER, a670c89d4a324e47
             → sellers_json: HTTP 403
line 31     startapp.com, smt, RESELLER
             → sellers_json: HTTP 404
line 32     xad.com, 241, RESELLER, 81cbf0a75a5e0e9a
             → sellers_json: HTTP 403
line 37     openx.com, 537124160, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 38     openx.com, 539214772, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 39     facebook.com, 177329882758774, RESELLER, c3e20eee3f780d68
             → sellers_json: HTML or login page instead of JSON
line 40     facebook.com, 313251062406336, RESELLER, c3e20eee3f780d68
             → sellers_json: HTML or login page instead of JSON
line 45     xad.com, 767, RESELLER, 81cbf0a75a5e0e9a
             → sellers_json: HTTP 403
line 46     xad.com, 1190, RESELLER, 81cbf0a75a5e0e9a
             → sellers_json: HTTP 403
line 52     openx.com, 540543200, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 54     appnexus.com, 1356, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 58     loopme.com, 9724, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 60     openx.com, 540298543, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 67     adcolony.com,44ef7fd4adebf701,RESELLER,1ad675c9de6b5176
             → sellers_json: HTML or login page instead of JSON
line 70     loopme.com,11405,RESELLER
             → sellers_json: HTTP 403
line 73     loopme.com, 9621, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 74     adcolony.com, 0a0f72cd66122f31, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTML or login page instead of JSON
line 75     adcolony.com, 801e49d1be83b5f9, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTML or login page instead of JSON
line 84     openx.com, 540871654, RESELLER, 6a698e2ec38604c6
             → 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