iOS · Plato Team Inc.

Plato: Fun Multiplayer Games

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

61/100

121 lines · 55 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

19 −20 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 (19)

line 2      google.com, pub-3252438284341857, DIRECT, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 12     pubmatic.com, 156556, RESELLER, 5d62403b186f2ace
             → sellers_json: https://pubmatic.com/sellers.json
line 13     pubmatic.com, 156140, RESELLER, 5d62403b186f2ace
             → sellers_json: https://pubmatic.com/sellers.json
line 14     pubmatic.com, 156139, RESELLER, 5d62403b186f2ace
             → sellers_json: https://pubmatic.com/sellers.json
line 16     pubmatic.com, 158430, RESELLER, 5d62403b186f2ace
             → sellers_json: https://pubmatic.com/sellers.json
line 21     rubiconproject.com, 21648, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 28     axonix.com, 56411, RESELLER
             → sellers_json: https://axonix.com/sellers.json
line 38     rubiconproject.com, 20942, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 41     smartclip.net, 6740, RESELLER
             → sellers_json: https://smartclip.net/sellers.json
line 42     smartstream.tv,3199,RESELLER
             → sellers_json: https://smartstream.tv/sellers.json
line 43     smartstream.tv,5641,RESELLER
             → sellers_json: https://smartstream.tv/sellers.json
line 46     telaria.com, 7wy0w, RESELLER, 1a4e959a1b50034a
             → sellers_json: https://www.telaria.com/sellers.json
line 47     tremorhub.com, 7wy0w, RESELLER, 1a4e959a1b50034a
             → sellers_json: https://tremorhub.com/sellers.json
line 55     admixer.net, 3d2ed9f3-1ce6-436c-896b-4d9c8418ad3f, RESELLER
             → sellers_json: https://admixer.net/sellers.json
line 59     algorix.co, 54250, RESELLER
             → sellers_json: https://algorix.co/sellers.json
line 83     improvedigital.com, 1366, RESELLER
             → sellers_json: https://improvedigital.com/sellers.json
line 93     onetag.com, 59aa7be4921bac8, RESELLER
             → sellers_json: https://onetag.com/sellers.json
line 107    pubnative.net, 1006458, RESELLER, d641df8625486a7b
             → sellers_json: https://pubnative.net/sellers.json
line 126    undertone.com, 3635, RESELLER
             → sellers_json: https://undertone.com/sellers.json

warning

DIRECT lines inconsistent with public data

2 −9 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 (2)

line 6      advertising.com, 26367, DIRECT, e1a5b5b6e3255540
             → observed: the same account is marked DIRECT by 8 different companies
line 53     admanmedia.com, 594, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 6 different companies  name in sellers.json: loopme  domain in sellers.json: loopme.com

warning

Lines for ad system domains that don't resolve

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

line 45     spotxchange.com, 139784, RESELLER, 7842df1d2fe2db34
             → ad_system: spotxchange.com
line 77     engagebdr.com, 10181, RESELLER
             → ad_system: engagebdr.com
line 78     engagebdr.com, 10252, RESELLER
             → ad_system: engagebdr.com
line 79     engagebdr.com, 10252, RESELLER #fill #video
             → ad_system: engagebdr.com
line 80     engagebdr.com, 16, RESELLER
             → ad_system: engagebdr.com
line 81     engagebdr.com, 7, RESELLER
             → ad_system: engagebdr.com
line 82     engagebdr.com, 84, RESELLER
             → ad_system: engagebdr.com
line 119    spotxchange.com, 99441, 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

Duplicate lines

7 −1 pts

Harmless but a sign of copy-paste maintenance.

How to fixRemove duplicates; keep one copy of each line.

Evidence (7)

ad_system: contextweb.com  seller_id: 561849  relationship: RESELLER
ad_system: engagebdr.com  seller_id: 10252  relationship: RESELLER
ad_system: inmobi.com  seller_id: c1e6d3502da64ebaa3ad0e4a4be15f11  relationship: RESELLER
ad_system: openx.com  seller_id: 540543195  relationship: RESELLER
ad_system: pubmatic.com  seller_id: 156517  relationship: RESELLER
ad_system: rubiconproject.com  seller_id: 15278  relationship: RESELLER
ad_system: sabio.us  seller_id: 100032  relationship: RESELLER

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

line 4      facebook.com, 206969163309685, RESELLER, c3e20eee3f780d68
             → sellers_json: HTML or login page instead of JSON
line 6      advertising.com, 26367, DIRECT, e1a5b5b6e3255540
             → sellers_json: HTTP 403
line 7      aol.com, 55101, DIRECT, e1a5b5b6e3255540
             → sellers_json: HTTP 404
line 8      appnexus.com, 1868, RESELLER
             → sellers_json: HTTP 403
line 11     openx.com, 539959224, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 18     xad.com, 240, RESELLER, 81cbf0a75a5e0e9a
             → sellers_json: HTTP 403
line 20     mopub.com, d0b18c955a6b4cdd82aa48f34fafb251, DIRECT, 74b46c0ea83967ca
             → sellers_json: HTML or login page instead of JSON
line 24     advertising.com, 8693, RESELLER
             → sellers_json: HTTP 403
line 25     aol.com, 25910, RESELLER
             → sellers_json: HTTP 404
line 26     appnexus.com, 2234, RESELLER
             → sellers_json: HTTP 403
line 27     appnexus.com, 2480, RESELLER
             → sellers_json: HTTP 403
line 31     loopme.com, 10287, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 32     loopme.com, s-2411, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 33     openx.com, 537153564, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 34     openx.com, 539363588, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 36     rhythmone.com, 3169196794, RESELLER, a670c89d4a324e47
             → sellers_json: HTTP 403
line 49     vungle.com, 5c81b254d984ad32b9c824ed, DIRECT, c107d686becd2d77
             → sellers_json: HTTP 403
line 50     adcolony.com, 1efc6603710003ea, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTML or login page instead of JSON
line 51     adcolony.com, 801e49d1be83b5f9, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTML or login page instead of JSON
line 52     adcolony.com, 81685aa581edd381, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTML or login page instead of JSON
line 57     advertising.com, 25990, RESELLER
             → sellers_json: HTTP 403
line 58     advertising.com, 28246, RESELLER
             → sellers_json: HTTP 403
line 60     appnexus.com, 10128, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 61     appnexus.com, 11452, DIRECT
             → sellers_json: HTTP 403
line 62     appnexus.com, 11452, RESELLER
             → 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