iOS · FloSports Inc

FloSports: Watch Live Sports

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

87/100

196 lines · 117 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

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

line 6      google.com, pub-5184334138259799, DIRECT, f08c47fec0942fa0
             → sellers_json: https://realtimebidding.google.com/sellers.json
line 43     triplelift.com, 8255-EB, DIRECT, 6c33edb13117fd86 #Triplelift
             → sellers_json: https://triplelift.com/sellers.json
line 47     triplelift.com, 14171, DIRECT, 6c33edb13117fd86 #SpringSC
             → sellers_json: https://triplelift.com/sellers.json
line 58     video.unrulymedia.com, UNRX-PUB-1d179db7-fc52-464c-8b5e-dcf78319fe84, DIRECT #Unrulydirect
             → sellers_json: https://video.unrulymedia.com/sellers.json
line 59     video.unrulymedia.com, 85858, DIRECT #TAM
             → sellers_json: https://video.unrulymedia.com/sellers.json
line 111    conversantmedia.com, 100658, RESELLER, 03113cd04947736d
             → sellers_json: https://conversantmedia.com/sellers.json
line 112    conversantmedia.com, 100660, RESELLER, 03113cd04947736d
             → sellers_json: https://conversantmedia.com/sellers.json
line 113    conversantmedia.com, 100661, RESELLER, 03113cd04947736d
             → sellers_json: https://conversantmedia.com/sellers.json
line 114    conversantmedia.com, 100662, RESELLER, 03113cd04947736d
             → sellers_json: https://conversantmedia.com/sellers.json
line 170    Media.net, 8CU1798C1, RESELLER
             → sellers_json: https://media.net/sellers.json
line 201    elementaltv.io, 24879480, DIRECT
             → sellers_json: https://elementaltv.io/sellers.json
line 251    videobyte.com, igLAZIh, DIRECT, ed26dcbc74bbdfd0
             → sellers_json: https://videobyte.com/sellers.json
line 281    conversantmedia.com, 100361, RESELLER, 03113cd04947736d
             → sellers_json: https://conversantmedia.com/sellers.json

warning

DIRECT lines inconsistent with public data

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

line 11     smartadserver.com, 4342, DIRECT, 060d053dcf45cbf3
             → observed: the same account is marked DIRECT by 3 different companies
line 13     smartadserver.com, 4071, DIRECT
             → observed: the same account is marked DIRECT by 59 different companies
line 55     video.unrulymedia.com, 1955794380, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: Google EB - FloSports, Inc.  domain in sellers.json: google.com
line 151    media.net, 8CUC4I31X, DIRECT #Media.netEB
             → observed: sellers.json lists the account as INTERMEDIARY  name in sellers.json: FloSports, Inc (via OB)  domain in sellers.json: google.com
line 157    applovin.com, 2713cc543ecb0969b83e3fdbf9ff011f, DIRECT
             → observed: the same account is marked DIRECT by 17 different companies  name in sellers.json: Wurl, Inc  domain in sellers.json: wurl.com
line 245    video.unrulymedia.com, 351983115, DIRECT
             → observed: sellers.json lists the account as INTERMEDIARY; the same account is marked DIRECT by 4 different companies  name in sellers.json: Optima Network  domain in sellers.json: optimanetwork.com
line 306    dauup.com, 44344, DIRECT, 4daba13e2b0dfd92 #Edge226
             → observed: the same account is marked DIRECT by 3 different companies  name in sellers.json: Publica  domain in sellers.json: getpublica.com

info

Duplicate lines

6 −1 pts

Harmless but a sign of copy-paste maintenance.

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

Evidence (6)

ad_system: telaria.com  seller_id: oyz9g-o97cq  relationship: DIRECT
ad_system: tremorhub.com  seller_id: oyz9g-o97cq  relationship: DIRECT
ad_system: pubmatic.com  seller_id: 158111  relationship: RESELLER
ad_system: loopme.com  seller_id: 11227  relationship: RESELLER
ad_system: oxiem.com  seller_id: 80190e083c  relationship: DIRECT
ad_system: oxiem.com  seller_id: af1afa3839  relationship: DIRECT

info

DIRECT accounts registered to another domain

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

line 25     beachfront.com, 14474, DIRECT, e2541279e8e2ca4d #BeachSSHB
             → domain in sellers.json: franklymedia.com  name in sellers.json: Frankly Media
line 46     triplelift.com, 12881, DIRECT, 6c33edb13117fd86
             → domain in sellers.json: flosports.com  name in sellers.json: FloSports
line 177    ssp.cadent.com, 1797, DIRECT, 1e1d41537f7cad7f
             → domain in sellers.json: flosports.com  name in sellers.json: Flosports
line 178    ssp.cadent.com, 2150, DIRECT, 1e1d41537f7cad7f #OB
             → domain in sellers.json: flosports.com  name in sellers.json: Flosports
line 302    gumgum.com, 14075, DIRECT, ffdef49475d318a9
             → domain in sellers.json: flosports.com  name in sellers.json: FloSports

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

line 11     smartadserver.com, 4342, DIRECT, 060d053dcf45cbf3
             → sellers_json: HTTP 404
line 12     smartadserver.com, 3926, DIRECT
             → sellers_json: HTTP 404
line 13     smartadserver.com, 4071, DIRECT
             → sellers_json: HTTP 404
line 14     smartadserver.com, 4228, DIRECT
             → sellers_json: HTTP 404
line 34     telaria.com,n92cp-ooy34,DIRECT,1a4e959a1b50034a #Telaria
             → sellers_json: HTTP 403 to automated requests
line 37     telaria.com,oyz9g-o97cq,DIRECT,1a4e959a1b50034a #Magnite-Vizio
             → sellers_json: HTTP 403 to automated requests
line 39     telaria.com,as2as-2zgv1,DIRECT,1a4e959a1b50034a #OMGCA
             → sellers_json: HTTP 403 to automated requests
line 50     appnexus.com, 9601, DIRECT #XanderAPS
             → sellers_json: HTTP 403 to automated requests
line 53     rhythmone.com, 2061927114, DIRECT, a670c89d4a324e47
             → sellers_json: HTTP 403 to automated requests
line 54     rhythmone.com,1955794380, DIRECT, a670c89d4a324e47 #R1EB
             → sellers_json: HTTP 403 to automated requests
line 65     smaato.com, 1100058601, DIRECT, 07bcf65f187117b4 #Springserve
             → sellers_json: HTTP 403 to automated requests
line 66     smaato.com, 1100058596, DIRECT, 07bcf65f187117b4 #Publica
             → sellers_json: HTTP 403 to automated requests
line 69     transmit.live, 60d619c4c1ed1d0075994755, DIRECT, 82507eb6a3d86ba0
             → sellers_json: HTTP 404
line 70     freewheel.tv, 538917, RESELLER, 82507eb6a3d86ba
             → sellers_json: HTTP 403 to automated requests
line 82     lgads.tv, 759273, DIRECT
             → sellers_json: HTTP 403 to automated requests
line 83     telaria.com,2auap-v5qjd,DIRECT,1a4e959a1b50034a #MagnitePay
             → sellers_json: HTTP 403 to automated requests
line 87     originmedia.tv, 19372216, DIRECT, 117241431
             → sellers_json: file is not valid JSON
line 88     telaria.com, 9we64-hsgu8, RESELLER, 1a4e959a1b50034a
             → sellers_json: HTTP 403 to automated requests
line 90     freewheel.tv, 1598785, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 91     freewheel.tv, 1598786, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 101    telaria.com,oyz9g-o97cq,DIRECT,1a4e959a1b50034a
             → sellers_json: HTTP 403 to automated requests
line 120    openx.com, 558228330, RESELLER, 6a698e2ec38604c6 #yieldmoEB
             → sellers_json: HTTP 403 to automated requests
line 124    freewheel.tv, sg1256491, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 125    freewheel.tv, 534465-r-523319, RESELLER
             → sellers_json: HTTP 403 to automated requests
line 126    smartadserver.com, 4478, RESELLER
             → sellers_json: HTTP 404

info

DIRECT accounts marked confidential

Buyers can't see who owns these accounts.

How to fixAsk the ad system to publish your seller entry with name and domain.

Evidence (2)

line 177    ssp.cadent.com, 1797, DIRECT, 1e1d41537f7cad7f
line 178    ssp.cadent.com, 2150, DIRECT, 1e1d41537f7cad7f #OB

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