Check Transfer Eligibility
Returns whether a domain is currently registered at name.com and whether the TLD supports internal transfer between name.com accounts. Use this to decide whether to send your user through the Create Transfer external transfer flow or the Create Internal Transfer In flow before initiating a transfer-in.
Response semantics
atName is true if the domain is currently registered at name.com in any account. This information is also publicly available via RDAP.
supportsInternalTransfer mirrors the TLD-level value returned by Tld Requirements. It indicates whether the TLD is eligible for internal transfer between name.com accounts. It does not reflect per-account allowlist eligibility — if your account is not allowlisted for internal transfer in, calling Create Internal Transfer In will return 403 Forbidden.
Privacy
This endpoint never reveals which account a domain is in. To check whether a domain is in your own account, use Get Domain instead.
Authorizations
Authenticate via HTTP Basic with your account username and API token. Examples use an explicit 'Authorization: Basic <base64(username:token)>' header; 'curl -u username:token' is equivalent. For sandbox, append "-test" to your username and use your sandbox token on api.dev.name.com.
Path Parameters
The domain to check transfer eligibility for. Punycode is normalized server-side, so either ASCII or UTF-8 is accepted.
Response
A successful response.
Result of a transfer eligibility check. Indicates whether the domain is currently registered at name.com (in any account) and whether the TLD supports internal transfer between name.com accounts.
The domain that was checked, in its canonical (ASCII / punycode) form.
"example.com"
Whether the domain is currently registered at name.com (in any account).
true
Whether the TLD supports internal transfer between name.com accounts. Mirrors the TLD-level flag returned by Get Tld Requirements. Does not reflect per-account allowlist eligibility for the internal transfer-in API.
true