Legitimate website blocked

[kirst-hen]

Hi there,

I've got a legitimate website that I need to view for work - eloops.com - that is being blocked by EE broadband/router.

EE customer services were super helpful and tracked down that it doesn't meet the criteria for a trustworthy website but I need more technical information to relay to my international 'colleagues'. They are based in Israel, it is a startup, so any information they can get to make the site safer would be super helpful to them as they are trying to sell in the UK. It's actually a really cool tool for employee engagement too, so totally not dodgy!

Unfortunately any information the super helpful lady tried to give me was drowned out by my son screaming that someone was on my phone and it wasn't for him (he's 20 months old and it was bedtime!) so if anyone knows the technical reasons that would be great - I'm guessing it's a combination of server location, trust certificates and some other techy criteria but am guessing!

Thank you :0)

[XRaySpeX]

What is the full URL for this website? I can't get to it at the mo' over EE BB. I don't think it's a security issue.

[XRaySpeX]

To get round this issue try switching the DNS in the router away from EE's ones to Manual with 1 of these public DNS pairs:

OpenDNS   :	208.67.222.222 & 208.67.220.220
Google DNS:	8.8.8.8 & 8.8.4.4 
Cloudflare DNS	1.1.1.1 & 1.0.0.1  

 I can now get to it with at least 1 of these.

[mikeliuk]

Hi @kirst-hen ,

I highly doubt the website mentioned is blocked by the service provider which shall not be named, but at any rate there is no evidence for this. I would recommend that you split your debugging into two parts:

Part I, name resolution of the domain "eloops.com".

Part II, debugging of access to your website using IPv4 address.

Under part one, I have carried out a DNS lookup for you using a Google DNS server (one of many behind 8.8.8.8).

You may compare against to https://www.linux.com/training-tutorials/check-your-dns-records-dig and the DNS record looks incomplete to me (for example missing name servers, which a whois lookup online suggests should be cloudflare servers), and looks misconfigured even if it is not incomplete.

I have also carried out a quick ping to each of the quoted IP addresses and all at least respond. A lookup suggests that all three IP addresses belong to cloudflare and you may now substitute each one in turn into your browser to carry out Part II of the debugging. Good luck! 😊

[x@x ~]$ dig @8.8.8.8 eloops.com

; <<>> DiG 9.11.20-RedHat-9.11.20-5.el8 <<>> @8.8.8.8 eloops.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43875
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;eloops.com. IN A

;; ANSWER SECTION:
eloops.com. 299 IN A 104.26.8.131
eloops.com. 299 IN A 104.26.9.131
eloops.com. 299 IN A 172.67.73.156

;; Query time: 85 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue May 25 22:41:07 BST 2021
;; MSG SIZE rcvd: 87

[x@x~]$ for i in 104.26.{8,9}.131 172.67.73.156; do ping -c 1 $i; done
PING 104.26.8.131 (104.26.8.131) 56(84) bytes of data.
64 bytes from 104.26.8.131: icmp_seq=1 ttl=53 time=76.0 ms

--- 104.26.8.131 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 76.004/76.004/76.004/0.000 ms
PING 104.26.9.131 (104.26.9.131) 56(84) bytes of data.
64 bytes from 104.26.9.131: icmp_seq=1 ttl=53 time=23.4 ms

--- 104.26.9.131 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 23.379/23.379/23.379/0.000 ms
PING 172.67.73.156 (172.67.73.156) 56(84) bytes of data.
64 bytes from 172.67.73.156: icmp_seq=1 ttl=51 time=35.4 ms

--- 172.67.73.156 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 35.401/35.401/35.401/0.000 ms