ok no worries might be my side, i ping the site and got 100% packet loss.
Many webservers do block ping, and this one does.
Another issue are doing something weird in the HTTP server which is supposed to redirect you to HTTPS: that is,
http://www.uno.uk/ or
http://uno.uk/.
It works fine in Chrome, but they don't like connections from curl:
| Text |
1
23
45
67
8 | $ curl -k http://www.uno.uk
<html><head><title>403 Forbidden</title></head>
<body><center><h1>403 Forbidden</h1></center>
<hr><center>nginx</center></body>
</html> |
Therefore I think they are doing some broken matching on the browser type (User-Agent)
If this is what's affecting you, then entering "https://www.uno.uk" (including the full "https://" prefix) should fix it for you.
It doesn't give great confidence in their technical clue - but then again, many companies outsource their main website to a third party.