Are these ordinary internet domains?
Yes. The catalog describes domains in the IANA-rooted internet namespace. They use standard DNS. It does not present alternate-root names as ordinary internet domains.
Who owns the domain, and where does it go?
The end user supplies the actual registry registrant information; the paying wallet is not a substitute. easyDNS provisions the registration and creates or selects a customer account for delivery. Track registration and account handoff separately. Normal easyDNS welcome communications accompany provisioning.
What should I approve before my agent spends?
Review the complete domain, current total, quoted term, renewal method, registrant contacts and any registry-specific requirements. Agree to the current terms before preparing the order. Your agent should obtain your spending approval before payment.
Where are the registration and renewal prices?
Get the current registration total and term from the requirements endpoint for the full domain. Lookup payments are separate. Static pages do not publish evergreen prices or assume renewal prices match registration prices. Check the renewal invoice or account for the current renewal amount.
Does a listed extension mean any name can be registered?
No. A full name must be available and return a valid offer. Eligibility rules and registry-specific fields may apply. Premium names are disabled in the recorded policy. The storefront includes only .ai, .io and .to as ccTLD exceptions. Read the live requirements and provide accurate details.
Does my agent need access to my inbox?
Follow the current requirements response. In SMTP mode, recipient acceptance is checked during preparation without sending an email; this does not prove mailbox ownership or guarantee delivery. Code mode requires an authorized verification step. Registrar contact verification remains separate: a new registrant contact must also confirm the separate email after registration. See contact-verification guidance and an example.
What if the payment succeeded but the result is pending?
Poll the original private status URL with the original bearer order token. A 202 or uncertain result does not prove failure. Do not create or pay for another order to recover the first. Registration can be confirmed while customer account delivery is still pending.
What must I save to recover access?
After settled payment and confirmed registration, durably save the returned recovery key with the domain, order ID and payment receipt. Make it retrievable independently of the registrant email. Treat it as an access secret: never put it in public URLs, logs or shared transcripts. If the response was lost, use the original authenticated status URL to retrieve the same key. Contact easyDNS privately for recovery; do not purchase again.
How do renewals work?
Renew through the easyDNS customer account before expiry. Automated recurring x402 renewal is planned, not available in this release. Review the renewal amount and your account’s billing/renewal settings; do not assume a wallet will renew the domain automatically. Follow the current easyDNS renewal instructions or sign in to your account.
What happens if a domain expires?
Expiry and recovery timelines depend on the TLD and registry; fees may apply. Check the account’s actual expiry date and renew in advance. The current easyDNS terms describe the applicable expiration and refund policies.
Can a completed domain registration be refunded?
Processed domain registrations are generally non-refundable under the current easyDNS terms. Ask easyDNS support about a specific order. An uncertain API response must be reconciled before assuming a purchase failed or a refund is due.
Can an agent manage DNS after registration?
Yes, through the customer account’s authorized easyDNS access. Start with the API-access guide and the official easyDNS MCP project. Keep credentials private and enable only the access needed for the task.
Do Markdown, JSON or llms.txt guarantee agent discovery?
No. They provide convenient, consistent references. The published skill and API documentation define the executable flow. This site does not assert new DNS discovery records or undocumented protocol paths.
Confirm your registrant contact email
If this is a new or unverified registrant contact for a generic TLD, you will also receive a separate contact-verification email as part of ICANN’s Whois Accuracy Program. You must follow the individual link in that email and confirm your contact information by the deadline shown.
The confirmation page is hosted at https://approve.domainadmin.com. Use the link in your actual email to reach your verification page. Failure to complete verification can result in domain suspension.
This confirmation is separate from the email check during order preparation and from easyDNS welcome or account-delivery emails. Successful payment, registration or account delivery does not confirm that this step is complete. Contacts already verified may not need another check; ccTLD requirements can differ.
