<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Domain Management on Upsonar Blog</title><link>https://upsonar.io/blog/categories/domain-management/</link><description>Recent content in Domain Management on Upsonar Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 22 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://upsonar.io/blog/categories/domain-management/index.xml" rel="self" type="application/rss+xml"/><item><title>Why .dev, .app, .page (and 40+ Other TLDs) Don't Respond to WHOIS</title><link>https://upsonar.io/blog/why-dev-app-page-dont-respond-to-whois/</link><pubDate>Sun, 22 Feb 2026 00:00:00 +0000</pubDate><guid>https://upsonar.io/blog/why-dev-app-page-dont-respond-to-whois/</guid><description>&lt;p>I was building &lt;a href="https://upsonar.io/blog/">upsonar.io&lt;/a> — it monitors uptime, SSL certificates, and domain expiration. When I got to domain expiry alerts, I hit a wall.&lt;/p>
&lt;p>Checked &lt;code>.com&lt;/code>, &lt;code>.org&lt;/code>, &lt;code>.net&lt;/code> — worked fine. Then I tried &lt;code>google.dev&lt;/code>.&lt;/p>
&lt;p>Connection refused.&lt;/p>
&lt;h2 id="the-investigation">The investigation&lt;/h2>
&lt;p>First thought: maybe Google blocks WHOIS queries for their domains? Let me check the WHOIS server for &lt;code>.dev&lt;/code>:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" class="chroma">&lt;code class="language-bash" data-lang="bash">&lt;span class="line">&lt;span class="cl">$ whois -h whois.iana.org dev
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Output (trimmed):&lt;/p>
&lt;pre tabindex="0">&lt;code>domain: DEV
organisation: Charleston Road Registry Inc.
...
whois:

status: ACTIVE
remarks: Registration information: https://www.registry.google
&lt;/code>&lt;/pre>&lt;p>See that empty &lt;code>whois:&lt;/code> field? There&amp;rsquo;s no WHOIS server for &lt;code>.dev&lt;/code> at all.&lt;/p></description></item><item><title>What Happens When Your Domain Expires (And How to Prevent It)</title><link>https://upsonar.io/blog/what-happens-when-domain-expires/</link><pubDate>Fri, 13 Feb 2026 00:00:00 +0000</pubDate><guid>https://upsonar.io/blog/what-happens-when-domain-expires/</guid><description>&lt;p>Your domain is the foundation of your online presence. Every page, every email, every API endpoint depends on it. When it expires, everything stops — instantly.&lt;/p>
&lt;p>Yet thousands of domains expire every day, often belonging to active businesses that simply forgot to renew. Here&amp;rsquo;s exactly what happens, day by day, and how to make sure it never happens to you.&lt;/p>
&lt;h2 id="the-domain-expiration-timeline">The Domain Expiration Timeline&lt;/h2>
&lt;h3 id="day-0-expiration-date">Day 0: Expiration Date&lt;/h3>
&lt;p>The moment your domain registration expires:&lt;/p></description></item><item><title>Domain Expiration Monitoring: The Complete Guide</title><link>https://upsonar.io/blog/domain-expiration-monitoring-guide/</link><pubDate>Tue, 10 Feb 2026 00:00:00 +0000</pubDate><guid>https://upsonar.io/blog/domain-expiration-monitoring-guide/</guid><description>&lt;p>Domain expiration monitoring is the practice of regularly checking when your domains expire and alerting you before they lapse. It sounds simple, but the consequences of getting it wrong are severe — complete website downtime, lost email, damaged SEO, and potentially losing your domain to squatters.&lt;/p>
&lt;p>This guide covers everything you need to know about monitoring domain expiration effectively.&lt;/p>
&lt;h2 id="why-you-need-domain-expiration-monitoring">Why You Need Domain Expiration Monitoring&lt;/h2>
&lt;p>Most domain owners assume their registrar handles everything. In reality:&lt;/p></description></item><item><title>WHOIS vs RDAP: The Future of Domain Lookups</title><link>https://upsonar.io/blog/whois-vs-rdap/</link><pubDate>Sat, 07 Feb 2026 00:00:00 +0000</pubDate><guid>https://upsonar.io/blog/whois-vs-rdap/</guid><description>&lt;p>For over 40 years, WHOIS has been the go-to protocol for looking up domain registration data. But it&amp;rsquo;s showing its age. RDAP (Registration Data Access Protocol) is the modern replacement that ICANN has been rolling out since 2019.&lt;/p>
&lt;p>If you manage domains, monitor domain expiration, or work with DNS infrastructure, here&amp;rsquo;s what you need to know about both protocols.&lt;/p>
&lt;h2 id="the-short-version">The Short Version&lt;/h2>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Feature&lt;/th>
 &lt;th>WHOIS&lt;/th>
 &lt;th>RDAP&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>&lt;strong>Created&lt;/strong>&lt;/td>
 &lt;td>1982&lt;/td>
 &lt;td>2015 (RFC 7480-7484)&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Response format&lt;/strong>&lt;/td>
 &lt;td>Free-form text&lt;/td>
 &lt;td>Structured JSON&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Authentication&lt;/strong>&lt;/td>
 &lt;td>None&lt;/td>
 &lt;td>Optional (tiered access)&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Standardization&lt;/strong>&lt;/td>
 &lt;td>Informal&lt;/td>
 &lt;td>IETF standards (RFC)&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>HTTPS support&lt;/strong>&lt;/td>
 &lt;td>No (port 43, plain text)&lt;/td>
 &lt;td>Yes (HTTPS by default)&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Internationalization&lt;/strong>&lt;/td>
 &lt;td>Limited&lt;/td>
 &lt;td>Full Unicode support&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Server discovery&lt;/strong>&lt;/td>
 &lt;td>Manual / hardcoded&lt;/td>
 &lt;td>IANA bootstrap registry&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>&lt;strong>Status&lt;/strong>&lt;/td>
 &lt;td>Being phased out&lt;/td>
 &lt;td>Replacing WHOIS&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;p>&lt;strong>For everyday domain checks&lt;/strong>, both give you the same essential information: registration dates, expiry date, registrar, name servers, and status codes.&lt;/p></description></item></channel></rss>