iOS · Glority Global Group Ltd.

PictureThis - Plant Identifier

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

50/100

69 lines · 34 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

3 −25 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 1      facebook.com, 343157279440661, DIRECT, c3e20eee3f780d68
             → observed: the same account is marked DIRECT by 6 different companies
line 3      google.com, pub-5782287905414548, DIRECT, f08c47fec0942fa0
             → observed: the same account is marked DIRECT by 5 different companies
line 9      unity.com, 1675209, DIRECT, 96cabb5fbdde37a7
             → observed: the same account is marked DIRECT by 4 different companies  name in sellers.json: Glority Global Group Ltd.

warning

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

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

line 3      google.com, pub-5782287905414548, DIRECT, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 12     yeahmobi.com, 5135195, RESELLER
             → sellers_json: https://yeahmobi.com/sellers.json
line 14     kidoz.net, 19692013, RESELLER
             → sellers_json: https://kidoz.net/sellers.json
line 28     rubiconproject.com, 21526, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 30     rubiconproject.com, 14334, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 38     tremorhub.com, rwd19-1675209, RESELLER, 1a4e959a1b50034a
             → sellers_json: https://tremorhub.com/sellers.json
line 60     bidmachine.io, 114, RESELLER
             → sellers_json: https://bidmachine.io/sellers.json
line 63     video.unrulymedia.com, 3630748062, RESELLER, a670c89d4a324e47
             → sellers_json: https://video.unrulymedia.com/sellers.json

warning

Lines for ad system domains that don't resolve

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

line 18     reforge.in, 107, RESELLER
             → ad_system: reforge.in
line 19     reforge.in, 353, 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

Duplicate lines

1 −1 pts

Harmless but a sign of copy-paste maintenance.

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

Evidence (1)

ad_system: pubnative.net  seller_id: 1006955  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 (22)

line 1      facebook.com, 343157279440661, DIRECT, c3e20eee3f780d68
             → sellers_json: returns a web page, not a sellers.json file
line 2      facebook.com, 451088681917292, RESELLER, c3e20eee3f780d68
             → sellers_json: returns a web page, not a sellers.json file
line 13     criteo.com, B-057955, RESELLER, 9fac4a4a87c2a44f
             → sellers_json: HTTP 403 to automated requests
line 15     pubnative.net, 1006955, RESELLER, d641df8625486a7b
             → sellers_json: HTTP 403 to automated requests
line 16     pubnative.net, 1007040, RESELLER, d641df8625486a7b
             → sellers_json: HTTP 403 to automated requests
line 17     pubnative.net, 1006955, RESELLER, d641df8625486a7b
             → sellers_json: HTTP 403 to automated requests
line 21     telaria.com, rwd19-1675209, RESELLER, 1a4e959a1b50034a
             → sellers_json: HTTP 403 to automated requests
line 22     liftoff.io, 7f6945815e6, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 36     rhythmone.com, 3630748062, RESELLER, a670c89d4a324e47
             → sellers_json: HTTP 403 to automated requests
line 37     spotx.tv, 117872, RESELLER, 7842df1d2fe2db34
             → sellers_json: HTTP 403 to automated requests
line 39     openx.com, 540871654, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 40     openx.com, 540679900, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 41     openx.com, 540838151, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 42     openx.com, 541031350, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 57     adcolony.com, 0a0f72cd66122f31, RESELLER, 1ad675c9de6b5176
             → sellers_json: returns a web page, not a sellers.json file
line 58     adcolony.com, 801e49d1be83b5f9, RESELLER, 1ad675c9de6b5176
             → sellers_json: returns a web page, not a sellers.json file
line 65     appnexus.com, 7353, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 66     appnexus.com, 2764, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 67     appnexus.com, 10617, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 68     appnexus.com, 9393, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 69     loopme.com, 9621, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403 to automated requests
line 70     loopme.com, 11414, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403 to automated requests

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