Android · Hudl, Inc.

Hudl Fan: Find, Watch, Follow.

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

78/100

210 lines · 134 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

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

line 4      google.com, pub-9761842059523356, DIRECT, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 9      google.com, pub-8601191365596436, DIRECT, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 39     improvedigital.com,2050,RESELLER
             → sellers_json: https://improvedigital.com/sellers.json
line 43     risecodes.com,63832beef8189a00015cb6d3,RESELLER
             → sellers_json: https://risecodes.com/sellers.json
line 53     onetag.com, 8adf727f4c4e2ba, DIRECT
             → sellers_json: https://onetag.com/sellers.json
line 61     lijit.com, 515768, DIRECT, fafdf38b16bf6b2b #SOVRN
             → sellers_json: https://lijit.com/sellers.json
line 62     lijit.com, 515768-eb, DIRECT, fafdf38b16bf6b2b #SOVRN
             → sellers_json: https://lijit.com/sellers.json
line 74     connectad.io,455,RESELLER,85ac85a30c93b3e5
             → sellers_json: https://connectad.io/sellers.json
line 105    sonobi.com, 1030aa5329, RESELLER, d1a215d9eb5aee9e
             → sellers_json: https://sonobi.com/sellers.json
line 121    e-planning.net, d97a02af829f879b, RESELLER, c1ba615865ed87b2
             → sellers_json: https://e-planning.net/sellers.json
line 127    video.unrulymedia.com, 3227031674, RESELLER
             → sellers_json: https://video.unrulymedia.com/sellers.json
line 148    onetag.com, 74fb6052d135e76, RESELLER
             → sellers_json: https://onetag.com/sellers.json
line 149    xandr.com, 17167, DIRECT
             → sellers_json: https://xandr.com/sellers.json
line 176    lemmatechnologies.com,97,RESELLER,7829010c5bebd1fb
             → sellers_json: https://lemmatechnologies.com/sellers.json
line 193    onetag.com, 6049d2c92852238, RESELLER
             → sellers_json: https://onetag.com/sellers.json
line 221    thebrave.io, 1234647, RESELLER, c25b2154543746ac
             → sellers_json: https://thebrave.io/sellers.json

warning

DIRECT lines inconsistent with public data

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

line 52     rubiconproject.com, 22884, DIRECT, 0bfd66d529a55807
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 43 different companies  name in sellers.json: Google  domain in sellers.json: google.com
line 54     onetag.com, 8adf727f4c4e2ba-OB, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Hudl-OB  domain in sellers.json: google.com
line 72     Media.net, 8CUQE561G, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Hudl (via OB)  domain in sellers.json: google.com
line 73     pubmatic.com, 165514, DIRECT, 5d62403b186f2ace
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Hudl (via EB)  domain in sellers.json: google.com
line 186    themediagrid.com, FWN84J, DIRECT, 35d5010d7789b49d
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 74 different companies  name in sellers.json: Start.io Inc  domain in sellers.json: start.io

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 78     conversantmedia.com, 100905, DIRECT/RESELLER, 03113cd04947736d
             → reason: relationship must be DIRECT or RESELLER, got 'DIRECT/RESELLER'

warning

Lines for ad system domains that don't resolve

1 −1 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 24     districtm.io,100962,RESELLER,3fd707be9c4527c3
             → ad_system: districtm.io

info

Duplicate lines

7 −1 pts

Harmless but a sign of copy-paste maintenance.

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

Evidence (7)

ad_system: openx.com  seller_id: 538959099  relationship: RESELLER
ad_system: pubmatic.com  seller_id: 137711  relationship: RESELLER
ad_system: pubmatic.com  seller_id: 156212  relationship: RESELLER
ad_system: rubiconproject.com  seller_id: 17960  relationship: RESELLER
ad_system: appnexus.com  seller_id: 1019  relationship: RESELLER
ad_system: inmobi.com  seller_id: b01aa06531c543d8a5fb9982f60afb00  relationship: RESELLER
ad_system: loopme.com  seller_id: 11318  relationship: RESELLER

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 5      google.com, pub-8064575791506511, DIRECT, f08c47fec0942fa0
             → domain in sellers.json: blueframetech.com  name in sellers.json: Agile Sports Technologies, Inc. dba Hudl

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 51)

line 15     openx.com,540191398,RESELLER,6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 17     appnexus.com,1908,RESELLER,f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 19     sovrn.com,375328,RESELLER,fafdf38b16bf6b2b
             → sellers_json: HTTP 403 to automated requests
line 21     smaato.com,1100044650,RESELLER,07bcf65f187117b4
             → sellers_json: HTTP 403 to automated requests
line 26     appnexus.com,3663,RESELLER,f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 27     rhythmone.com,1654642120,RESELLER,a670c89d4a324e47
             → sellers_json: HTTP 403 to automated requests
line 28     smartadserver.com,4125,RESELLER,060d053dcf45cbf3
             → sellers_json: HTTP 404
line 36     appnexus.com,1356,RESELLER,f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 55     appnexus.com, 13099, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 58     freewheel.tv, 20393, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 59     freewheel.tv, 24377, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 60     openx.com, 560860438, DIRECT, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 63     openx.com, 538959099, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 67     appnexus.com, 1019, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 81     appnexus.com,17167,DIRECT,f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 87     openx.com, 540680795, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 88     openx.com, 537127194, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 93     appnexus.com, 4052, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 95     openx.com, 540031703, RESELLER, 6a698e2ec38604c6
             → sellers_json: HTTP 403 to automated requests
line 98     yahoo.com, 55771, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 429 to automated requests
line 104    adcolony.com, 8d559ca59197a1a0, RESELLER, 1ad675c9de6b5176
             → sellers_json: returns a web page, not a sellers.json file
line 107    yahoo.com, 59875, RESELLER
             → sellers_json: HTTP 429 to automated requests
line 110    yahoo.com, 57289, RESELLER, e1a5b5b6e3255540
             → sellers_json: HTTP 429 to automated requests
line 111    appnexus.com, 10239, RESELLER, f5ab79cb980f11d1
             → sellers_json: HTTP 403 to automated requests
line 113    openx.com, 537120563, RESELLER, 6a698e2ec38604c6
             → 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