Ad systems without a public sellers.json
16The 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 (16)
line 11 openx.com, 610028655, DIRECT, 6a698e2ec38604c6
→ sellers_json: HTTP 403 to automated requests
line 16 appnexus.com, 16916, RESELLER, f5ab79cb980f11d1
→ sellers_json: HTTP 403 to automated requests
line 17 freewheel.tv, 535354-r-523319, RESELLER
→ sellers_json: HTTP 403 to automated requests
line 18 freewheel.tv, 535354-r-524565, RESELLER
→ sellers_json: HTTP 403 to automated requests
line 19 freewheel.tv, sg1251727, RESELLER
→ sellers_json: HTTP 403 to automated requests
line 24 smartadserver.com, 5427, RESELLER, 060d053dcf45cbf3
→ sellers_json: HTTP 404
line 25 smartadserver.com, 5855, RESELLER, 060d053dcf45cbf3
→ sellers_json: HTTP 404
line 35 loopme.com, 15270, RESELLER, 6c8d5f95897a5a3b
→ sellers_json: HTTP 403 to automated requests
line 36 loopme.com, 15268, RESELLER, 6c8d5f95897a5a3b
→ sellers_json: HTTP 403 to automated requests
line 45 zetaglobal.net, 989, RESELLER
→ sellers_json: HTTP 404
line 57 zetaglobal.com, 108, RESELLER
→ sellers_json: HTTP 404
line 72 ogury.com, ae2867f7-64af-4f94-a7f7-780ede964919, RESELLER
→ sellers_json: HTTP 403 to automated requests
line 89 loopme.com, 11362, RESELLER, 6c8d5f95897a5a3b
→ sellers_json: HTTP 403 to automated requests
line 92 zetaglobal.net, 716, RESELLER
→ sellers_json: HTTP 404
line 96 smartadserver.com, 4582, RESELLER, 060d053dcf45cbf3
→ sellers_json: HTTP 404
line 104 yahoo.com, 100033, RESELLER, e1a5b5b6e3255540
→ sellers_json: HTTP 429 to automated requests