Looks to me HBL bank is using incapsula to protect their website, but Cloudflare is unable to make out that it needs to take users to the correct https://www.hblibank.com.pk/Login - not some non-SSL site.
It was timing out a few weeks ago (when using CF DNS). This is the reason, I’m not switching over to 18.104.22.168 - and sticking to Google DNS.
Don’t know who needs to fix this - Incapsula or Cloudflare.
Under the theory of “Garbage In, Garbage Out”, I don’t really blame anyone for handling it in any particular way, and I don’t know what the standards say, but maybe 22.214.171.124 should be aligned with those other resolvers.
This is the problem. It seems only Cloudflare has a problem of not being able to handle it. Others in the business (Google, OpenDNS etc.) can all manage it correctly. And, this makes it even more bizarre.
HBL is the largest bank in Pakistan with millions of customers and over $50 Billion in assets. Anyone using Cloudflare DNS and HBL would now be scratching their heads, and probably moving back to ISP’s DNS or Google DNS.
See the links posted by myself and @Judge. This is an issue with the bank and as every day passes, will become inaccessible as other services move towards new standards and securing DNS. Google just announced it will be doing so soon and suspect OpenDNS won’t be far behind either.
I don’t find it condescending. I find it to be an act of frustration in dealing with someone else’s mistakes. Someone configures something incorrectly, but it works. As others clean up their act, this misconfiguration comes to light and they (not you, but the organization with the misconfiguration) get all bent out of shape because it no longer works.
Same thing happened with 126.96.36.199, which was misappropriated by many hardware vendors. Now people get mad at Cloudflare because they can’t reach 188.8.131.52.