Tried to open wepage and on port 80 got redirected to https

# curl -v http://awesome-hd.net/
* About to connect() to awesome-hd.net port 80 (#0)
* Trying 104.28.6.23... connected
* Connected to awesome-hd.net (104.28.6.23) port 80 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.15.3 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
> Host: awesome-hd.net
> Accept: */*
>
< HTTP/1.1 302 Moved Temporarily
< Date: Sun, 23 Nov 2014 18:14:34 GMT
< Content-Type: text/html; charset=UTF-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: __cfduid=d87ccdc49efd5f40880dc034578138fbf1416766474; expires=Mon, 23-Nov-15 18:14:34 GMT; path=/; domain=.awesome-hd.net; HttpOnly
< Location: https://awesome-hd.net/
< Vary: Accept-Encoding
< Server: cloudflare-nginx
< CF-RAY: 18df58dea02705a3-ARN
<
* Connection #0 to host awesome-hd.net left intact
* Closing connection #0

no responce on port 443

# curl -v https://awesome-hd.net/
* About to connect() to awesome-hd.net port 443 (#0)
* Trying 104.28.6.23... Connection timed out
* Trying 104.28.7.23... Connection timed out
* couldn't connect to host
* Closing connection #0
curl: (7) couldn't connect to host


Scanning from our isp shows what port is filtering.

# nmap -p443 awesome-hd.net

Nmap scan report for awesome-hd.net (104.28.6.23)
Host is up (0.040s latency).
Other addresses for awesome-hd.net (not scanned): 104.28.7.23
PORT STATE SERVICE
443/tcp filtered https

Nmap done: 1 IP address (1 host up) scanned in 1.16 seconds


Meanwhile scaning from different isp than other shows what port 443 is available.

# nmap -p443 awesome-hd.net

Nmap scan report for awesome-hd.net (104.28.7.23)
Host is up (0.062s latency).
Other addresses for awesome-hd.net (not scanned): 104.28.6.23
PORT STATE SERVICE
443/tcp open https

Nmap done: 1 IP address (1 host up) scanned in 1.54 seconds


Conlusiong, port 443 is closed for our isp, id recommend you to contact site admins.