<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Sahil Ranpariya</title>
    <description>The latest articles on DEV Community by Sahil Ranpariya (@sahil_ranpariya).</description>
    <link>https://dev.to/sahil_ranpariya</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4256258%2Ff2b51e5f-6c99-4f60-97bc-34b314ac2110.png</url>
      <title>DEV Community: Sahil Ranpariya</title>
      <link>https://dev.to/sahil_ranpariya</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sahil_ranpariya"/>
    <language>en</language>
    <item>
      <title>Handling Domain Expiry</title>
      <dc:creator>Sahil Ranpariya</dc:creator>
      <pubDate>Fri, 20 Nov 2026 19:39:15 +0000</pubDate>
      <link>https://dev.to/sahil_ranpariya/handling-domain-expiry-12pm</link>
      <guid>https://dev.to/sahil_ranpariya/handling-domain-expiry-12pm</guid>
      <description>&lt;h1&gt;
  
  
  Introduction to Domain Expiry Alerts
&lt;/h1&gt;

&lt;p&gt;As a developer, I've seen firsthand how a missed domain expiry can lead to website downtime and lost business. It's a problem that can be easy to overlook, especially for freelancers and small agencies managing multiple client sites. To address this issue, I built a feature into my SitePulse product that checks domain expiry dates and sends alerts when they're about to expire.&lt;/p&gt;

&lt;h1&gt;
  
  
  How Domain Expiry Checks Work
&lt;/h1&gt;

&lt;p&gt;The domain expiry check looks up each domain's expiry date every day using RDAP, with a WHOIS fallback. It supports a wide range of top-level domains, including .com, .in, .co.uk, .io, .co, and many more, as long as the registry publishes the expiry date. If the registry doesn't publish the date, SitePulse will indicate that instead of making an incorrect guess.&lt;/p&gt;

&lt;h1&gt;
  
  
  Alerts and Notifications
&lt;/h1&gt;

&lt;p&gt;When a domain's expiry date is approaching, SitePulse sends email alerts 30, 7, and 1 day before it expires. This gives site owners ample time to renew their domain and avoid any potential downtime. These alerts are part of the Pro plan, which also includes other features like client status pages and monthly reports.&lt;/p&gt;

&lt;h1&gt;
  
  
  Trade-Offs and Limits
&lt;/h1&gt;

&lt;p&gt;While the domain expiry check is a valuable feature, it's not foolproof. If a registry doesn't publish the expiry date, SitePulse won't be able to provide an accurate alert. Additionally, the check only runs daily, so there might be a small window where a domain expires before the next check runs. Despite these trade-offs, I believe the domain expiry check is a useful tool for anyone managing multiple websites.&lt;/p&gt;

&lt;h1&gt;
  
  
  Conclusion
&lt;/h1&gt;

&lt;p&gt;If you're interested in learning more about SitePulse and its features, including the domain expiry check, you can visit &lt;a href="https://sitepulse.buymazing.in" rel="noopener noreferrer"&gt;https://sitepulse.buymazing.in&lt;/a&gt;. I built this to help freelancers and small agencies like myself manage client sites more effectively, and I hope you find it useful. The free plan is available now, with features like email alerts and second opinions from Europe and Asia.&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Building Uptime Monitoring</title>
      <dc:creator>Sahil Ranpariya</dc:creator>
      <pubDate>Fri, 20 Nov 2026 19:09:01 +0000</pubDate>
      <link>https://dev.to/sahil_ranpariya/building-uptime-monitoring-1o3e</link>
      <guid>https://dev.to/sahil_ranpariya/building-uptime-monitoring-1o3e</guid>
      <description>&lt;h1&gt;
  
  
  Introduction to Uptime Monitoring
&lt;/h1&gt;

&lt;p&gt;I built SitePulse to help freelancers and small agencies monitor their clients' websites. One of the main challenges they face is ensuring their clients' sites are always available. This can be a daunting task, especially when dealing with multiple sites.&lt;/p&gt;

&lt;h1&gt;
  
  
  Handling Uptime Checks
&lt;/h1&gt;

&lt;p&gt;SitePulse checks for uptime by sending requests to the site and expecting an answer within 10 seconds. If the site doesn't respond or returns an error status twice in a row, and checks from both Europe and Asia can't reach it, the site is considered down. However, if either region can still reach the site, no alert is sent. I also implemented 'page must contain' checks, which allow users to specify text that must be present on the page for it to be considered up.&lt;/p&gt;

&lt;h1&gt;
  
  
  Trade-offs and Limits
&lt;/h1&gt;

&lt;p&gt;When building SitePulse, I had to make some trade-offs. For example, I chose not to implement SSL certificate expiry checks or SMS/phone-call alerts. I also had to limit the free plan to 5 sites, checks every 5 minutes, and 7 days of history. The Pro plan, which is not yet available for upgrade, will offer more features such as domain expiry warnings, client status pages, and monthly client reports.&lt;/p&gt;

&lt;h1&gt;
  
  
  Conclusion
&lt;/h1&gt;

&lt;p&gt;Building SitePulse has been a learning experience, and I'm still working on improving it. If you're interested in trying it out, you can sign up for the free plan, which includes 5 sites, checks every 5 minutes, and 7 days of history, at &lt;a href="https://sitepulse.buymazing.in" rel="noopener noreferrer"&gt;https://sitepulse.buymazing.in&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>buildinpublic</category>
      <category>monitoring</category>
      <category>saas</category>
    </item>
  </channel>
</rss>
