Script error with firefox

[pete y testing]

hi guys

using firefox i get the following script msg error occasionally when using the snb forum , it doesnt seem to happen on any other site

https://z.moatads.com/quantcas…224&uid=Vrm0_AAO734KaInEhgVb3Q:8

firefox version is 43.0.3

just letting you know and if anyone else has seen this before

 

[L&LD]

hi guys

using firefox i get the following script msg error occasionally when using the snb forum , it doesnt seem to happen on any other site

https://z.moatads.com/quantcas…224&uid=Vrm0_AAO734KaInEhgVb3Q:8

firefox version is 43.0.3

just letting you know and if anyone else has seen this before

Does it happen with the current version of firefox? (Yours is outdated).

Does it happen with another browser? If no; it is your firefox plugins. If yes; it is your system's configuration.

 

[System Error Message]

It seems to work for me on firefox and my firefox is bare minimum.

 

[sfx2000]

using firefox i get the following script msg error occasionally when using the snb forum , it doesnt seem to happen on any other site

Regional ad provider's banner ad/javascript perhaps?

Things have been ok here in the US across different browsers...

 

[pete y testing]

Regional ad provider's banner ad/javascript perhaps?

quite possible as its now gone away

 

[pete y testing]

ok , its back again

Script: https://secure-ds.serving-sys.…urstingScript/SZMKFLVPAIDBR.js:27

keeps coming up in firefox

on 47.0 firefox

 

[stevech]

This is what I get right now (11Jun16 21:37 PT)
Firefox can't find the server at secure-ds.serving-sys.xn--urstingscript-9q16e.

 

[sfx2000]

That's odd - wonder if your ISP is doing ad-insertion - many do to the chagrin of site owners, as the ISP is sneaking revenue opportunities away due to the substitution (or worse, the ad, while suppressed, is sent as a page view, nasty stuff)

While normally we don't talk about ad-blockers, Ghostery can be handy to localize which ad-provider is causing concerns thru selective blocking - then it's an iterative process of elimination.

An alternate approach would be to go to tools -> Web Developer, and there you might see the offending URL in the debug.

Once it's found, the admins can go back to the provider with the problem report.