Email authentication
SPF, DKIM, and DMARC records that prove your mail is legitimate and keep it out of spam.
Product
From intent to diagnosis.
ResolveRadar does not start with a record. It starts with what you are trying to accomplish, then works out whether your DNS configuration can actually deliver it.
Start with intent
What are you trying to do? Pick the job, and ResolveRadar knows the expected DNS behavior behind it.
Tracking domains
CNAME records that route click and open tracking through your own branded domain.
Domain verification
TXT records that prove you own a domain to email platforms, ad networks, and SaaS vendors.
Analyze the configuration
A record can look correct and still fail. ResolveRadar follows the full dependency chain, from your customer's domain to the service it is supposed to reach.
Dependency chain
- Customer domain
- DNS record
- Target hostname
- Expected service
Chain of trust
We verify DNSSEC from the parent zone down and flag unsigned gaps, orphan DS records, and expired signatures.
Resolver behavior
We query multiple public resolvers and authoritative nameservers, because a record that resolves in one place can still fail in another.
Conflicts and limits
We count SPF lookups against the 10-lookup limit, catch conflicting records at the same name, and spot leftovers from old providers.
Diagnose and explain
Every finding is written for the person who has to act on it, not for a DNS engineer.
resolveradar · diagnostic report
Issue detected
A new vendor's SPF include pushed this domain past the 10-lookup limit, so email authentication is failing silently.
Why this matters
Receiving servers treat mail from this domain as unauthenticated. Receipts and notifications will increasingly land in spam.
Recommended action
Flatten the SPF record or remove the unused include from the old provider. Here is the exact change, ready to hand to whoever manages the zone.
Move beyond DNS lookup.
See what intent-aware diagnostics find on real configurations.
Request Early Access