DNS automation
v1.10.0
Check domain availability
Check whether a domain is still registrable. Answered from the regfish lookup service (RDAP/WHOIS against the registries), the same source that powers the domain search on regfish.de, not the account database. This endpoint deliberately works on any domain, not just the ones in the account: the whole point is to ask about domains nobody owns yet. A check that cannot be completed (registry unreachable, timeout) returns
502 rather than reporting the domain as taken, guessing here would cost the customer a registration. Rate limit: 60 checks per minute and API key, and 120 checks per minute and account. The account limit applies across all of your API keys and OAuth clients, so issuing another credential does not raise it.GET
/domains/availability/{domain}
Domains
Authentication
Parameters
Name
Type
Format
Required
Description
domain
string
-
Required
A domain name to check. Unlike `fqdn_relaxed` this also accepts internationalised names (e.g. `müller-shop.de`); they are converted to punycode and validated against the public suffix list server-side.
Request example
GET
curl --request GET \
--url 'https://api.regfish.com/domains/availability/example.de' \
--header 'x-api-key: YOUR_API_KEY'Responses
200
Availability result
Response example 200
{
"success": true,
"code": 0,
"response": {
"domain": "example",
"sld": "example",
"tld": "example",
"available": true,
"status": "available",
"flags": [
"example"
]
}
}400
Not a valid registrable domain name
Response example 400
{
"success": false,
"message": "Not a valid registrable domain name",
"error": "Not a valid registrable domain name"
}401
Unauthorized
Response example 401
{
"success": false,
"message": "Unauthorized",
"error": "Unauthorized"
}429
Too many availability checks
Response example 429
{
"success": false,
"message": "Too many availability checks",
"error": "Too many availability checks"
}500
Unexpected error
Response example 500
{
"success": false,
"message": "Unexpected error",
"error": "Unexpected error"
}502
Availability could not be determined
Response example 502
{
"success": false,
"message": "Availability could not be determined",
"error": "Availability could not be determined"
}Community
Devenez membre de la communauté
L'API DNS regfish est une excellente solution pour les développeurs qui souhaitent automatiser les domaines et les zones DNS. Faites partie de la communauté et bénéficiez de l'automatisation DNS. L'API DNS est disponible gratuitement pour chaque client regfish.