Topic · DNS & Infrastructure
DNS wildcard record
A DNS wildcard record can synthesize responses for otherwise nonexistent names beneath a DNS zone.
How it works
Wildcard matching follows DNS closest-encloser rules rather than acting as an unrestricted string match.
What can go wrong
Wildcards may cause unexpected subdomain existence checks or create spoofable service endpoints.
What to check or do
Test existing and nonexistent labels against authoritative servers before relying on wildcard assumptions.
How to investigate DNS wildcard record
- Signal to investigate
- A wildcard DNS record makes nonexistent mail-related names appear to resolve.
- Evidence to collect
- Compare exact owner queries with wildcard matches and check whether explicit records exist under the zone.
- Common wrong conclusion
- Wildcard DNS behavior does not imply wildcard DMARC, SPF or DKIM policy handling.
How to interpret the evidence
Wildcards synthesize answers only in certain name-existence conditions. Email authentication protocols define their own owner names and record-discovery rules, so a wildcard is not a substitute for protocol-specific publication.
What to change and how to verify it
Create required _dmarc, _domainkey and _bimi records explicitly and verify their complete names.
Put this into practice
Run a focused check, then explore protection if your domain needs it.