iOS · FitNow, Inc.

Lose It! – Calorie Counter

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

90/100

116 lines · 90 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

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

line 19     pubmatic.com, 157709, DIRECT, 5d62403b186f2ace
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Ziff Davis (Everyday Health) (via EB)  domain in sellers.json: google.com
line 22     rubiconproject.com, 17750, DIRECT, 0bfd66d529a55807 #display
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Google  domain in sellers.json: google.com
line 26     triplelift.com, 12381-EB,DIRECT,6c33edb13117fd86
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: everydayhealth (via EB Network)  domain in sellers.json: google.com
line 120    themediagrid.com, A7OJMU, DIRECT, 9fac4a4a87c2a44f
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 36 different companies  name in sellers.json: Nimbus Advertising Solutions  domain in sellers.json: adsbynimbus.com

warning

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

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

line 65     adview.com,32076181,RESELLER,1b2cc038a11ea319
             → sellers_json: https://adview.com/sellers.json
line 68     growintech.co,2723d092b63885e0d7c260cc007e8b9d2393g,RESELLER,9d8dfe5c6b00fb37
             → sellers_json: https://growintech.co/sellers.json
line 73     xandr.com,10128,RESELLER,f5ab79cb980f11d1
             → sellers_json: https://xandr.com/sellers.json
line 78     e-planning.net,081dcb996d2ccc1e,RESELLER,c1ba615865ed87b2
             → sellers_json: https://e-planning.net/sellers.json

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 101    adsbynimbus.com, 637b4903-b2ca-4e40-bacb-c8e5e5de4909, DIRECT, dd263a8a859bd0e0
             → domain in sellers.json: babycenter.com  name in sellers.json: BabyCenter

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

line 6      appnexus.com,7886,DIRECT,f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 15     openx.com,539581926,DIRECT,6a698e2ec38604c6
             → sellers_json: HTTP 403
line 16     openx.com, 537150862, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 17     openx.com, 559910619, DIRECT, 6a698e2ec38604c6 #nimbus
             → sellers_json: HTTP 403
line 18     openx.com, 566413278, DIRECT, 6a698e2ec38604c6 #directpay
             → sellers_json: HTTP 403
line 27     ogury.com, 787136cd-456e-420f-8ec5-152ea727acad, DIRECT
             → sellers_json: HTTP 403
line 28     appnexus.com, 11470, RESELLER, f5ab79cb980f11d1 #ogury
             → sellers_json: HTTP 403
line 45     vungle.com,64ecb0b0006b5a0011e57f9a,DIRECT,c107d686becd2d77
             → sellers_json: HTTP 403
line 52     loopme.com,10999,RESELLER,6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 63     openx.com,540280728,RESELLER,6a698e2ec38604c6
             → sellers_json: HTTP 403
line 94     loopme.com, 9724, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 122    appnexus.com,12616,RESELLER,f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 135    openx.com, 540709535, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 137    loopme.com, 11656, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 138    zetaglobal.net, 989, RESELLER
             → sellers_json: HTTP 404

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