What are the domain's extended attributes?

Some domain extensions ask for additional registration information beyond standard name, email and address fields. In a registrar checkout or API these fields may be called extended attributes or TLD-specific parameters.

Why are they required?

Registry rules differ by extension. Depending on the TLD, an applicant may be asked for a registrant type, country/city connection, organization identifier, local address, purpose of use, trademark/licensing declaration or consent to special policies.

For example, a .NYC application involves a connection to New York City under that registry's rules, while .CA uses CIRA's Canadian Presence Requirements. Do not fill a field with invented details simply to make a form accept the order.

Where to enter the information

Choose the exact domain and extension in NiceNIC's registration flow.
Review any displayed eligibility or document instructions before payment.
Use the registration checkout or supported API operation that exposes the TLD-specific fields; if required fields are missing, ask NiceNIC Support for the correct submission flow.
Enter truthful values that match the registrant's actual eligibility and supporting documents.
Complete the order and monitor whether the registry accepts it, requests additional evidence or places it under manual review.

If the order is rejected

Record the extension, field name, non-sensitive error and order number. Confirm the valid choice set against the current registry policy; do not assume another TLD's attribute codes are transferable. Reseller API integrations may require separate field names or enumerated values documented for that extension.

Extended attributes affect registration eligibility, not necessarily WHOIS visibility or DNS configuration. For a particular extension, see the relevant TLD requirements article or ask NiceNIC Support for the current attribute list.

Examples of extended attributes

"Extended attributes" are extra registration fields required by some TLDs in addition to ordinary name, address and email contact information. Depending on the registry, a registration may ask for:

an individual/organization registrant classification;

a country-specific identity or company-registration identifier;

a local presence or address proof;
a purpose or eligibility statement;
additional administrative contacts or a supported local service arrangement.

Illustrative scenario: A small company can successfully register a typical .COM with ordinary accurate contact details, but when attempting a restricted local-domain category it may be asked for company evidence matching the registrant's legal name. That is not a DNS error and cannot be repaired by modifying nameservers or trying a different password.

What to do if the panel requests a value you do not have

Stop and read the extension-specific requirements. Don't enter random text, a borrowed identifier, or a fictitious address just to pass validation. Check whether the registrar offers an authorized trustee or local-presence service for that exact extension, and whether the registry allows it. If documents are required, match the exact entity name and jurisdiction across the order and the documents.

A domain may appear "paid" but remain pending review until these attributes are accepted. Save the order number and any registry rejection text so support can identify the missing field.