Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Domains & DNS

Wildcard DNS risks: what a catch-all record can accidentally match

Published August 2026 · 2 min read · Updated 2026-09-05

Wildcard DNS matches otherwise-unconfigured names under a label, which can be convenient for dynamic environments but also hides typos, abandoned hosts, unintended virtual-host routing, and certificate/security assumptions. Use wildcards when the application genuinely expects arbitrary names, not as a substitute for knowing the inventory.

Understand which names the wildcard catches

A wildcard such as *.example.com applies according to DNS wildcard synthesis rules and does not simply override every explicit record. Test existing names, missing names, deeper labels, and delegated subdomains to understand behavior.

Explicit records can stop wildcard matching at particular nodes even when no record of the queried type exists there.

Consider web virtual-host behavior

If every random hostname resolves to the same server, the web server or application must decide whether to serve content, reject unknown Host headers, or redirect. A default vhost that exposes the main site can make typo/subdomain discovery look legitimate.

Keep TLS certificate coverage aligned; a wildcard certificate has its own hostname-depth rules.

Avoid masking inventory problems

Monitoring and asset management become harder when any hostname resolves. Explicit records are usually clearer for fixed production services, mail hosts, APIs, and administrative interfaces.

Never use a wildcard to expose management services that should have no public name.

Review wildcard dependency before migration

When changing DNS providers or application routing, test representative generated names plus unknown names. Remove the wildcard when the business use case ends.

  • Test wildcard synthesis rules.
  • Reject unknown Host headers where appropriate.
  • Keep fixed services explicit.
  • Audit wildcards during migrations.

Next step

Use wildcard DNS only where its fallback behaviour is understood, and test explicit names, mail, certificates and application routing for unintended matches.

Explore DotMoose domains and DNS

Keep reading

Related guides.

CAA record planning: control which certificate authorities may issue for a domain

Plan CAA records around the certificate providers you use, subdomains and incident contacts, then verify issuance will still work before enforcing restrictions.

Read the guide

CNAME chain problems: why extra DNS aliases can break or slow resolution

Trace CNAME chains, loops, missing terminal records and provider restrictions, then shorten unnecessary aliases without changing the intended hostname.

Read the guide

DKIM selector rotation: change signing keys without breaking verification

Rotate DKIM selectors by publishing the new key first, switching signers, monitoring authentication and retaining the old selector long enough for queued mail.

Read the guide

More domains & dns guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move