---
title: "Remove the specifed DNSSEC record from the domain"
method: DELETE
path: "/v2/customers/{customerId}/domains/{domain}/dnssecRecords"
tags: ["Domains"]
---

# Remove the specifed DNSSEC record from the domain

`DELETE /v2/customers/{customerId}/domains/{domain}/dnssecRecords`

## Request

- Base URL: `https://api.ote-godaddy.com`
- URL: `https://api.ote-godaddy.com/v2/customers/{customerId}/domains/{domain}/dnssecRecords`
- Auth: none declared

## Path parameters

- `customerId` string, required
- `domain` string, required

## Headers

- `X-Request-Id` string

## Request body

- DomainDnssec[]
  - `algorithm` 'RSAMD5' | 'DH' | 'DSA' | 'RSASHA1' | 'DSA_NSEC3_SHA1' | 'RSASHA1_NSEC3_SHA1' | 'RSASHA256' | 'RSASHA512' | 'ECC_GOST' | 'ECDSAP256SHA256' | 'ECDSAP384SHA384' | 'ED25519' | 'ED448' | 'PRIVATEDNS' | 'PRIVATEOID', required: This identifies the cryptographic algorithm used to generate the signature<br/><ul><li><strong style='margin-left: 12px;'>RSAMD5</strong> - [01] DRSA/MD5 </li><li><strong style='margin-left: 12px;'>DSA</strong> - [03] DSA/SHA1</li><li><strong style='margin-left: 12px;'>RSASHA1</strong> - [05] RSA/SHA-1</li><li><strong style='margin-left: 12px;'>DSA_NSEC3_SHA1</strong> - [06] DSA-NSEC3-SHA1</li><li><strong style='margin-left: 12px;'>RSASHA1_NSEC3_SHA1</strong> - [07] RSASHA1-NSEC3-SHA1</li><li><strong style='margin-left: 12px;'>RSASHA256</strong> - [08] RSA/SHA-256</li><li><strong style='margin-left: 12px;'>RSASHA512</strong> - [10] RSA/SHA-512</li><li><strong style='margin-left: 12px;'>ECC_GOST</strong> - [12] GOST R 34.10-2001</li><li><strong style='margin-left: 12px;'>ECDSAP256SHA256</strong> - [13] ECDSA Curve P-256 with SHA-256</li><li><strong style='margin-left: 12px;'>ECDSAP384SHA384</strong> - [14] ECDSA Curve P-384 with SHA-384</li><li><strong style='margin-left: 12px;'>ED25519</strong> - [15] Ed25519</li><li><strong style='margin-left: 12px;'>ED448</strong> - [16] Ed448</li></ul>
  - `keyTag` integer: This is an integer value less than 65536 used to identify the DNSSEC record for the domain name.
  - `digestType` 'SHA1' | 'SHA256' | 'GOST' | 'SHA384': This identifies the algorithm used to construct the digest<br/><ul><li><strong style='margin-left: 12px;'>SHA1</strong> - [01] SHA-1</li><li><strong style='margin-left: 12px;'>SHA256</strong> - [02] SHA-256</li><li><strong style='margin-left: 12px;'>GOST</strong> - [03] GOST R 34.11-94</li><li><strong style='margin-left: 12px;'>SHA384</strong> - [04] SHA-384</li></ul>
  - `digest` string: The digest is an alpha-numeric value
  - `flags` 'ZSK' | 'KSK': This identifies the key type; either a Zone-Signing Key or a Key-Signing Key<br/><ul><li><strong style='margin-left: 12px;'>ZSK</strong> - [256] Zone-Signing Key</li><li><strong style='margin-left: 12px;'>KSK</strong> - [257] Key-Signing Key</li></ul>
  - `publicKey` string: Registries use this value to encrypt DS records. Decryption requires a matching public key
  - `maxSignatureLife` integer: This specifies the validity period for the signature. The value is expressed in seconds. You can use any integer value larger than zero

## Response `202`

Request Accepted. You may use GET /v2/customers/{customerId}/domains/{domain}/actions/DNSSEC_DELETE to poll status

## Other responses

- `400`: Authentication info not sent or invalid
- `401`: Request was malformed
- `403`: Authenticated user is not allowed access
- `404`: The domain does not exist
- `409`: There is already a similar action processing
- `422`: Request body doesn't fulfill schema, see details in `fields`
- `429`: Too many requests received within interval
- `500`: Internal server error

---

[API](https://skmtc.dev/godaddy/apis/domains-api.md) - [All operations](https://skmtc.dev/godaddy/apis/domains-api/llms.txt) - [OpenAPI document](https://skmtc.dev/godaddy/apis/domains-api/revisions/475bd0561c3c?raw)