Skip to main content
POST
/
dnssec
Check if DNSSEC is enabled for a domain
curl --request POST \
  --url https://api.geekflare.com/dnssec \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '
{
  "url": "https://example.com"
}
'
{
  "timestamp": 1776233511285,
  "apiStatus": "success",
  "apiCode": 200,
  "meta": {
    "url": "example.com",
    "test": {
      "id": "mxqx9v9y0742lap6altwdteqd28t23nq"
    }
  },
  "data": {
    "isEnabled": true,
    "dnskey": [
      "DNSKEY 256 3 13 oJMRESz5E4gYzS/q6XDrvU1qMPYIjCWzJaOau8XNEZeqCYKD5ar0IRd8 KqXXFJkqmVfRvMGPmM1x8fGAa2XhSA=="
    ],
    "rrsig": [
      "RRSIG DNSKEY 13 2 3600 20251124121323 20250924121323 2371 geekflare.com. LUeqKWfw4GcaqSaCbFT7ik6mTgFdWsRdVzn1hHGSwMGZ4HuwlVFB3e1K 9Os+4DnxyYNkfWkBHJcBfFN7e4snHg=="
    ]
  }
}

Documentation Index

Fetch the complete documentation index at: https://docs.geekflare.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

x-api-key
string
header
required

API Key required for all endpoints

Body

application/json
url
string
required

Target URL

Example:

"https://example.com"

Response

DNSSEC test result retrieved successfully

timestamp
number
required

Timestamp of the request in milliseconds

Example:

1776233511285

apiStatus
enum<string>
required

API status message

Available options:
success,
failure
Example:

"success"

apiCode
number
required

API status code

Example:

200

meta
object
required

Metadata about the DNSSEC test

data
object
required

DNSSEC test result data