.co.de
API Commands
Section titled “API Commands”Please find in the following a set of the most commonly used standard API commands in order to register, modify, renew, and transfer a domain name.
Domain Registration
Section titled “Domain Registration”(API Command reference » AddDomain)
command = AddDomaindomain = yourdomain.co.deperiod = (INT)ownercontact0 = (CONTACT)admincontact0 = (CONTACT)techcontact0 = (CONTACT)billingcontact0 = (CONTACT)nameserver0 = (NAMESERVER)nameserver1 = (NAMESERVER)Domain Modification
Section titled “Domain Modification”(API Command reference » ModifyDomain)
command = ModifyDomaindomain = yourdomain.co.deDomain Renewal
Section titled “Domain Renewal”(API Command reference » RenewDomain)
command = RenewDomaindomain = yourdomain.co.deperiod = (INT)expiration = (INT)Domain Deletion
Section titled “Domain Deletion”(API Command reference » DeleteDomain)
COMMAND = DeleteDomainDOMAIN = yourdomain.co.deDomain Transfer
Section titled “Domain Transfer”(API Command reference » TransferDomain)
command = TransferDomaindomain = yourdomain.co.deaction = REQUESTauth = (TEXT)Transfers are processed through our fulfillment team. Please sent an email with the p-handles and nameservers to [email protected] in order to get the transfer processed.
Domain Restore
Section titled “Domain Restore”(API Command reference » RestoreDomain)
command = RestoreDomaindomain = yourdomain.co.deDomain Restrictions
Section titled “Domain Restrictions”There are no restrictions for .co.de
Fulfillment Info
Section titled “Fulfillment Info”FTLD .co.de is a Fulfillment TLD. Fullfilment TLDs (FTLDs) are registered through a manual registration process. The manual registration process might involve documents, depending on respective registry regulations, and are therefore not automated for real-time registrations and real-time updates. Updates might cause additional costs!
IDN Information
Section titled “IDN Information”The German special characters “Ä, Ü, Ö, ß” are supported
| Questions | Answers |
|---|---|
| The domain has been suspended with an event from DENIC. What are the next steps? | Double check the details in question are correct in the contact associated with the domains. Provide proof via one of two ways: 1. Using the modifyContact API with the x-verification-* extensions. The updates are sent across to DENIC in an hourly basis. 2. Alternatively, use the modifyContact API with the x-verification-* extensions first. Next, clone the contact. Then update the domain with the ModifyDomain API, this is sent to DENIC in real time. It depends on how many requests are in the queue at DENIC’s side before the submission is reviewed. Use the statusDomain API to check back if the verification date has cleared and if the domain status is not longer under serverHold. In addition, DENIC sends a notification when they have verified the x-verification details submitted. ModifyContact - API Command CloneContact - API Command ModifyDomain - API Command StatusDomain - API Command |
| Does ICANN’s annual RDRP email template cover DENIC’s NIS2 annual reminder requirement? | Yes. |
| How to recognise genuine e-mails from DENIC? | - The sender domain is always denic.de - DENIC will never ask you to send passwords, payment details or the login by e-mail. - All verification steps are carried out exclusively via the provider. - If in doubt: Call DENIC Direct Services (+49 69 27235-275). - If something seems suspicious, please forward the e-mail to info[at]denic[dot]de. |
