You also have 2 _dmarc records when there must be only 1.
[add]
Checking further, there are multiple Cloudflare nameservers pairs resolving for your domain, so make sure you are in the correct/preferred account for your domain and that the nameservers shown at the bottom of this page… https://dash.cloudflare.com/?to=/:account/:zone/dns/records
…are alec and stevie.
hello thanks please advise on why i am still not able to enable the DNSSEC I believe this is preventing the propagation process its been over two days now and my site is still down i must also tell you that i am just a truck driver and know nothing of this making it a bigger challenge to comprehend
I suggest you pause Cloudflare, or set the DNS record to “DNS only” so requests go direct to your server and bypass Cloudflare. Then you can make sure your site is working, if it is not, fix it. Once fixed, you can re-enable Cloudflare.
Don’t mess around with things like DNSSEC at the moment until your site is working properly.
hello i have a certificate and it showing in my details under the ssl/ttls section this just sounds like a ploy to get me into buying a certificate from cloudflare money of which i do not have the main reason for joining cloudflare was the fact they offer a free cdn service but all this was definitely not stressfree and in the meantime my site is still down i forgot nothing in life is free i have paused cloudflare on your suggestion my question is what do i do now ?
It isn’t. I’m just a Cloudflare user. If you think me giving up my free time to help has some ulterior motive, you are welcome to ignore my advice.
Cloudflare origin certificates are free. However your origin certificate does seem to be valid.
Requests are bypassing Cloudflare and going direct to your host and your site is now giving 404 which is coming from your host and nothing to do with Cloudflare.
Work with your host to get your site working, once it is working you can un-pause Cloudflare. Pausing Cloudflare bypasses the proxy, it won’t affect your mail settings.
thanks for your input i really appreciate it the reason why this error message is showing is because of the fact i transferred my domain name to cloudflare my original domain name from payhip is now running which is : PROFESSIONAL TRUCK DRIVER - Payhip but this doesnt make anything better i am now sitting with a dormaint name and all my effort of getting ezimox.space seems to be in vail can i ask if there is anything else i can do to fix this issue i really dont have anyone else to ask thanks again
yes my domain name is on ezimox,space i have had this name for over 3 months and since i migated to cloudflare i have noticed a significant drop on my site visitors please advise on what the problem could be thanks again for the insight
Your site now seems to be loading at your domain ok.
You can try to proxy the DNS records again. If any problems, you’ll have to stay with “DNS only”.
If you do proxy the records and you get an error in a few months’ time, it’s because your host needs to renew their SSL certificate so you can set back to “DNS only” until that happens.
thank you just a quick question is it an option to purchase another domain name with cloudflare and link it to my current domain name to try get passed this proxy issue
according to payhip they say i can only use cloudflare if they are not proxied on the dns records i am just trying to figure out a loophole around this issue as my propagation has still not been finalised and i think this may be the reason my dnssec is still a problem i just thought if i purchase a domain name from cloudflare and linked it to my current url it would sort this problem out