Updates to DNS Coffee: new pages, new features, and changes to the API.
Aug 02, 2026
Every v1 API list is now pageable or has a documented bound, and the paging story converges on one dialect: limit plus an opaque cursor, following each response's next_cursor while has_more is true.
The nine full-day change feeds (/feeds/{domains,nameservers,ips}/{new,old,moved}/{date}) accept an optional limit and cursor, so a multi-million-row day can be read as ordered pages — each page equally fast no matter how deep. Without limit they still return the complete day in one response. /zones/{zone}/records and /feeds/search switch from offset to the same cursor dialect, and feed-search pages stay stable while a new day's feed imports mid-walk. /domains/{domain}/child-nameservers joins them: the largest parent domains have hundreds of thousands of exactly ranked children, and the whole ranking is now walkable page by page instead of capped at the first thousand.
The twelve current/archive sub-lists (a nameserver's domains, a domain's nameservers, an IP's nameservers, and their siblings) join the cursor dialect too: every page now carries next_cursor, and following it walks even the largest lists completely — including the mass-migration date blocks and the rows predating tracking that date-based paging could never split. Archive lists also accept removed_before, the removal-date counterpart of before, for windowed reads.
Endpoints that used to truncate silently now take a limit and say when they cut the list: /domains/{domain}/records and /domains/{domain}/dnssec report *_truncated flags, /zones/{zone}/soa pairs its history with the exact serial_count, and /zones/{zone}/domains, /zones/trending, and /records/stats accept adjustable limits.
Breaking: the seventeen operations that returned a bare JSON array now return an object with a named list field (nameservers, domains, ips, tlds, series) plus paging metadata — including has_more on the date-windowed sub-lists, whose before/after paging is otherwise unchanged — and the ranked "top" lists normalize their maximum limit to 1000. The API reference documents the paging parameters and response fields on every affected endpoint.
Jul 30, 2026
DNS Coffee has always indexed more than delegations, and that data is now on the site. Domain pages show every other record we have observed at the name — CNAME, TXT, MX, CAA, SRV, and the rest — alongside a new DNSSEC section listing the domain's DS records: key tags, algorithms, digests, and when the delegation was first signed. Names that exist in zone files only as records (a bare CNAME with no delegation, for example) now resolve to their own page instead of a 404 — over 200,000 previously invisible names.
Zone pages gained an SOA section (current serial, contact, and timers, with recent serial history) and a DNSSEC section showing the zone's active DNSKEYs, their algorithms and roles, and the freshness of its apex signatures. Zones carrying miscellaneous records also link to a new per-zone records browser at /zones/{zone}/records, filterable by type.
A new records overview page summarizes the whole collection: active record counts by type, the SRV service breakdown, and the zones contributing the most records. And a new DNSSEC overview page tracks signing across every zone we index: which zones are signed and since when, the algorithms they use, expired apex signatures, and a timeline of DNSSEC adoption reaching back to 2013. It also tracks signature health over time — zones serving no valid apex signature at all (the failure mode that breaks validation) are charted historically, and each zone page lists its dated signature incidents. As the per-zone rollup data accumulates, zone pages also chart how many of each zone's domains are signed over time.
The v1 API exposes all of it: /domains/{domain}/records, /domains/{domain}/dnssec, /zones/{zone}/soa, /zones/{zone}/dnssec, /zones/{zone}/records, /records/stats, /dnssec/zones, and /zones/{zone}/dnssec/history.
Jul 29, 2026
The TLDs page now shows which TLDs are growing and shrinking the fastest: two ranked tables of the 25 steepest movers in each direction, based on a fitted trend over the last 90 days of weekly average domain counts — so a single import spike doesn't crown a winner, but a zone collapsing this month shows up within weeks. Each row reports the zone's current size, its change in domains per month, and that change as a percentage of its size. The home page carries the top five of each as a teaser.
Every zone page now shows how IANA classifies that TLD — generic, country-code, sponsored, test — and which organization runs it, and the zones list gains sortable Type and Operator columns plus charts breaking down zones by type and by operator. That table has a search box that narrows it as you type, and clicking any bar in those charts filters it to that operator or type. The classification comes from IANA's root zone database, refreshed daily.
The TLD Graveyard uses it for a new chart of retirements per year, grouped by type, which separates the eras cleanly: a batch of test TLDs retired together in 2013, a couple of country-code changes, then a steady run of generic TLDs from 2016 onward. Summary tiles above it show how many TLDs have been retired, the busiest year, and the largest any of them ever grew — which turns out to be 666 domains, the clearest sign of why they were shut down.
On the API, zone type and organization appear on the zone, root, zone list, and graveyard endpoints, and the growth ranking is available at GET /api/v1/zones/trending.
Jul 28, 2026
Domain and nameserver pages now summarize the whole family of nameservers under a registered domain, not just list them. A domain that parents nameservers shows how many of them are still in use, how many have been retired, and how many domain delegations they serve between them — for a big registrar's nameserver domain that is often a handful of live nameservers carrying millions of delegations while tens of thousands sit retired. Each nameserver page also tells you where that nameserver ranks among its active siblings. The same figures are available from the API on the child-nameservers and nameserver-parent endpoints.
Jul 27, 2026
DNS Coffee has a new look, brewed from scratch: a warm light theme and a black-coffee dark theme, switchable from the toggle in the navigation bar (auto mode follows your system preference). Every page has been reworked — record pages now open with an at-a-glance header and quick-stat tiles, the big data tables (zones, nameservers, IPs, the TLD graveyard) sort by clicking their column headers, charts share one palette that reads in both themes, and the whole site is now friendlier on phones.
Jul 26, 2026
The ~1,253 nameservers above our size gate — the ones serving more than 60% of all delegations, names like registrar-servers.com and dns-parking.com — used to show "history unavailable" where their domains-over-time chart should be: reconstructing the series for a nameserver that large from every domain association took too long to do on demand.
They now have a full chart going back to April 2011, at the same weekly resolution as the internet-wide domain chart on the home page. The data updates continuously as new zones are imported.
Jul 24, 2026
The IP page now opens with a chart of how many IPv4 and IPv6 addresses have appeared in glue records over time, and a table of the addresses with the most nameservers currently resolving to them — the parking, registrar, and hosting blocks that a large share of the internet's delegations point at.
Both are also on the v1 API, as GET /api/v1/stats/ip-history and /stats/ips/top.
An address counts on a date when it was actually present, so one that stopped appearing and later returned is not counted during the gap. Addresses whose first sighting predates the collection are labelled "before tracking" rather than given a misleading date.
Jul 24, 2026
The v1 API now carries daily change feeds for glue addresses, alongside the domain and nameserver feeds it already had. GET /api/v1/feeds/ips/new/{date} lists the addresses that gained a nameserver that day, /old/{date} those that lost their last one, and /moved/{date} those whose set of nameservers churned — all split by IP version, with totals from /feeds/ips/counts/{date}.
Addresses are shared far more widely than nameservers, so a busy hosting address turns up in these feeds most days. Add first_ever=true to the new feed to see only addresses never seen in glue anywhere before — new infrastructure appearing for the first time, rather than everyday churn.
The feeds start on 2026-07-24 and are not backfilled, so earlier dates come back empty.
Jul 21, 2026
The v1 API can now return the actual domains behind the trends chart, not just the daily counts. GET /api/v1/feeds/search lists the domains in one feed (type=new, old, or moved) whose name contains a search term, newest change first — paged with limit plus a cursor and optionally narrowed to a from/to date range within the recent feed window.
Jul 20, 2026
You can now search IPs by subnet: enter CIDR notation in the search box (e.g. 205.251.192.0/18) to list every stored IP in the block — each with its seen dates and active nameserver count — on a dedicated page like /ip/205.251.192.0/18. Large subnets show a clickable density map of their child blocks to drill down, and every page links to its parent and neighboring subnets. Subnets down to /16 (IPv4) and /32 (IPv6) are supported, and the same data is available from the v1 API at /api/v1/ip/{ip}/{prefixlen} (with the density rollup at /blocks).
Jul 20, 2026
DNS Coffee now has an FAQ covering data sources, takedown requests, and how to get API access, along with this News page for tracking changes to the site and the API.
Jul 19, 2026
The current v1 API is live, built on OpenAPI 3.1 with self hosted documentation at api.dns.coffee/doc. It serves everything the older API did, plus:
The previous API version keeps working but is now deprecated. New integrations should use v1.
Jul 18, 2026
The home page now leads with live collection totals for domains, nameservers, IPv4 and IPv6 records, zones, and imports, each linking to its section. Below them are full history growth charts for the root zone and the internet as a whole, with range buttons to focus on recent activity.
Jul 18, 2026
The TLDs page has a new chart showing how many domains each TLD adds per month, with the current partial month prorated so the latest point is comparable to the rest.
Jul 17, 2026
The new Feeds page shows the domains and nameservers added and removed across all zones each day, including a truly new count that ignores names that merely reappeared. A history graph tracks the daily volume over time.
Jul 17, 2026
Nameserver pages gained a domains over time history graph and a list of related nameservers found through shared parent domains and shared IP addresses. The nameservers page now ranks the most used nameservers across the whole dataset.
Jul 16, 2026
Search now matches domains and nameservers by any substring of the name, shows exact matches at the top of the results, and produces shareable result URLs. A quick lookup path like /q/example.com jumps straight to a domain, nameserver, IP, or zone when the term matches one exactly.