I use Cloudflare for legacy websites that I need to protect because they're very vulnerable or to secure a client's critical websites. We will implement it after a review or if the website has gotten a poor grade on one of those online checks to see if the security meets the minimum requirements. 

Usually, after I show them their website is vulnerable, I get them to sign up immediately. For me, it's more of a delta suspender as a security measure. I find that many web developers do a poor job of updating their websites and keeping all the security modules.

Cloudflare has a server, and you point your DNS there. From there, you either enable the passthrough or use their full proxy. When you use their full proxy, you get all the features. If you're only doing the DNS, it's just a basic DNS server. Most people don't use it just for DNS; they use it for proxying their websites. You can proxy other services as well, but I've only used it for web applications on different ports.

We use the solution to personalize content and suggestions for cloud environment and database administration.

In Cloudflare, we utilize their DNS and DDoS protection services. All incoming traffic to our server passes through the Cloudflare network. However, we face challenges when it comes to handling legitimate DDoS attacks. These attacks are well-crafted and mimic genuine requests to our publicly facing web pages. Despite Cloudflare's scoring mechanism, there are concerns about the effectiveness in blocking such attacks, as the traffic still reaches our infrastructure directly. Cloudflare recently introduced a new solution for Captcha, but enabling it poses challenges. Some customers are unhappy with Captcha, and modern AI-based DDoS tools can even bypass Captcha, further complicating the situation.

When I was in Singapore, I used Cloudflare for DNS management, but when I started at Yoma Bank, I started using the application gateway routing and firewall features. 

We typically use it to safeguard websites, especially web applications.

Cloudflare serves as both a Content Delivery Network and a security system. When integrated into the software, it optimizes content loading speeds, ensuring users access content swiftly. Additionally, Cloudflare safeguards websites from various cyber threats, providing security. 

We use Cloudflare for security and delivery.

The first use case was to administer the main domain of the organization where I worked.

We have the entire registration process for the main domain and its subdomains, and we create web application firewall (WAF) and load balancer rules.

We did a major MX migration from Google to Microsoft, and doing that with Cloudflare has given us immense security.

This domain also started to visualize improper accesses from other countries and monitor where the main accesses came from.

We made some blocks of administrator sites that only be accessed by a specific IP.

We monitor traffic on Cloudflare, and we have some applications that we download on Cloudflare. We have ten to twenty gigs per country.

Our customers are residential ISP customers with high traffic because of Google apps, Amazon network peering, and Direct TV, so we use Cloudflare for the customers. For example, we announce all traffic or customer traffic to the BDP station, and Cloudflare works by caching the content, and the servers send the content to our clients.

We are an IT consulting company, we provide solutions to our customers. We implement the solutions for our customers. Some of our customers use CloudFlare, some of them are using  Imperva and Palo Alto.

Our customers use this solution for any web traffic, mostly GCP or to AWS cloud as a backend.

We are a reseller of CDN solutions and this is one of the products that we implement for our customers.

I also use Cloudflare for various websites. It is a content delivery platform.

I use Cloudflare to secure my own websites and servers since I use the proxy functionality to hide my website/server IP. Also, I like to use Cloudflare DNS manager. I think it's simple and easy to use.

We use it for DNS load balancing and WAF. 

I just switched to Cloudflare as my domain registrar. That led me to use their CDN service, and I will probably use them for SSL when that is available. 

Cloudflare is typically a firewall. There are several editions available, such as the free edition.

Our company provides the solution to customers who need website load balancing or DDoS protection. Customers with minimal traffic use the Business Plan and customers with a huge amount of traffic use the Enterprise Plan. 

We currently have thirty customers on the Business Plan and three customers on the Enterprise Plan. 

Our primary use case would be as an immediate wrapper-type security solution as opposed to other solutions which put an in-point monitor on a workstation. I'm the VP of our company and director of IT.

I work as the Senior SEO Strategist on a very small in-house team of digital marketers for Lakeview Health, a drug and alcohol rehab. Upon starting my role, one of my first tasks was migrating our websites to a new web hosting provider so that we could take ownership of them. With all our sites developed in WordPress, I decided on hosting with WP Engine which recommended Cloudflare in the setup process. 

In the past, I worked in environments where the developers and IT team managed the websites, so I admit that there are gaps of knowledge in my understanding of how the internet works. Using Cloudflare made the process of migrating much easier and gave me the satisfaction of knowing we’d receive enhanced security features, alongside a reputable CDN, simple DNS hosting, and the many other solutions Cloudflare offers.

We are using Cloudflare for the CDN for our applications. We deployed the solution as SaaS.

I use this for DNS for many of my former clients and personal sites. When using services like Heroku, Cloudflare is very useful for CNAME flattening. I also use it for their end-to-end SSL with TLS authentication on nginx for securing servers. 

The second major use case is as a CDN where I will push logic to the edge for caching and redirects.

For DDOS mitigation.

Cloudflare is used for service protection. We use this solution as a managed service for our end user customers, such as banking users for protection.

Our customers use the web application firewall and Zero Trust predominantly. 

My primary use for the Cloudflare service is for load balancing. I also use the product to manage the connection to my web server's backend.

In addition to a reliable and easy to use a DNS service, Cloudflare enables us to host websites on hardware in-house, by protecting us against DDoS attacks as well as from our slightly unreliable ISP. 

We primarily provide the solution to our clients. 

It offers DDoS protection, WAF is available, and CDN services are there. You can log the IP address countrywide and it optimizes the content for you.

We primarily use the solution for security purposes. We use the product for theft and DDoS protection.

We use this solution for security.