Principal Cyber Prevent and Defense Engineer at a comms service provider with 1,001-5,000 employees
Real User
Top 5
2024-09-10T08:34:03Z
Sep 10, 2024
I have not extensively worked with it, so I can't think of any improvements that are needed in the tool at the moment. It is a foolproof solution. The support is great. I don't think that I can come up with any cons about the tool at the moment. The integration of LLMs on the dashboard is something that is needed in the tool. What Cloudflare is doing internally is that it is stepping ahead in areas like detection and protection. The tool should integrate LLMs on the dashboards and assist you with policy creation.
Senior Solutions Architect at Think Power Solutions
Real User
Top 5
2024-05-17T04:50:00Z
May 17, 2024
It can improve the central time, performance, and SEO schema. Cloudflare performs well with static content. However, there are some performance considerations when it comes to dynamic content that involves fetching data from databases or using APIs. We are not currently using Cloudflare for an e-commerce website. Still, if we were to add an e-commerce site on a platform with region-specific pricing and content, Cloudflare's service might need improvements in handling these dynamic requirements.
Managed Services Manager at Adapture Technology Group
MSP
Top 5
2024-03-20T08:09:08Z
Mar 20, 2024
We're facing challenges due to an upgrade in the machine learning model. The problem arises from some users abusing the APIs, resulting in an influx of suspicious traffic. Cloudflare's learning model mistakenly identifies this traffic as human. Consequently, it assigns it a higher trust score, akin to legitimate human traffic, causing complications in our architecture. Previously, such traffic would have been categorized as suspicious, enabling us to apply appropriate blocking rules. However, we encounter difficulties distinguishing between genuine and suspicious traffic with the new categorization. Despite these challenges, overall, Cloudflare remains the preferred solution compared to Azure, AWS CloudFront, and Google Cloud Armor.
Senior Cloud Solution Architect at ITSG integrated Technology Solution Group
Real User
Top 5
2024-01-18T02:46:42Z
Jan 18, 2024
Cloudflare DNS is still a new tool in the market. I haven't come across any issues with the product. I did two designs with the help of Apigee and Cloudflare. I had done one design with the help of Apigee, while the other one was done with Cloudflare. In a lot of organizations, when it comes to the area of design, companies don't understand the broader perspective of what I try to do, how I try to do it or try to understand the right configuration needed. Areas like how assessment, discovery, and payload are dealt with and how it all comes into your organization can be considered when trying to make suggestions to Cloudflare for improvements. The improvements to be made in the tool can be based on your thought process instead of trying to bring up something that is over-prescribed or over-allocated by others, which won't make sense. Based on the functional requirements of every user of the tool, improvements need to be made to the product.
Cloudflare's free plan is limited to 5,000 records for their free plan. They should increase that. For example, if I create a domain called abc.com and a subdomain called a.abc.com, my record count will be two. I can make a maximum of 5,000 subdomains. However, if we use our own DNS hosted on another provider, there is no limit. Their free plan also lacks name server customization.
IT Security Director at a financial services firm with 1,001-5,000 employees
Real User
Top 5
2023-03-20T14:48:39Z
Mar 20, 2023
I'm not aware of any areas in need of improvement. There might be helpful if there was some web application firewall feature. That way, I wouldn't need a third-party solution like Radware.
At the moment, they are all mostly positive. There will most likely be enhancements in the future. I believe they currently have this feature, but there will most likely be integration with APIs so we can control some features through API. I have all of the features I need here. The one feature that is paid is the custom nameservers instead of using the default ones, I want to use a custom one. Otherwise, I'm already pleased with most of the features.
Cloudflare offers DDoS protection, security, DNS management, and CDN services to enhance website performance and security. Users benefit from improved load balancing and comprehensive security features, making it a reliable choice for managing web traffic and protecting against cyber threats.Cloudflare is widely recognized for its comprehensive features that cater to web security and performance. Users frequently take advantage of its DDoS protection, flexible SSL options, and content...
I have not extensively worked with it, so I can't think of any improvements that are needed in the tool at the moment. It is a foolproof solution. The support is great. I don't think that I can come up with any cons about the tool at the moment. The integration of LLMs on the dashboard is something that is needed in the tool. What Cloudflare is doing internally is that it is stepping ahead in areas like detection and protection. The tool should integrate LLMs on the dashboards and assist you with policy creation.
It can improve the central time, performance, and SEO schema. Cloudflare performs well with static content. However, there are some performance considerations when it comes to dynamic content that involves fetching data from databases or using APIs. We are not currently using Cloudflare for an e-commerce website. Still, if we were to add an e-commerce site on a platform with region-specific pricing and content, Cloudflare's service might need improvements in handling these dynamic requirements.
The pricing could be improved.
We're facing challenges due to an upgrade in the machine learning model. The problem arises from some users abusing the APIs, resulting in an influx of suspicious traffic. Cloudflare's learning model mistakenly identifies this traffic as human. Consequently, it assigns it a higher trust score, akin to legitimate human traffic, causing complications in our architecture. Previously, such traffic would have been categorized as suspicious, enabling us to apply appropriate blocking rules. However, we encounter difficulties distinguishing between genuine and suspicious traffic with the new categorization. Despite these challenges, overall, Cloudflare remains the preferred solution compared to Azure, AWS CloudFront, and Google Cloud Armor.
Cloudflare DNS is still a new tool in the market. I haven't come across any issues with the product. I did two designs with the help of Apigee and Cloudflare. I had done one design with the help of Apigee, while the other one was done with Cloudflare. In a lot of organizations, when it comes to the area of design, companies don't understand the broader perspective of what I try to do, how I try to do it or try to understand the right configuration needed. Areas like how assessment, discovery, and payload are dealt with and how it all comes into your organization can be considered when trying to make suggestions to Cloudflare for improvements. The improvements to be made in the tool can be based on your thought process instead of trying to bring up something that is over-prescribed or over-allocated by others, which won't make sense. Based on the functional requirements of every user of the tool, improvements need to be made to the product.
Cloudflare should add more documentation and pricing to the cloud version.
Cloudflare's free plan is limited to 5,000 records for their free plan. They should increase that. For example, if I create a domain called abc.com and a subdomain called a.abc.com, my record count will be two. I can make a maximum of 5,000 subdomains. However, if we use our own DNS hosted on another provider, there is no limit. Their free plan also lacks name server customization.
An integrated SSO would be nice, as well as the ability to integrate with the on-site active directory instead of just AD through Azure AD.
I'm not aware of any areas in need of improvement. There might be helpful if there was some web application firewall feature. That way, I wouldn't need a third-party solution like Radware.
It would be helpful if the solution could continue evolving to compete with the other solutions on the market.
The documentation could improve for Cloudflare DNS.
At the moment, they are all mostly positive. There will most likely be enhancements in the future. I believe they currently have this feature, but there will most likely be integration with APIs so we can control some features through API. I have all of the features I need here. The one feature that is paid is the custom nameservers instead of using the default ones, I want to use a custom one. Otherwise, I'm already pleased with most of the features.