Extension coverage API
See which extensions are taken for the same domain name. Check all published TLDs in one request, with summary counts, percentage taken and optional TLD lists.
What you get
Send seosoftwarereviews directly, or seosoftwarereviews.info, to check the same name across all published extensions.
The default response contains counts, percentage taken and the credit cost, keeping it small even
when hundreds of TLDs are checked. Newly imported datasets join the default check automatically.
A name without an extension is one valid domain label: letters, digits and internal hyphens, up to 63 ASCII/punycode bytes. International names use IDN conversion where supported. For a bare name, both domain and name in the response contain the normalized label; no extension is invented.
Use this as an additional data point when researching a domain. A name appearing across several extensions can indicate interest, but does not establish its market value.
Authentication
Use HTTPS and send your account key in the apikey header or query parameter.
Include app to identify your integration. The endpoint uses your existing DomDetailer credit balance.
Keep your key on your server, outside browser code and public repositories.
curl.exe -H "apikey: YOUR_KEY" "https://domdetailer.com/api2/checkExtensions.php?app=YourApp&domain=seosoftwarereviews"
Extension coverage
1 creditCheck the same exact name across all published extensions by default. Get counts and percentage taken, with optional taken and not_found lists. Not found does not mean available to register. Each successful request costs one credit total; requests with no usable data are not charged.
GET https://domdetailer.com/api2/checkExtensions.php?apikey=YOUR_KEY&app=YourApp&domain=example.com
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
apikey |
string | Required | Your account API key. May also be sent as an apikey header. |
app |
string | Required | A short identifier for your integration. |
domain |
string | Required | An exact name without an extension, a full domain or an HTTP(S) URL. seosoftwarereviews and seosoftwarereviews.info both check seosoftwarereviews. Names allow letters, digits and internal hyphens, up to 63 ASCII/punycode bytes. Subdomains are reduced using the Public Suffix List: www.example.co.uk checks example. Hosted tenant names such as user.blogspot.com are rejected. Use ASCII punycode for portable IDN input. |
suffixes |
string | Optional | Optional comma-separated selection, up to 5000 entries; duplicates are removed. Omit to check all published extension datasets automatically, including newly imported extensions. Explicitly requested extensions without data count as unknown. Long selections may exceed your HTTP server URL limit. |
include_taken |
boolean | Optional | Set to 1 to include the taken TLD list. Default 0 omits it. Does not change which extensions are checked. |
include_not_found |
boolean | Optional | Set to 1 to include the not_found TLD list. Default 0 omits it. Does not change the counts or credit cost. |
Response fields
| Field | Type | Meaning |
|---|---|---|
domain |
string | Normalized registry-level domain, or the normalized name when no extension was supplied. |
name |
string | Exact ASCII/punycode label checked across extensions. |
taken |
array | Only returned with include_taken=1. Extensions where the name was found, without leading dots. Based on registry data, not a live registrar check. |
not_found |
array | Only returned with include_not_found=1. Extensions checked where the name was absent. This does not guarantee availability to register. |
unknown |
array | Only returned when explicitly requested extensions have no data, listing those unchecked extensions. |
meta |
object | Always returned: counts, percentage taken and credit cost, independent of list options. |
warnings |
array | Optional. Only returned when a result needs qualification, such as older data. Omitted for fresh results. |
| Field | Type | Meaning |
|---|---|---|
checked |
integer | Number of extensions actually checked: taken plus not_found. Excludes unknown extensions. |
taken |
integer | Number of checked extensions where the name was found, whether or not the list was requested. |
not_found |
integer | Number of checked extensions without a match. Not a count of domains available to register. |
unknown |
integer | Number of explicitly requested extensions without data. Zero when checking all published datasets. |
percentage_taken |
number | Percentage of checked extensions that are taken: taken / checked * 100, rounded to two decimal places. Excludes unknown extensions. |
credits_used |
integer | Always 1 on a successful response, including partial coverage. |
| Field | Type | Meaning |
|---|---|---|
code |
string | stale_data means the listed results use older data while an update is pending. |
count |
integer | Number of checked extensions using older data. The warning stays compact even across hundreds of datasets. |
Read the coverage interpretation guide for unchecked extensions, freshness warnings and the limits of registration inference. The example below is illustrative, not a live report of available datasets.
Example response
{
"domain": "example.com",
"name": "example",
"meta": {
"checked": 400,
"taken": 120,
"not_found": 280,
"unknown": 0,
"percentage_taken": 30,
"credits_used": 1
}
}
Code
curl -G https://domdetailer.com/api2/checkExtensions.php \ --data-urlencode "apikey=YOUR_KEY" \ --data-urlencode "app=YourApp" \ --data-urlencode "domain=example.com"
import requests r = requests.get( "https://domdetailer.com/api2/checkExtensions.php", params={ "apikey": "YOUR_KEY", "app": "YourApp", "domain": "example.com", }, timeout=60, ) r.raise_for_status() data = r.json()
const url = new URL("https://domdetailer.com/api2/checkExtensions.php"); Object.entries({ apikey: "YOUR_KEY", app: "YourApp", domain: "example.com", }).forEach(([k, v]) => url.searchParams.set(k, v)); const res = await fetch(url); if (!res.ok) throw new Error(`HTTP ${res.status}`); const data = await res.json();
$qs = http_build_query([
'apikey' => 'YOUR_KEY',
'app' => 'YourApp',
'domain' => 'example.com',
]);
$json = file_get_contents(
'https://domdetailer.com/api2/checkExtensions.php?' . $qs
);
$data = json_decode($json, true);
Reading results
| Count in meta | Meaning |
|---|---|
taken | The name appears in our registry data for these extensions. |
not_found | These extensions were checked, but the name was absent from the data. |
unknown | No usable published dataset is available for these extensions. They were not checked. |
Set include_taken=1 to return the taken list, or
include_not_found=1 to return the not_found list. Both default to
0 and work independently. These flags do not change the counts or the extensions checked.
Requested lists remain arrays even when empty. Extensions have no leading dot; compound suffixes
such as co.uk remain intact. An unknown list is returned only when an explicit
selection includes extensions without data. domain is the normalized domain and
name is the label checked.
For all published TLDs plus the taken list, append &include_taken=1 to the quick-start URL.
To restrict the check and return both lists, append
&suffixes=com,net,org&include_taken=1&include_not_found=1.
Percentage taken
meta.percentage_taken = meta.taken / meta.checked × 100, rounded to two decimal places.
If you request 20 extensions and 12 are taken, 3 are not found and 5 are unknown, the result is 80%: 12 out of 15 checked. Unknown extensions are excluded.
The value is a JSON number, without a percent sign. Read it alongside meta.checked:
100% across two checked extensions represents less coverage than 100% across twenty.
Use the same extension selection when comparing domains.
Coverage & freshness
Omit suffixes to check all published datasets. Approvals awaiting their first import
are not included. To compare a fixed selection, pass comma-separated suffixes.
The endpoint accepts up to 5,000 entries, subject to your HTTP server's URL length limit.
Explicitly requested extensions without data count as meta.unknown and are not checked.
Supported datasets are scheduled to refresh daily. Results reflect registry data snapshots, rather than a live registrar check. Routine snapshot details are omitted from the response.
If older data is used, an optional warnings field counts the affected extensions.
It is omitted when all checked data is fresh. The warning below is illustrative:
"warnings": [{"code": "stale_data", "count": 1}]
Refresh cached results daily and retain any freshness warnings. New coverage becomes queryable once its first dataset is published.
Billing & errors
A successful request costs one credit total, including partial coverage or older data.
If no requested extensions can be checked, the endpoint returns 503 coverage_unavailable
without charging. Failed requests are not charged.
| Status | What to do |
|---|---|
| 400 | Check app and domain, the suffix selection (up to 5000 entries), and that list options are 0 or 1. |
| 401 | Provide your API key. |
| 402 | Add credits to your account. |
| 404 | Check that the supplied credentials identify an account. |
| 405 | Use GET for data requests. |
| 429 | Slow down and respect the returned retry guidance. |
| 500 | A server error occurred. Retry later; contact support if it persists. |
| 502 | The coverage query failed. Retry after a short pause. |
| 503 | Coverage is unavailable or none of the requested datasets is published. Retry later or choose other extensions. |
Start at 25,000 lookups for $34.
One balance covers the browser tools, the desktop app and the API. Nothing renews, nothing expires, and you can stop using it for six months without losing anything.