Type
Product improvement
Description
A simple enable/disable toggle for DNS entries
Benefit
We don’t have to delete DNS entries entirely.
This lets us also test the impact of removing entries that may be linked to something we have no visibility of.
Wonder how would that have an impact on importing and/or exporting DNS records to/from Cloudflare? 
Those which aren’t “enabled”, wouldn’t be exported at all because they’re actually not DNS records which should be used somewhere else, or? Someone might raise a question ‘where is my DNS record, I expored all?’ and then blame Cloudflare for having such feature? Not a case from my viewpoint.
Then why to keep them there at all?
If proxy 
isn’t working due to some reason for the user and which needs troubleshooting, we can have unproxied 
(DNS-only) and check, otherwise remove for the security concern.
I can only image more troubleshooting issues for all such as case “… my Website doesn’t work but I added DNS record … yep, but you didn’t enabled it”.
I assume this might be by using the apex (*) wildcard DNS record which causes such issues for users, whos’ sub-domains are unknown, but still resolving for some other reason.
DNS maintenance strategy nowadays has to be ensured from the user, administrator, etc. and taken seriously as business grows.
What I was thinking was a lot more simple - see image attached. As for import/export, you should just have a column header which should say Enabled True or False.
Thank you for idea!
The only thing which might be is the UI confussion, e.g. “I’ve enabled the DNS record”, however it’s not proxied and when guiding the customer it might create confussion at first sight or this might be oversight step for them. Nevertheless, happy to share toughts before it would get implemented 
