A catch-all is a rule that accepts anything which does not match a more specific target. The best-known example is email: a catch-all address receives every message sent to your domain even when the exact name does not exist, so mail to a typo or an old address still lands somewhere instead of bouncing back to the sender.
Think of it as the lost-and-found desk at a large building. Most deliveries have a clear recipient and go straight to them. But anything addressed to a name nobody recognises ends up at one central desk where someone can sort it out, rather than being thrown away. The catch-all is that desk.
The same pattern appears beyond email. On a web server, a catch-all route handles any request that did not match a known path, often by showing a friendly error page. Setting one up usually involves the right DNS records for mail, or a fallback rule in your web server config for traffic. The downside for email is that catch-alls also attract spam, since a sender does not need to guess a real address to reach you. A growing twist is that a catch-all also makes life harder for email verification tools. When they probe whether sam@yourdomain exists, the server says yes to everything, so a marketer cannot tell a real inbox from a made-up one. That is why many teams now prefer a handful of named aliases like info@ and support@, plus a quiet forwarding rule for the rare misaddressed message, rather than one open catch-all.
At TopDevs we set up catch-all rules deliberately, balancing the convenience of never losing a message against the spam it can invite.
