<!-- DRAFT (prompt 41300). Publish only after the JSON buttons from docs/Plan_JSON_See_Download_Copy_20261022.md ship; until then this describes features that don't exist yet on most pages. -->

CSV, JSON or Just the Website: Your Domain Data, Your Format

Most domain tools give you one way to see your results: their screen. If you want the list somewhere else, you copy and paste.

DNSLister works the other way around. Anything you find here, whether it's a search, your Favorites, a word list or TLD data, comes in three formats:

1. The website (GUI). Sort it, filter it, score it, click through to RDAP.
2. CSV. Open it in Excel, Google Sheets or Numbers.
3. JSON. Feed it to a script, a database or an AI assistant.

The data is the same in all three. Use whichever fits what you're doing next.

When to use which

You want to...	Use
Browse, compare and shortlist names	The website
Share a shortlist with a co-founder or client	CSV (it opens anywhere)
Sort 5,000 names by your own formula	CSV in a spreadsheet
Load results into your own database	CSV or JSON
Script a nightly check, or pipe results into another tool	JSON
Ask ChatGPT or Claude to pick from your list	JSON (paste the link or the file)

One click for each

Wherever you see an export, you get the same row of buttons:

• ⬇ CSV: downloads a spreadsheet file.
• ⬇ JSON: downloads the same data as a .json file.
• { } View JSON: opens it in a new browser tab. Firefox shows a neat collapsible tree. Chrome shows the text with a "Pretty-print" box.
• 🔗 Copy JSON URL: copies the link, on public data like TLD Health and DNS Providers. Paste it into a script, a spreadsheet's import function or an AI chat.

Files you can find again

Every download is named so a crowded Downloads folder still makes sense:

DNSLister.com_Favorites_20261022.csv
DNSLister.com_Favorites_20261022.json

It starts with where it came from, then what it is, then the date. The CSV and JSON versions of the same export share the same name.

What's in the JSON

Every JSON export has the same simple shape: a little header saying what it is and when it was made, then a list of rows. Each row has the same columns as the CSV. Numbers come through as numbers, yes/no fields as true/false, and tags as lists, so you don't have to clean anything up before you use it.

Should we add XML?

We've kept it to CSV and JSON because they cover almost everything people do with domain lists today. But some older tools, registrar bulk-import screens and enterprise systems still want XML.

Would you use XML exports? Tell us what you'd feed them into. If enough of you need it, it'll be a third button next to the other two.

---

Ready to try it? Run a search, save a few names to Favorites, and export them in whichever format you like.