iOS · UREELS PTE. LTD.

JoyReels - Enjoy Short Dramas

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

60/100

44 lines · 31 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 −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 (11)

line 12     pubmatic.com, 159668, RESELLER, 5d62403b186f2ace
             → sellers_json: https://pubmatic.com/sellers.json
line 14     onetag.com, 72b20ec05ea6e86, DIRECT
             → sellers_json: https://onetag.com/sellers.json
line 17     google.com, pub-3769010358500643, RESELLER, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 25     rubiconproject.com, 24484, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 28     rubiconproject.com, 23986, RESELLER, 0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 35     eskimi.com,2020000032, RESELLER
             → sellers_json: https://eskimi.com/sellers.json
line 38     dragon-advertising.com, 44f683a84163b3523afe57c2e008bc8c8283, RESELLER
             → sellers_json: https://dragon-advertising.com/sellers.json
line 39     e-planning.net, 384cc67d47354bbd, RESELLER, c1ba615865ed87b2
             → sellers_json: https://e-planning.net/sellers.json
line 44     sonobi.com, 94997de4e6, RESELLER, d1a215d9eb5aee9e
             → sellers_json: https://sonobi.com/sellers.json
line 45     e-planning.net, ef8dc1dee54baf18, RESELLER, c1ba615865ed87b2
             → sellers_json: https://e-planning.net/sellers.json
line 46     opera.com, pub5479493704320, RESELLER, 55a0c5fd61378de3
             → sellers_json: https://opera.com/sellers.json

warning

DIRECT lines inconsistent with public data

1 −13 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 (1)

line 14     onetag.com, 72b20ec05ea6e86, DIRECT
             → observed: the same account is marked DIRECT by 25 different companies

warning

Malformed lines

1 −2 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 37     bidvol.com, RESELLER, 93287
             → reason: relationship must be DIRECT or RESELLER, got '93287'

warning

Lines for ad system domains that don't resolve

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

line 43     gamoshi.io, 267-b5310, RESELLER, 20e30b2ae1f670f2
             → ad_system: gamoshi.io

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: google.com  seller_id: pub-4445253617644321  relationship: DIRECT

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 (10)

line 7      smartadserver.com, 4395, RESELLER, 060d053dcf45cbf3
             → sellers_json: HTTP 404
line 10     smartadserver.com, 4467, RESELLER
             → sellers_json: HTTP 404
line 15     advertising.com, 28246, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 18     freewheel.tv, 20393, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 19     freewheel.tv, 24377, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 20     yahoo.com, 58905, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 429 to automated requests
line 21     aol.com, 58905, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 404
line 30     appnexus.com, 13794, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 36     adzvigo.com, b83aac23b9528732c23cc7352950e88031818, RESELLER
             → sellers_json: bot-check page instead of the file
line 41     appnexus.com, 8233, RESELLER
             → 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