Email authentication
/api/v1/dnssec-testPacketFlo DNSSEC Test API
Check whether DNSSEC is configured and actually validating.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | Yes | Domain to check. |
Example request
curl "https://packetflo.io/api/v1/dnssec-test?domain=example.com&api_key=YOUR_API_KEY"
Example response
{ "ok": true, "data": { "domain": "example.com", "keyCount": 3, "validated": true, "status": "enabled" }, "meta": { "tool": "dnssec-test", "version": "v1" } }
Reading the result
enabled means DNSKEY answers were present and the A lookup carried the resolver's authenticated-data flag. Keys without that flag produce misconfigured; no keys produce not-configured.
Response fields
| Field | What it tells you |
|---|---|
keyCount | Number of answers returned by the DNSKEY query. |
validated | Whether the resolver set the AD flag on the A response. |
status | The classification derived from those two signals. |
Scope and limits
Uses Cloudflare DNS over HTTPS with five-second request timeouts. It relies on resolver validation rather than independently verifying the signature chain. Upstream failures can look like absent keys or missing validation; repeat an unexpected result before changing DNSSEC configuration.
Authentication and errors
Send your key in the x-api-key header, or the supported api_key query parameter. Each request uses 2 credits from the key's shared 300-credit rolling 24-hour budget. Credits are charged before parameter validation. Successful responses and quota errors include usage headers; GET and OPTIONS support CORS.
| API status | Meaning |
|---|---|
200 | The diagnostic returned a result in data, with ok: true and version information in meta. Read the diagnostic fields to determine the target's condition. |
400 | Invalid or blocked input, or a lookup/check failure that could not be returned as a diagnostic result. Read error for details. |
401 | Missing, invalid or revoked API key. |
429 | The request would exceed the key's available credit budget. |