betfred.com images not loading properly

[#1]

I'm having problems with http://www.betfred.com  Is anybody else seeing an issue?

Lots of the images aren't loading and the site just generally isn't functioning properly.  It's fine if I go via a non-Plusnet connection.

Seems to have started in the last couple of days.

Moderator's note by Dick (Strat) Link fixed

[#2]

your link gives me ,,,, HTTP Error 400. The request hostname is invalid. 

[#3]

Take out the trailing . in the link and it works.

[#4]

Oops - I can't modify the original post to remove the trailing .  If you can edit it Strat, could you do so please?

I'm still getting the issue on the site where a load of the images don't load and navigation is broken, across multiple browsers and PCs, all behind my plusnet connection.  Fine if I connect via a different ISP.

[#5]

Link fixed.

[#6]

It doesn't work in Opera or firefox..

BUT it does work in TOR Browser

That is usually an indication that the ISP is blocking it. (Maybe your firewall, maybe they use bad packets?)

[#7]

It's working for me fine via Firefox, it could be a DNS issue have you tried different ones, I use OpenDNS  

[#8]

@carvell, I've a suspicion it's related to the IP address you're assigned (it's in the 209.93.0.0/16 range). See here.

[#9]

Ah, yes, almost certainly.  Especially given that when trying to access the mobile betfred.com returns "There may be a problem with your connection".

Ah well, could you add betfred.com to the list of sites to try to negotiate with please!

[#10]

Open DNS supports my theory - the PNet DNS are set to block BetFred.

Not that I blame them, I despise online gambling (well, it;s not really gambling, it's scratch cards but played online, not like a REAL Blackjack table or roulette wheel)

At any rate, if idiots want to do it then it;s not PNet's place to play nanny and stop them.

[#11]

@Casey: I use Google's DNS, not Plusnet.  I'm sure it's this geolocation issue, especially given that the mobile site point blanc refuses to load on the Plusnet connection.  Same with William Hill.

[#12]

It IS possible.. But I;m using Pnet's DNS

GFeoLoc says I'm in London. If i try that sire with the browsers direct it's a no-go.. use TOR broswer and it's fine (which implies it's not a GeoLoc issue as TOR says I'm in Germany... or Switzerland.. or...) Where does Google DNS say you are? It IS possible - if G Dns says you;re in America then BF might be blocked there (America is NOT "the land of the free"!!).

But that doesn't explain why my London GeoLoc is blocked and the TOR browser isn't...

Maybe there are two issues - the geolocation AND a block?

[#13]

---

@Casey wrote:
Open DNS supports my theory - the PNet DNS are set to block BetFred.

Eh?

The only time you'll see gambling sites blocked is if you have Safeguard switched on and configured to block them. You'd also need to be using the 213.120.234.42 and 213.120.234.38 resolvers.

If you're using the traditional Plusnet DNS addresses - 212.159.6.9, 212.159.6.10, 212.159.13.49 and 212.159.13.50 - then nothing is blocked.

[#14]

While I agree with your words, in general, it doesn't explain why Opera and firefox, direct, are blocked - FFox even posts the "website not found" message". But TOR browser - which is only FFox routed through the TOR network - works perfectly. The simple act of needing a TOR proxy tends to imply the ISP carries the block... "tend to" becasue it's possible that BF might block incoming requests from the Pnet network (maybe someone on PNet screwed them over and they IP blocked the whole lot). Why else is direct blocked and proxy not blocked?

[#15]

I'm not convinced your problem is the same one being reported by @carvell. For a start, you're not assigned a 209.93 IP, instead your IP is from a range that's been in operation for years.

Even if our content filter was blocking access, it wouldn't return a 404 error.

Are you able to trace to the website? This is what I get and I can access the site:

>tracert www.betfred.com

Tracing route to www.betfred.com [195.244.208.158]
over a maximum of 30 hops:

  1     5 ms     5 ms    68 ms  home.gateway [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    13 ms    74 ms    10 ms  172.17.7.237
  5    15 ms    13 ms    13 ms  172.17.11.230
  6    29 ms    20 ms    12 ms  be2.psb-ir01.plus.net [195.166.129.180]
  7    12 ms    76 ms    14 ms  core1-BE1.southbank.ukcore.bt.net [195.99.125.130]
  8    50 ms    13 ms    14 ms  62.172.103.23
  9    24 ms    74 ms    13 ms  t2c3-et-3-1-0-0.uk-lon1.eu.bt.net [166.49.211.236]
 10    13 ms    76 ms    13 ms  166-49-211-254.eu.bt.net [166.49.211.254]
 11    43 ms    13 ms    13 ms  ae14-xcr1.lnd.cw.net [195.2.30.113]
 12   106 ms    83 ms    49 ms  cw-guernsey-gw.lnd.cw.net [195.89.19.102]
 13    47 ms    97 ms    81 ms  ten1-2-rtcch01.blk.gibtelecom.net [212.120.252.9]
 14    71 ms    80 ms    48 ms  gi0-0-0-1-rtafr01.gibtelecom.net [212.120.234.114]
 15    47 ms   104 ms    87 ms  212.120.234.126
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21  ^C