Offered free of charge as part of our research tools.
Newly Registered Domains
A daily list of newly registered domains, covering 1,758 effective TLDs.
Free, API-ready in text, JSON and gzip, no signup.
Daily history. Thirty days shown, ninety days kept.
Three formats. Readable, structured, compact.
One domain per line.
Lowercase, deduplicated, LF endings, UTF-8 with IDNs in punycode. Views directly in the browser and pipes cleanly into anything.
Illustrated with reserved example domains.
example.com example.net example.org xn--exampl-gva.example new-domain.example
The same domains, with metadata.
An object with date, count, generated_at, and a domains array of strings. Aggregates carry from and to instead of date.
Illustrated with reserved example domains.
{
"date": "2026-10-27",
"count": 353289,
"generated_at": "2026-10-27T08:39:46Z",
"domains": [
"example.com",
"example.net",
"example.org",
...
]
}
A third of the size.
The plain-text list, gzip-compressed. Decompresses to the exact .txt content, ideal for pipelines that download the larger windows on a schedule or keep files compressed at rest.
$ curl -s https://smet.cz/nrd/data/today.txt.gz \
| gunzip | head -n 3
example.com
example.net
example.org
Every URL is the API. Nothing separate to integrate.
Every file on this page is a plain HTTPS GET: no key, no signup, no session. The same holds for curl, wget, Python, PowerShell, or any pipeline tool that can fetch a URL.
Endpoints
/nrd/data/{today,7d,30d}.txt
/nrd/data/daily/YYYY-MM-DD.txt
Aggregates always cover the current day, the last 7 days and the last 30 days. Daily files are dated in UTC and kept for 90 days; a day's file grows until the day closes, then never changes. Swap the extension to .json or .txt.gz.
Discovery via manifest
/nrd/data/manifest.json
A generation timestamp, the three aggregates with counts and date ranges, and a days array listing every downloadable daily file. Enumerate from the manifest instead of guessing dates. Each day entry lists its date, domain count and available formats.
Compression
Accept-Encoding: zstd, br, gzip
The edge negotiates compression on every response and the transfer shrinks to roughly a third, with nothing to change on your side. Prefer compressed files at rest? Fetch the .txt.gz variant directly. Browsers and most HTTP libraries decode it automatically.
Built for production. Performance, resilience, compliance.
These endpoints are engineered to be depended on. A firewall in Singapore, a SOC in Frankfurt, and a pipeline in Virginia all read the same file at local-network speed.
Fast in every region
95% of requests complete in under 50 ms, answered from edge locations in every region of the world. Poll as often as your pipeline needs.
Global resilience
Anycast routing and instant failover keep requests flowing during incidents. No single point of failure between you and the data.
GDPR by design
Domain names only, no registrant or contact details. Published files are deleted after 90 days, and any entry is removed on request.
How this works
Every published file is distributed through a tiered global cache, so requests are answered from edge storage close to you rather than from a single origin server. If an update can't complete, the previous complete file serves until the next one lands, so a URL never returns an error or a partial file.
Usage tips
Fetching historical files? Space requests a couple of seconds apart. Take dates from the manifest and fetch each closed day only once, since it never changes. In your User-Agent, add what you use the feed for next to the client name. It is optional and helps us improve the service.
Methodology. Coverage and how to read the data.
This list is built for the broadest coverage practically achievable. Because of how registration data is licensed and published across the industry, no provider can claim a fully complete picture, since some zones simply don't make their data available. Within those constraints, our goal is to capture as much of each day's registrations as possible.
Entries are deduplicated, normalized to lowercase punycode, and dated by first appearance in our collection. For zones without public registration data, first appearance can trail actual registration by a short interval, and newly transferred or reactivated domains may appear alongside brand-new ones. The list is best understood as "domains that just became visible to the internet," which for security, brand-protection, and research use is usually the more useful definition anyway.
Today's list is updated throughout the day as new registrations are collected, so today.txt and the current daily file keep growing until the day closes.
Free to use, with attribution.
The data is published under CC BY 4.0: free for commercial and non-commercial use, under one condition, visible attribution to smet.cz. Redistribution is permitted with that attribution carried along.