DDoS Protection Guide

A quick, practical checklist to harden your site against floods and abusive traffic.

Updated 8/17/2025
1.

Put an edge in front of your origin (WAF/CDN).

This soaks up L3/L4/L7 traffic and hides your server. Enable caching for static assets to reduce origin work.

2.

Hide your origin IP with Secure DNS.

Keep DNS pointing to your edge, not your server. If you need custom DNS to mask origin, check our partner callitdns.com (launching soon).

Partner: callitdns.com — Secure DNS made simple (launching soon).

3.

Lock in HTTPS.

Force HTTP→HTTPS redirects, add HSTS, and prefer HTTP/2/3 for resilience under load.

4.

Add basic rate limiting.

Throttle high‑cost endpoints (auth, search, forms, APIs). Consider IP + token buckets and circuit breakers.

5.

Reduce dynamic work.

Cache pages where safe, precompute results, and move heavy tasks to queues/background jobs.

6.

Protect admin/origin endpoints.

Restrict by IP or auth, avoid exposing origin hostnames publicly, and block direct hits at the provider firewall.

7.

Monitor and alert.

Track request rates, error spikes, and cache hit ratio. Alert on anomalies and auto‑scale where possible.

Run a free scanHow to hide your origin IPWAF vs CDN

This guide is vendor‑neutral; use any reputable edge/WAF. We’ll publish a Secure DNS setup flow at launch with callitdns.com.