<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DDoS Protection on Eknix — Web security &amp; performance for the enterprise</title><link>https://www.eknix.com/tags/ddos-protection/</link><description>Recent content in DDoS Protection on Eknix — Web security &amp; performance for the enterprise</description><generator>Hugo</generator><language>en-us</language><copyright>© {year} EKNIX LTD. All rights reserved.</copyright><lastBuildDate>Wed, 14 May 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://www.eknix.com/tags/ddos-protection/index.xml" rel="self" type="application/rss+xml"/><item><title>Is Google reCAPTCHA a DDoS Defence? The Cost Math Says No</title><link>https://www.eknix.com/blog/recaptcha-ddos-cost/</link><pubDate>Wed, 14 May 2025 00:00:00 +0000</pubDate><guid>https://www.eknix.com/blog/recaptcha-ddos-cost/</guid><description>&lt;p&gt;There&amp;rsquo;s a category of question that gets asked quietly in Slack channels and in private post-incident reviews: &amp;ldquo;could we just use reCAPTCHA to handle this?&amp;rdquo; It&amp;rsquo;s not an unreasonable instinct. Google reCAPTCHA is already deployed on most sites, it can challenge suspicious traffic, and it costs nothing for the first ten thousand requests. As a lightweight speed bump, it has its place.&lt;/p&gt;
&lt;p&gt;But &amp;ldquo;speed bump against DDoS traffic&amp;rdquo; and &amp;ldquo;speed bump against spam submissions&amp;rdquo; are very different things — and running reCAPTCHA into a volumetric attack has a financial profile that most teams haven&amp;rsquo;t priced out before they need to.&lt;/p&gt;</description></item></channel></rss>