TXT Records

What It Does

Queries all TXT records at the apex and categorizes them: SPF, DKIM, domain verification tokens (Google, Facebook, Microsoft, Apple, Atlassian, DocuSign, Stripe, and 25+ more), DMARC at `_dmarc`, BIMI at `default._bimi`, MTA-STS at `_mta-sts`, and custom entries. Probes ~30 common DKIM selectors in parallel (`google._domainkey`, `selector1._domainkey`, `s1._domainkey`, `k1._domainkey`, `pm._domainkey`, etc.) and surfaces every selector that returns a `v=DKIM1` record (RFC 6376) — the only reliable way to answer "is DKIM configured?" without prior knowledge of the selector name. Detects stale `_acme-challenge` TXT tokens left over from prior ACME (RFC 8555) issuance — a hygiene smell that contributes to zone-hygiene scoring.

Why It's Useful

TXT records are the most overloaded DNS record type — a single domain may have 10+ records for different purposes. Categorization saves manual analysis. The DKIM selector probe is the most-requested email-deliverability feature gap in DNS tooling: the selector name is sender-specific and unknown without context, so DKIM is invisible to plain `dig`. Stale-ACME detection catches a real hygiene smell that often goes unnoticed. The result is a single call that answers "is this domain's email-auth and zone hygiene in good shape?"

Use Cases

Parameters

Response Fields

Code Examples

curl "https://api.edgedns.dev/v1/dns/txt" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d "domain=example.com"

const response = await fetch(
  'https://api.edgedns.dev/v1/dns/txt?domain=example.com',
  {
    headers: {
      'Authorization': 'Bearer YOUR_API_KEY'
    }
  }
);

const data = await response.json();
console.log(data);

import requests

response = requests.get(
    'https://api.edgedns.dev/v1/dns/txt',
    headers={'Authorization': 'Bearer YOUR_API_KEY'},
    params={
    'domain': 'example.com'
    }
)

data = response.json()
print(data)

Related Endpoints

External References

Learn more about the standards and protocols behind this endpoint.