Feeds · updated throughout the day

Newly Registered Domains

A daily list of newly registered domains, covering 1,799 effective TLDs. Free, API-ready in plain text, JSON and gzip, no signup.

384,513 domains today · 2026-09-09
TXTJSONGZIP
2,905,999 last 7 days
TXTJSONGZIP
11,518,320 last 30 days
TXTJSONGZIP

Sample

file formats, illustrated

What the feed looks like. The shape of the plain-text list and the head of the JSON, illustrated with reserved example domains, so you can see the format before downloading.

today.txt
example.com
example.net
example.org
xn--exampl-gva.example
new-domain.example
today.json
{
  "date": "2026-09-09",
  "count": 384513,
  "generated_at": "2026-09-09T08:30:51Z",
  "domains": [
    "example.com",
    "example.net",
    "example.org",
    ...
  ]
}

Daily history

latest 15 days shown · files kept 90 days

Every day is published as a standalone file the moment aggregation completes, and stays available for 90 days. The table lists the latest 15 days; older files remain downloadable at the same URL pattern and are listed in the manifest. Plain text opens directly in the browser; JSON carries the same domains with metadata; GZIP is the plain-text list compressed.

DateDomainsDownload
2026-09-09384,513TXT JSON GZIP
2026-09-08403,304TXT JSON GZIP
2026-09-07310,366TXT JSON GZIP
2026-09-06325,127TXT JSON GZIP
2026-09-05647,128TXT JSON GZIP
2026-09-04427,215TXT JSON GZIP
2026-09-03408,346TXT JSON GZIP
2026-09-02351,634TXT JSON GZIP
2026-09-01351,551TXT JSON GZIP
2026-08-31257,753TXT JSON GZIP
2026-08-30266,611TXT JSON GZIP
2026-08-29351,841TXT JSON GZIP
2026-08-28353,865TXT JSON GZIP
2026-08-27340,224TXT JSON GZIP
2026-08-26398,635TXT JSON GZIP

Formats

stable paths, stable schemas

Plain text .txt

One domain per line, lowercase, deduplicated, LF endings, UTF-8 with IDNs in punycode. Views directly in the browser and pipes cleanly into anything.

JSON .json

Object with date, count, generated_at, and a domains array of strings. Aggregates carry from and to instead of date.

GZIP .txt.gz

The plain-text list, gzip-compressed to roughly a third of the size. Decompresses to the exact .txt content - ideal for pipelines that download the larger windows on a schedule or keep files compressed at rest.

Stable URLs

Aggregates live at /nrd/data/today.txt, /nrd/data/7d.txt, /nrd/data/30d.txt (same for .json and .txt.gz). Daily files at /nrd/data/daily/YYYY-MM-DD.txt. A machine-readable index sits at /nrd/data/manifest.json.

API access

every URL is the API

There is no separate API to integrate - the feed itself is the API. Every file on this page is a plain HTTPS GET: no key, no signup, no session. curl https://smet.cz/nrd/data/today.txt is a complete integration, and the same holds for wget, Python, PowerShell, or any pipeline tool that can fetch a URL.

Aggregate endpoints

/nrd/data/today.txt, /nrd/data/7d.txt, and /nrd/data/30d.txt always hold the current day, the last 7 days, and the last 30 days. Swap the extension for .json or .txt.gz to switch format. The paths never change - point a scheduled job at them once and it keeps working.

Daily endpoints

Each day lives at /nrd/data/daily/YYYY-MM-DD.txt (also .json and .txt.gz), dated in UTC, and stays downloadable for 90 days. The current day's file grows as registrations are collected, then never changes again once the day closes.

Discovery via manifest

/nrd/data/manifest.json is the machine-readable index: a generation timestamp, the three aggregates with counts and date ranges, and a days array listing every downloadable daily file with its date and count. Enumerate from the manifest instead of guessing dates.

Compression

The edge negotiates compression on every response: request with Accept-Encoding: zstd, br, or gzip 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.

Built for production

performance, resilience, compliance

These endpoints are engineered to be depended on. The feed is delivered from a global edge network, so a firewall in Singapore, a SOC in Frankfurt, and a pipeline in Virginia all read the same file at local-network speed.

<50 ms

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.

Anycast

Global resilience

Anycast routing and instant failover keep requests flowing during incidents - no single point of failure between you and the data.

90 days

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.

Built for Threat hunting Phishing detection Brand protection Typosquatting monitoring DNS blocklists Threat intel enrichment Fraud prevention SEO & market research Academic research

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. Files update throughout the day and reach the edge within moments of each publish; in the rare case 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. Because the current dataset lives on the edge network itself, delivery is decoupled from origin availability.

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.

Using this data in a product, feed, or research? This feed 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. Full terms on the legal page. Questions: [email protected].