# Get Specific TLD Requirements

Returns the registration requirements some general information for a specific TLD. The response contains a detailed description of eligibility criteria and a fields object with all required and optional fields, including validation rules, conditional logic, and nested field structures. Provide the TLD as a path parameter to retrieve its complete registration requirements. Useful when you only need details for one TLD (e.g., when a user selects .fr from a dropdown).

Endpoint: GET /core/v1/domaininfo/requirements/{tld}
Version: 1.8.2
Security: BasicAuth

## Path parameters:

  - `tld` (string, required)
    TLD indicates which domain requirements to retrieve (without the dot prefix, e.g., 'fr' for .fr domains). For punycode TLDs, use the ASCII version instead of the UTF-8. So for the онлайн TLD, you would submit xn--80asehdb.
    Example: "fr"

## Response 200 fields (application/json):

  - `tldInfo` (object, required)
    General information about a specific TLD. These are not registration requirements, but contain useful information for domain reseller and domain registrants in general.

  - `tldInfo.tld` (string, required)
    The TLD this information relates to.
    Example: ".fr"

  - `tldInfo.ccTld` (boolean, required)
    Whether the TLD is a Country Code TLD.
    Example: true

  - `tldInfo.supportsTransferLock` (boolean, required)
    Whether the TLD supports implementing a Transfer Lock.
    Example: true

  - `tldInfo.supportsDnssec` (boolean, required)
    Whether the TLD supports DNSSEC.
    Example: true

  - `tldInfo.supportsPremium` (boolean, required)
    Whether there are premium domains for this TLD.
    Example: true

  - `tldInfo.supportsPrivacy` (boolean, required)
    Whether the TLD supports WHOIS Privacy.
    Example: true

  - `tldInfo.requiresPreDelegation` (boolean, required)
    Whether this TLD requires pre-delegation. If this is true, these domains must be added to the name servers before the domain creation is completed.
    Example: true

  - `tldInfo.expirationGracePeriod` (number, required)
    The number of days you have to renew your domain after it has expired, but before it is removed from your account.
    Example: 25

  - `tldInfo.allowedRegistrationYears` (array, required)
    The years that a domain is allowed to be registered for.
    Example: [1,3,5,8,10]

  - `tldInfo.idnLanguages` (object, required)
    The IND Languages that the TLD supports (if any).
    Example: {"DE":"German","DK":"Danish","ES":"Spanish","IT":"Italian","JP":"Japanese"}

  - `tldInfo.hsts` (boolean, required)
    The entire TLD namespace has been added to the HSTS Preload list. As such, all second-level domains under .TLD will only load on modern browsers if a valid SSL certificate has been configured and the webserver is serving HTTPS.
    Example: true

  - `tldInfo.minDomainLength` (number, required)
    The minimum allowed length for the second level domain (SLD) for a given TLD. The SLD would be the example part of example.com. Attempts to register a domain with a shorter length than allowed will result in a failure of a Create Domain request.
    Example: 3

  - `tldInfo.minIdnDomainLength` (number,null, required)
    The minimum allowed length for the second level domain (SLD) that utilizes an IDN character for a given TLD.  The SLD would be the èxample part of èxample.com. Attempts to register a domain with a shorter length than allowed will result in a failure of a Create Domain request. This value will often be different from the minDomainLength for non-IDN registrations.  This parameter will return as null for any TLDs that do not support IDN registrations.
    Example: 5

  - `requirements` (object, required)
    The registration requirements for this TLD, including required fields, validation rules, and conditional logic. This field will always be present but may be an empty object when no specific requirements exist for the TLD.

  - `requirements.description` (string)
    A detailed description of the registration requirements for this TLD, including eligibility criteria, restrictions, and important notes.
    Example: "Required fields to register an .fr domain"

  - `requirements.fields` (object)
    An object containing all required and optional fields for domain registration, with their validation rules and conditional logic.

## Response 404 fields (application/json):

  - `message` (string, required)
    A human-readable message providing more details about the error
    Example: "Not Found"

  - `details` (string,null)
    Additional context or information about the error
    Example: "The requested domain does not exist."

## Response 429 fields (application/json):

  - `message` (string)
    A human-readable message providing more details about the error
    Example: "Rate Limit Exceeded"