Greetings,
Thank you for writing.
First of all, wishing you all the best in 
Looks like you’re not having the A type DNS records pointed to your web hosting server, or a temporary IP, proxied 
at the DNS tab of Cloudflare dashboard.
Could you please navigate to the DNS tab of Cloudflare dashboard for your zone and cross-check? Please add the missing DNS record.
- Click on the button “Add record”.
- Type @ for the name field
- For IPv4 address enter 192.0.2.1
- Make sure it’s proxied .
- Click on “Save” button to apply and save changes.
In picture:
Wait for few minutes so you’d get the Universal SSL certificate issued for your proxied hostname and then double-check if the configured Redirect rule is active (green checkmark) and working as expected.
In case if needed, here are the step-by-step instructions:
In the meantime, you might have to try with a different Web browser, clear your cache & data, or use Incognito Mode (Private Window) since your local machine (device) DNS cache might still not resolve despite you’ve added the missing DNS record.
Can confirm I got the “Access denied” page.
I’d suggest you to double-check the Security → Events at Cloudflare dashboard under your Cloudflare account for your zone, or via direct link https://dash.cloudflare.com/?to=/:account/:zone/security/events.
You should be able to see the challenged or blocked event under the Security tab → Events at Cloudflare dashboard for your zone and know exactly which security option was triggered. Could be Managed Rules my best guess, otherwise Bot Fight Mode or Browser Integrity Check.
Once you find them, click on a particular one to find more details about it (user-agent, IP, HTTP version …). If yes, could you share some details which service was triggered that blocked you?
May I ask if it is L7 DDoS HTTP Spam, or rather some other? 
If above, kindly, if you have received an email related to your zone having potentially abusive behaviour, please reply to the email that you’ve received from Cloudflare team.
Otherwise, please reach out directly to [email protected].
This issue has to be checked and solved by the Trust&Safety team.
Thank you for patience.
Please, do acknowledge below if it’s related to your case as well: