iOS · Free VPN LLC

Free VPN by Free VPN .org™

Developer URL: https://freevpnapp.org/
app-ads.txt: https://freevpnapp.org/app-ads.txt · 200
Checked: Oct 7, 2026

65/100

116 lines · 58 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 4      applovin.com, 5a7f80d6d508c0ebe7007ddb1c4cd8b1, RESELLER
             → sellers_json: https://applovin.com/sellers.json
line 7      Axonix.com, 56266, RESELLER
             → sellers_json: https://axonix.com/sellers.json
line 9      mintegral.com, 12101, RESELLER
             → sellers_json: https://mintegral.com/sellers.json
line 12     smartadserver.com, 1289, RESELLER
             → sellers_json: https://smartadserver.com/sellers.json
line 13     smartadserver.com, 3042, RESELLER
             → sellers_json: https://smartadserver.com/sellers.json
line 16     telaria.com, rwd19-1019584, RESELLER, 1a4e959a1b50034a
             → sellers_json: https://www.telaria.com/sellers.json
line 17     tremorhub.com, rwd19-1019584, RESELLER, 1a4e959a1b50034a
             → sellers_json: https://tremorhub.com/sellers.json
line 21     google.com, pub-6845454968529492, RESELLER
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 22     google.com, pub-5253946476177754, RESELLER
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 39     pubmatic.com, 156030, RESELLER, 5d62403b186f2ace
             → sellers_json: https://pubmatic.com/sellers.json
line 56     adingo.jp, 25274, DIRECT
             → sellers_json: https://adingo.jp/sellers.json
line 71     video.unrulymedia.com, 905992537, RESELLER, a670c89d4a324e47 # RhythmOne
             → sellers_json: https://video.unrulymedia.com/sellers.json
line 74     onetag.com, 72b20ec05ea6e86, DIRECT
             → sellers_json: https://onetag.com/sellers.json
line 77     google.com, pub-3769010358500643, RESELLER, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 92     rubiconproject.com,21526, RESELLER,0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 93     rubiconproject.com,21938, RESELLER,0bfd66d529a55807
             → sellers_json: https://rubiconproject.com/sellers.json
line 108    rubiconproject.com, 17346, RESELLER, 0bfd66d529a55807 #EBDA
             → sellers_json: https://rubiconproject.com/sellers.json
line 115    video.unrulymedia.com, 1149317856, RESELLER #EBDA
             → sellers_json: https://video.unrulymedia.com/sellers.json
line 117    media.net, 8CUDR582K, DIRECT
             → sellers_json: https://media.net/sellers.json

warning

DIRECT lines inconsistent with public data

2 −6 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 74     onetag.com, 72b20ec05ea6e86, DIRECT
             → observed: the same account is marked DIRECT by 24 different companies
line 116    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

warning

Lines for ad system domains that don't resolve

6 −5 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 (6)

line 45     districtm.io, 101760, RESELLER, 3fd707be9c4527c3
             → ad_system: districtm.io
line 66     engagebdr.com, 10417, RESELLER # EngageDBR
             → ad_system: engagebdr.com
line 89     reforge.in,83, DIRECT
             → ad_system: reforge.in
line 90     reforge.in,409, DIRECT
             → ad_system: reforge.in
line 96     engagebdr.com, 10181, RESELLER
             → ad_system: engagebdr.com
line 113    spotxchange.com,108706, RESELLER, 7842df1d2fe2db34 #EBDA
             → ad_system: spotxchange.com

warning

Malformed lines

1 −1 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 80     yahoo.com, 58905, RESELLER e1a5b5b6e3255540
             → reason: relationship must be DIRECT or RESELLER, got 'RESELLER e1a5b5b6e3255540'

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

DIRECT accounts registered to another domain

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

line 61     chocolateplatform.com, 16065, DIRECT, 49a66ce31a704197
             → domain in sellers.json: actmobile.com  name in sellers.json: ActMobile Networks Inc

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 1      mopub.com, c7cd5e95ca7c4347b8ea77d519bbd4b5, DIRECT, 74b46c0ea83967ca
             → sellers_json: HTML or login page instead of JSON
line 3      adcolony.com, e0355e23aa56b4c34dacf5ece1c237bc, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTML or login page instead of JSON
line 5      adcolony.com, 5d8cbf6671c93a42, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTML or login page instead of JSON
line 10     mobfox.com, 44666, RESELLER
             → sellers_json: HTTP 403
line 14     tapjoy.com, a92a273e84854428a4d61a1867f58639, RESELLER, 29e595b1aeb5904d
             → sellers_json: HTML or login page instead of JSON
line 18     loopme.com, 9621, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 19     adcolony.com, 0a0f72cd66122f31, RESELLER, 1ad675c9de6b5176
             → sellers_json: HTML or login page instead of JSON
line 24     appnexus.com, 10005, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 27     openx.com, 540338069, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 28     rhythmone.com, 1605779867, RESELLER, a670c89d4a324e47
             → sellers_json: HTTP 403
line 30     Vungle.com, 56f167bda94d7ae44a000103, RESELLER, c107d686becd2d77
             → sellers_json: HTTP 403
line 31     Openx.com, 540280728, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 32     Appnexus.com, 10128, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 35     Loopme.com, 10999, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 42     openx.com, 537149888, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 43     appnexus.com, 3703, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 44     groundtruth.com, 107, RESELLER, 81cbf0a75a5e0e9a
             → sellers_json: HTTP 403
line 46     loopme.com, s-2411, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 47     loopme.com, 5679, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 48     Ogury.com, c137917a7ac4c5dbd307dc260449f10d, DIRECT
             → sellers_json: HTTP 403
line 49     Ogury.com, ceac16d141fbd177430bd02a3f4f922b, DIRECT
             → sellers_json: HTTP 403
line 50     Ogury.com, 80a74be587cce0145afb4640f895a0e6, DIRECT
             → sellers_json: HTTP 403
line 51     Ogury.com, e25359a5fd6b99cdbca1c588569ade36, DIRECT
             → sellers_json: HTTP 403
line 52     Ogury.com, 955a459078b65ef5edd97da016a73791, DIRECT
             → sellers_json: HTTP 403
line 53     Ogury.com, 90a105bd23ea175ac7d75877f0cc87fb, DIRECT
             → 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