Technologist
Posted Oct 22, 2026
Wow! It’s been a very, very long time since I last published anything on this blog.
Like so many developers, I’m guilty of letting my personal corner of the web sit quietly in the background while busy building projects, solving client problems, and getting caught up in the day-to-day. Every so often I’d think, “I really ought to write a post about what I’ve been working on,” only to push it to the back burner.
Dusting off the keyboard today feels long overdue, and a recent refactor project gave me the perfect excuse to finally break the silence.
A few years ago, I found myself repeatedly running into a classic web development headache: trying to help clients, friends, and colleagues figure out where their DNS was actually hosted.
If you’ve ever managed client websites or migrated domains, you know the drill:
“We need to launch the new site this week! Who manages your DNS?”
“Uh… GoDaddy? Or maybe Network Solutions? Or our old marketing agency?”
For developers, popping open a terminal to run dig +trace NS domain.com or whois is second nature. But for non-technical folks, asking them to touch a terminal is a non-starter. And even for developers, discovering that a domain points to ns1.digitalocean.com or ns-123.awsdns.com is only half the battle. The very next step is inevitably hunting down that provider’s login portal, knowledge base, or account recovery page so the client can find their credentials.
To solve that scratch-your-own-itch problem, I originally built whois.theirnameservers.com (which I wrote about back when it first launched).
Recently, I decided it was time to give the tool a comprehensive modernization and UX overhaul. Here’s a look at what the tool does, how it works under the hood, and how I used Google DeepMind’s Antigravity and Gemini to refactor and polish it.
What TheirNameservers Does
The philosophy behind TheirNameservers is straightforward: fast answers with zero friction.
You visit whois.theirnameservers.com, paste whatever you have into the search box, and hit Enter.
Instead of an intimidating wall of raw DNS zone file text, you get:
- The Confirmed Active Nameservers: Cleanly listed with one-click copying.
- Provider Recognition: Automatic detection of recognized DNS hosts (Cloudflare, AWS Route 53, GoDaddy, Namecheap, Bluehost, DigitalOcean, Google Cloud, Wix, Squarespace, Shopify, and dozens more).
- Action Shortcuts: Direct links to that specific provider’s login page, lost password form, homepage, and documentation—saving you the search detour.
- Shareable Deep Links: Clean URLs (
whois.theirnameservers.com/example.com) that you can instantly send to a client or teammate with one click.
My Favorite Usage Trick: The Address Bar Prefix
While the search box on the homepage is handy, my personal favorite way to use the tool—and the trick I rely on almost every day—is doing lookups directly from the browser’s address bar.
Because the parser handles full URLs and protocol strings seamlessly, you never even have to navigate to the homepage first. If you are browsing a website and wonder “Who hosts their DNS?”, you can simply click your address bar, jump to the front of the URL, and prefix it with https://whois.theirnameservers.com/:
https://whois.theirnameservers.com/https://any-site-you-are-on.com/blog/article
Hit Enter, and the site instantly strips the extra protocol, path, and parameters, runs the nameserver lookup, and displays the result modal immediately.
Likewise, you can just paste any URL, domain, or copied link right after the domain in a new tab:
https://whois.theirnameservers.com/example.com
No clicking into search inputs or manually cleaning up https:// prefixes beforehand—just instant answers straight from your URL bar.
What’s Powering It Under the Hood
I wanted the tool to be blazingly fast, resilient, and lightweight—no heavy JavaScript SPA frameworks, no bloated client-side bundles, and no unnecessary database dependencies.
Here is what powers the stack:
1. Robust “Dirty Input” Normalization
People rarely paste clean domains. They paste full URLs copied from browser address bars (https://www.example.com/page?ref=campaign), email addresses (info@company.co.uk), or strings containing zero-width Unicode spaces and full-width dots.
Before running any lookup, the backend parser strips protocols, userinfo, trailing paths, query strings, and ports. It handles Internationalized Domain Names (IDN / Punycode conversion) and intelligently extracts the registrable root domain across complex multi-part TLDs (like .co.uk, .gc.ca, .com.au, and CentralNic SLDs) so queries don’t fail just because someone pasted a subdomain or localized URL.
2. High-Performance Native DNS Queries
Lookups query authoritative nameservers directly with minimal latency. Matched nameserver hostnames are evaluated against an internal signature directory that maps host patterns to verified provider metadata and administrative links.
3. Native Web Platform UI & Tailwind CSS
- Native
<dialog>Modal: Results display in an accessible HTML5<dialog>element styled with fluid 300ms cubic-bezier entrance transitions and native backdrop blurring. - Inlined Minified CSS: The site styles are compiled with Tailwind CSS and delivered inline in the HTML payload, ensuring zero render-blocking CSS network requests.
- Browser History Integration: Opening and closing result modals synchronizes with the browser’s
HistoryAPI (pushState/popstate), so the browser’s native Back and Forward buttons work exactly as users expect. - Ambient Visuals with Reduced-Motion Awareness: The desktop experience features an ambient background video that automatically disables itself if the visitor has
prefers-reduced-motionenabled or uses a browserSave-Dataheader.
The Refactor: Pair Programming with Gemini and Antigravity
For this latest update, I brought in Antigravity (Google DeepMind’s agentic AI coding environment) running Gemini 3.8 Flash as my pair-programming copilot.
Refactoring a production utility isn’t just about asking an LLM to generate generic code; it’s about sweating the small, frustrating edge cases that differentiate a rough prototype from a polished, production-ready tool.
Having an agentic assistant that directly understands the project structure, builds the assets, and iterates on live feedback made a huge difference.
Reflections
Using an agentic tool like Antigravity alongside Gemini highlighted how much pair programming has shifted. Rather than context-switching between editing files, running terminal builds, checking CSS output, and looking up mobile viewport quirks, I could steer the architecture and design intent while the assistant handled the build steps, investigated browser edge cases, and validated the output in real time.
If you ever find yourself needing to quickly check what nameservers a domain is using—or need to hand someone a link to fix their DNS without walking them through a terminal session—give it a spin: