Sorry, I didn’t let name servers at Cloudflare. So…my website is not yet fully back to Cloudflare name servers…
Clearly it is not.
How the ■■■■ is that possible??? It’s fine on my end still.
It appears fine from Sitemeer, but it doesn’t work for me or isitup.org. I don’t know what the underlying issue is, but it appears to be outside of Cloudflare.
I enabled Cloudflare again. I will do other tests again.
Whynodns reports:
You currently have TLSv1 enabled.
This version of TLS is being phased out. This warning won’t break your padlock, however if you run an eCommerce site, PCI requirements state that TLSv1 must be disabled by June 30, 2018.
I show www as proxied but not eko4life.com. I was not testing the www host, only the apex name.
That’s because the meerkats are trustworthy. Those other shady sites on the other hand 
For me, the site loads fine. You get a 503, right @epic.network? Restrictions on PoPs?
You should disable any TLS below 1.2.
Mixed Content - Pass
Sorry, I don’t follow you.
It loads for me and isitup.org now that it is routing through the Cloudflare proxy.
On my host?
You should disable TLS below 1.2 on Cloudflare and your host. TLS 1.1 and lower have not been safe for years.
Testing your site at SSL Labs shows that you disabled TLS 1.2. You will want to leave that one enabled. You only want to disable the versions less than TLS 1.2. That means that TLS 1.2 should still be enabled.
Can’t find anywhere on my host where to set TLS. Cloudflare is using TLS 1.3.
How to resolve SSL errors reported by Whynodns?
I already answered that question. 