DNSBuddy
Changelog

Version 2.0.0

Shipped on February 25, 2026. Questions about this release? Email hello@dnsbuddy.co.
← All releases

2.0.0

February 25, 2026

Features

Frontend

  • DNS Health With all the different activity we see, I wanted to also monitor the DNS Health of the various providers. This will be important as I scale and start to build out my own DNS Hosts in the future.
  • Domain Digger This is similar to a tool we previously offered, but a lot better. We now identify over 100 different TXT Validation Records, 30 different MX and 50 different NS (DNS Providers). We are constantly enhancing our data, and trying to provide the best results around.
  • DNS History Beta We're excited to introduce the DNS History viewer: a new beta tool for exploring the detailed DNS and nameserver change history of any monitored domain. See a Git-like timeline of all past DNS record changes and track how your domain has evolved over time.
  • Feedback just got a whole lot better Previously we made you own up a GitHub issue and provide a template, now on every page you will see a little icon to provide us feedback. This gets instantly posted to our internal discord, and we will take it from there.
  • Learning hub is here! To help drive traffic and to help educate, I thought it would be a win win to build out some resources around various things around DNS.
  • Introducing the SPF Analyzer A brand new feature that helps you analyze, parse, and visualize SPF records—including their structure, DNS lookups, and granting relationships. Built for clarity, speed, and modern best practices.
  • Subdomain Finder Tool Introducing a new Subdomain Finder tool, providing asynchronous, scalable subdomain enumeration with live job status and results via API. Now supports polling for results, robust error handling, and Redis-backed storage for improved performance.

Improvements

Frontend

  • More reliable DNS lookups We have moved away from DoH (DNS over HTTPS) to using our own backend. Which allows us to easily parse, and handle the results better.
  • Expanding WHOIS lookup to be more reliable We implemented RDAP per RFC 7482. When RDAP is not available we fall back to the TLDs WHOIS server. We try to parse it, and are looking for feedback as you come across any issues. We also provide a quick easy way to download the results.
  • Increased Bulk FCrDNS capacity Prior we had a limit of 100, now it's 256. We can always increase, but for now we thought this increase is probably a good start.

Deprecations

Frontend