Wierd issue accessing argos.co.uk

[#1]

@FedUpAlready Just had a look and no issues with your link with latest Samsung Internet, Firefox or Chrome all either with PN FTTC or Full Fibre and with or without a VPN (Windscribe).

[#2]

@FedUpAlready 

"Access Denied

You don't have permission to access "http://www.argos.co.uk/" on this server.

Reference #18.beed655f.1787652607.174fba3e

https://errors.edgesuite.net/18.beed655f.1787652607.174fba3e

"

Access Denied Errors: Troubleshooting & What the Reference Number MeansAccess Denied Errors: Troubleshooting & What the Reference Number Means

https://www.memesita.com/access-denied-errors-troubleshooting-what-the-reference-number-means/

Access Denied: It’s Not Just a Blue Screen of Doom (But It Can Be Frustrating)

One thing possibly worth pointing out in the OP: "http://www.argos.co.uk/"

This is hardly the normal route nowadays (although it worked for me using Edge and Opera) which would surely be: https://www.argos.co.uk/   Or the default www.argos.co.uk

 

[#3]

@FedUpAlready 

...As I was trying to say. Before I was VERY rudely interrupted by LITHIUM! 😠

Time to update that "Favicon"!

Lithium - I curse you and all your descendants, for all eternity.

[#4]

@pvmb Fair point about the URL, but it does have https in the address bar.

I started with a link from google search, looking for light weight vacuum cleaners.  Since that gave the error I tried just argos in the address bar, and let it take me there.  If I type in just www.argos.co.uk in Firefox's address bar, it still adds the https and I still get that same error page.

I guess they've employed people, or signed with a hosting company that just don't really know what they're doing, which will no doubt lose them a lot of sales.  I can just use Chrome for now though.

[#5]

Thanks for checking, @Mav . Yes, it seems to be Argos that's causing the problem.

[#6]

@pvmb I'm not sure what you mean about refreshing the Favicon.  I tried this, which googling says should work:

https://www.argos.co.uk/favicon.ico

And hard refreshed that when it showed it.  No effect on the error page though.