DNSSECs
/
Create DNSSEC

Name.com Core API (1.0.1)

RESTful API for managing domains, DNS records, and related services at Name.com. Access via HTTPS at api.name.com (production) or api.dev.name.com (testing). Supports standard authentication, rate-limited to 20 requests/second.

Download OpenAPI description
namecom.api.json
namecom.api.yaml
Overview
Account Services

accountservices@name.com

Terms of Service

Languages
Servers
Mock server

https://docs.name.com/_mock/coreapi/namecom.api/

Testing

https://api.dev.name.com/

Hello

Use the Hello endpoint to verify that your API connection and credentials are working properly. This simple call returns a success message (along with server time and version info) to confirm the API is reachable and authenticated.

Operations

Account Info

Use Account Info endpoints to retrieve basic information about your Name.com account. For example, you can check your account’s current credit balance and other account details using these endpoints.

Operations

Accounts

Use Accounts endpoints (available upon request) to manage sub-accounts under your main account. For example, resellers can programmatically create new customer accounts with their own login credentials and permissions.

Operations

Domains

Use Domains endpoints to search for domain availability, register new domains, and manage existing domains.

Operations

DNS

Use DNS endpoints to manage DNS records for your domains. You can list all existing DNS records for a domain and create, update, or delete records as needed.

Operations

DNSSECs

Use DNSSEC endpoints to configure DNS Security Extensions for your domains. These endpoints allow you to add, retrieve, or remove DNSSEC records.

Operations

List DNSSECs

Request

Lists all DNSSEC (DS) records configured for a domain.

Path
domainNamestringrequired

DomainName is the domain name to list keys for.

curl -i -X GET \
  -u <username>:<password> \
  'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/domains/{domainName}/dnssec'

Responses

A successful response.

Bodyapplication/json
dnssecArray of objects(DNSSEC)required

Dnssec is the list of registered DNSSEC keys.

dnssec[].​algorithminteger(int32)(Algorithm is an integer identifying the algorithm used for signing. Valid values can be found here: https://www.iana.org/assignments/dns-sec-alg-numbers/dns-sec-alg-numbers.xhtml)required
dnssec[].​digeststringrequired

Digest is a digest of the DNSKEY RR that is registered with the registry.

dnssec[].​digestTypeinteger(int32)(DigestType is an integer identifying the algorithm used to create the digest. Valid values can be found here: https://www.iana.org/assignments/ds-rr-types/ds-rr-types.xhtml)required
dnssec[].​domainNamestringrequired

DomainName is the domain name.

dnssec[].​keyTaginteger(int32)(KeyTag contains the key tag value of the DNSKEY RR that validates this signature. The algorithm to generate it is here: https://tools.ietf.org/html/rfc4034#appendix-B)required
Response
application/json
{
  "dnssec": [
    { … }
  ]
}

Create DNSSEC

Request

Adds (registers) a new DNSSEC DS record for a domain.

Path
domainNamestringrequired

DomainName is the domain name to create keys for.

Bodyapplication/jsonrequired
algorithminteger(int32)(Algorithm is an integer identifying the algorithm used for signing. Valid values can be found here: https://www.iana.org/assignments/dns-sec-alg-numbers/dns-sec-alg-numbers.xhtml)
digeststring

Digest is a digest of the DNSKEY RR that is registered with the registry.

domainNamestring

The name of the domain.

digestTypeinteger(int32)(DigestType is an integer identifying the algorithm used to create the digest. Valid values can be found here: https://www.iana.org/assignments/ds-rr-types/ds-rr-types.xhtml)
keyTaginteger(int32)(KeyTag contains the key tag value of the DNSKEY RR that validates this signature. The algorithm to generate it is here: https://tools.ietf.org/html/rfc4034#appendix-B)
curl -i -X POST \
  -u <username>:<password> \
  'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/domains/{domainName}/dnssec' \
  -H 'Content-Type: application/json' \
  -d '{
    "algorithm": 0,
    "digest": "string",
    "domainName": "string",
    "digestType": 0,
    "keyTag": 0
  }'

Responses

A successful response.

Bodyapplication/json
algorithminteger(int32)(Algorithm is an integer identifying the algorithm used for signing. Valid values can be found here: https://www.iana.org/assignments/dns-sec-alg-numbers/dns-sec-alg-numbers.xhtml)required
digeststringrequired

Digest is a digest of the DNSKEY RR that is registered with the registry.

digestTypeinteger(int32)(DigestType is an integer identifying the algorithm used to create the digest. Valid values can be found here: https://www.iana.org/assignments/ds-rr-types/ds-rr-types.xhtml)required
domainNamestringrequired

DomainName is the domain name.

keyTaginteger(int32)(KeyTag contains the key tag value of the DNSKEY RR that validates this signature. The algorithm to generate it is here: https://tools.ietf.org/html/rfc4034#appendix-B)required
Response
application/json
{
  "algorithm": 0,
  "digest": "string",
  "digestType": 0,
  "domainName": "string",
  "keyTag": 0
}

Delete DNSSEC

Request

Deletes a DNSSEC record from a domain.

Path
domainNamestringrequired

DomainName is the domain name the key is registered for.

digeststringrequired

Digest is the digest for the DNSKEY RR to remove from the registry.

curl -i -X DELETE \
  -u <username>:<password> \
  'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/domains/{domainName}/dnssec/{digest}'

Responses

DNSSEC successfully deleted.

Response
No content

Get DNSSEC

Request

Retrieves details of a specific DNSSEC record for a domain.

Path
domainNamestringrequired

DomainName is the domain name.

digeststringrequired

Digest is the digest for the DNSKEY RR to retrieve.

curl -i -X GET \
  -u <username>:<password> \
  'https://docs.name.com/_mock/coreapi/namecom.api/core/v1/domains/{domainName}/dnssec/{digest}'

Responses

A successful response.

Bodyapplication/json
algorithminteger(int32)(Algorithm is an integer identifying the algorithm used for signing. Valid values can be found here: https://www.iana.org/assignments/dns-sec-alg-numbers/dns-sec-alg-numbers.xhtml)required
digeststringrequired

Digest is a digest of the DNSKEY RR that is registered with the registry.

digestTypeinteger(int32)(DigestType is an integer identifying the algorithm used to create the digest. Valid values can be found here: https://www.iana.org/assignments/ds-rr-types/ds-rr-types.xhtml)required
domainNamestringrequired

DomainName is the domain name.

keyTaginteger(int32)(KeyTag contains the key tag value of the DNSKEY RR that validates this signature. The algorithm to generate it is here: https://tools.ietf.org/html/rfc4034#appendix-B)required
Response
application/json
{
  "algorithm": 0,
  "digest": "string",
  "digestType": 0,
  "domainName": "string",
  "keyTag": 0
}

Email Forwardings

Use Email Forwardings endpoints to set up and manage email forwarding addresses on your domains.

Operations

URL Forwardings

Use URL Forwardings endpoints to control URL redirection settings for your domains.

Operations

Vanity Nameservers

Use Vanity Nameservers endpoints to configure custom nameserver hostnames (glue records) for your domains.

Operations

Transfers

Use Transfers endpoints to move domains into your Name.com account. Start by creating a transfer request, then monitor and manage the status of pending transfers. You can also cancel a transfer if needed.

Operations

Orders

Use Orders endpoints to review and track purchases made via the API.

Operations

Webhook Notifications

Use Webhook Notification endpoints to subscribe to real-time notifications for account and domain events. This keeps your application updated on important changes without polling the API.

OperationsWebhooks