Bulk domain extension coverage checker
Paste or import a list of domains to see where each exact name appears across domain extensions. Compare the summary counts, then expand a result to see its TLD lists. 1 credit per successful domain check.
- 01 Enter your API key, or sign in to use your account key.
- 02 Add domains, one per line, or import a TXT or CSV file.
- 03 Leave extensions blank for all published datasets, or choose a fixed selection.
- 04 Run the batch. Expand rows to inspect the returned TLD lists without another request.
Extension coverage results
Expand a successful row to see Taken / unavailable, Not found / check availability and any unknown extensions. The details use the same response and no extra credits.
Requests use the key you enter. Sign in to keep your account key on our server.
Compare exact-name presence across extensions
Extension coverage adds another data point to domain research: how often the same name appears in published registry datasets. Start with several candidates, compare their summaries and open the lists for the names that interest you.
Presence across extensions does not establish a name's value, ownership or suitability. Use the same extension selection when comparing domains, and read the counts alongside the percentage. The extension coverage guide explains the underlying data.
What the result columns mean
- Domain and Name
- Domain is the normalized domain returned by the API. Name is the exact label checked across extensions. For example, www.example.co.uk is reduced to example.co.uk and checks the name example. The tool does not search variations, synonyms or similar spellings.
- Checked, Taken and Not found
- Checked is the number of extensions with usable data. Taken counts matches in that data; Not found counts checked extensions without a match. These two counts add up to Checked. Expand the row to inspect both lists. Not found requires a registrar check before you treat a domain as available.
- Unknown and Status
- Unknown counts explicitly selected extensions without usable data; they were not checked. Status identifies successful results, partial coverage, freshness warnings or request errors. Older registry data can still produce a successful result, so retain any warning when reviewing the list.
- Percentage taken
- Taken divided by Checked, multiplied by 100. Unknown extensions are excluded. If 12 extensions are taken, 3 are not found and 5 are unknown, the result is 80%: 12 out of 15 checked. A high percentage across a small selection is different from the same percentage across hundreds of extensions.
- Credits used
- A successful domain request costs 1 credit total, including partial coverage. Failed API requests and requests with no usable datasets are not charged. Opening a row and exporting returned data make no additional API request. See credit packs and lookup pricing before starting a large batch.
A practical comparison workflow
Import your candidate domains and choose a consistent extension set, or leave the selection blank to use all published datasets.
Sort the summaries, compare Checked alongside % taken, and expand the rows you want to investigate. Check any unknown or older-data warnings.
Confirm current availability with a registrar. For broader research, use the bulk domain metrics checker and backlink checker before making a decision.
Extension coverage questions
Can I check several domains at once?
Yes. Paste one domain per line or import a TXT or CSV file. The tool sends a separate request for each unique domain and adds the results to one table. The optional extension selection applies to the whole batch. Keep the tab open until the batch finishes.
Does not found mean a domain is available to register?
No. Not found means the exact name was absent from the checked registry data. A registered domain without DNS delegation can be missing from a zone file. Check current availability with a registrar before registering or making a purchase decision.
What does each successful check cost?
Each successful domain request costs 1 credit total, including partial coverage or older data. Failed API requests and requests with no usable coverage are not charged. Expanding a result and exporting the table use the response already returned and cost no extra credits. Running the check again is a new request.
Which extensions are included?
Leave the extension field empty to check all published datasets. To compare a fixed selection, enter extensions such as com, net, org and co.uk. Extensions in your selection without a usable dataset appear as unknown and are excluded from the percentage taken. Results use registry snapshots, rather than a live registrar check.
Building your own workflow? Read the extension coverage API reference for request options, response fields and error handling.