Custom TLDs & CSV Export in Domain Checker

Domain Checker's default TLD set covers the common cases, but naming rarely stays common. Custom TLD injection lets you add any niche or country-code extension on demand, and CSV export turns the surviving shortlist into a file you can hand to a client, a co-founder, or whoever owns the registrar account.

Adding TLDs beyond the defaults

The out-of-the-box picker covers .com, .net, .io, .ai, .co, .xyz and more. When a project needs something the defaults do not list — a regional launch on a country-code TLD, an industry extension, a vanity ending — add it through custom TLD injection and it joins the matrix like any other column. From that point every keyword on your list is checked against it in the same pass as everything else.

This matters most for three cases. Regional targeting: SEO teams building country-specific sites need ccTLD coverage, and a scan that includes the local extension alongside .com shows immediately where full coverage is possible. Industry extensions: some niches have a de facto standard ending that no general default list would include. Brand protection: once a winner is chosen, a quick scan of that single stem across a wide extension set shows what a competitor could register next to you.

Because lookups are routed to the official RDAP provider for each extension, coverage follows the registries rather than a hard-coded list — an injected TLD gets the same registry-truth answers as a default one.

Filtering before you export

Most of any bulk scan is noise; the good .com went a decade ago. The available-only toggle collapses the grid to domains that are actually unregistered, which is the difference between a wall of red and a shortlist you can reason about. Filter first, then export — the file should contain decisions, not data.

Exporting to CSV

Export writes the results — filtered or complete — as a CSV that opens in any spreadsheet. Naming decisions almost always involve someone who was not in the browser with you, and a file beats a screenshot: it can be sorted, scored, annotated, and attached to the email where the decision actually happens. Domain investors feed the CSV into their own scoring models; agencies attach it to the naming deck so every candidate is pre-verified.

The export lands in your regular downloads folder. Like everything else in the extension, it is produced locally — your candidate list never passes through a Degird server on its way to the file.

Next steps

• The full bulk scanning workflow
• Installation and first scan