ResolveRadar / Product & infrastructure
Go beyond “the record exists.”
DNS diagnostics built around what a configuration is meant to accomplish, and what could stop it from working.
Independent product · In development
The problem
A DNS record can exist, have the right spelling, and still be part of a configuration that fails. Email authentication, tracking links, and other services depend on more than a single successful lookup. Someone still has to connect the pieces.
The idea
Start with what each record is supposed to do. Then examine the conditions and dependencies that have to hold for it to work. The useful question is not just whether a record exists, but whether the configuration supports its intended purpose.
What I am building
ResolveRadar brings that context into DNS monitoring and diagnosis. The product is being developed to turn configuration findings into explanations that help the person responsible understand what needs attention and why.
Where it stands
ResolveRadar is a separate product in development, with a public website and an early-access path. The work draws on my background in email infrastructure and deliverability, where seemingly small configuration details can have consequences across an entire system.
A useful diagnostic should help you decide what to do next.
Another kind of problem
Shadow Data