Android · Rumble Inc

Rumble: Stream & Watch Videos

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

91/100

83 lines · 64 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

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

line 5      media.net, 8CU91I413, DIRECT
             → sellers_json: https://media.net/sellers.json
line 36     thunder-monetize.com, 9630185716, RESELLER
             → sellers_json: https://thunder-monetize.com/sellers.json
line 38     lijit.com, 591223, DIRECT, fafdf38b16bf6b2b #SOVRN
             → sellers_json: https://lijit.com/sellers.json
line 68     netmarvel.com, 1012818, RESELLER, b9b555df26e4707f
             → sellers_json: https://netmarvel.com/sellers.json
line 90     algorix.co, 604689, RESELLER, 5b394c12fea27a1d
             → sellers_json: https://algorix.co/sellers.json

warning

DIRECT lines inconsistent with public data

1 −3 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 20     pubmatic.com, 159436, DIRECT, 5d62403b186f2ace
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Rumble (via EB)  domain in sellers.json: google.com

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

line 10     indicue.com, 2717, DIRECT
             → sellers_json: HTTP 403
line 11     freewheel.tv, sg1217511, RESELLER
             → sellers_json: HTTP 403
line 24     appnexus.com, 17785, DIRECT, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 31     openx.com, 538959099, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 57     adintouch.com, 10017, RESELLER
             → sellers_json: HTTP 404
line 60     appnexus.com, 8035, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403
line 63     eskimi.com, 2020000694, RESELLER
             → sellers_json: HTTP 403
line 66     loopme.com, 11656, RESELLER, 6c8d5f95897a5a3b
             → sellers_json: HTTP 403
line 69     openx.com, 540709535, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403
line 78     zetaglobal.net, 989, RESELLER
             → sellers_json: HTTP 404
line 81     anyclip.com, 001w000001gja9jAAA, DIRECT
             → sellers_json: HTTP 403
line 83     freewheel.tv, 545588-r-524565, RESELLER
             → sellers_json: HTTP 403
line 84     freewheel.tv, 545588-r-523319, RESELLER
             → sellers_json: HTTP 403
line 100    zetaglobal.net, 704, DIRECT
             → 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