Addresses · Verification · Services

DNS API

Read the records
behind a domain.

Resolve addresses, inspect verification text and find service records. Get each answer with its name, value and remaining lifetime in one JSON format.

Get startedExplore the API

All ten record types on every plan.

Look up a DNS name

Try it

One name. The answer you need.

DNS records.
Ready for your app.

Choose a record type for a specific task, or leave it out to query all ten supported types at the same name.

Resolve a name to IPv4 addresses.

Ask for A records. Each answer keeps its owner name and remaining TTL in seconds.

Request

curl "https://api.parseapi.com/dns/example.com?type=A" \
  -H "X-API-Key: YOUR_API_KEY"

Example response

JSON200 OK
{
  "domain": "example.com",
  "records": [
    {
      "name": "example.com",
      "type": "A",
      "ttl": 6,
      "value": "104.20.23.154"
    },
    {
      "name": "example.com",
      "type": "A",
      "ttl": 6,
      "value": "172.66.147.243"
    }
  ]
}

Complete examples captured October 14, 2026. Records and remaining TTLs can change.

Full DNS reference

Public DNS names

The exact name.
Its remaining lifetime.

Look up domains, subdomains, international names, service labels and reverse DNS names. Keep the remaining TTL with each record when you use the answer.

Names, record values and errors
Four useful fields per record
name identifies the owner, type identifies the record, value keeps its DNS presentation text, and ttl gives remaining seconds.
Answers within their DNS lifetime
Cached answers stay within the lowest record TTL. Remaining TTLs decrease on reuse. A zero TTL means use the answer without caching it.
Empty answers and failures stay distinct
An empty records array means the name has no answers for the requested type. Missing names and temporary DNS failures have their own HTTP errors. Answers reflect a recursive DNS view and can differ by location.

Mail and verification

Read MX priorities and hosts, or query TXT at a verification, DMARC or DKIM name. For a compact mail-server list, use the MX API.

Addresses and services

Read IPv4 and IPv6 addresses, aliases and nameservers. Query SRV for a service target and port, PTR for reverse DNS, or CAA and SOA for published configuration.

From the first lookup to your app

One request.
A familiar response.

Use the same endpoint and API key for every supported record type. Add DNS to a domain setup check, support dashboard or service discovery workflow.

HTTP, SDKs and MCP

Copy a request above, choose an SDK in your language, or connect DNS to your agent through MCP.

DNS referenceChoose your SDKExplore MCP

Before you build.

Which record types can I look up?

A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, SRV and PTR. Choose one with type, or omit type to query all ten at the supplied name.

Can I check DMARC, DKIM and verification records?

Yes. Pass the full DNS name and choose TXT. Use _dmarc.example.com for DMARC, your selector._domainkey.example.com for DKIM, or the name supplied by your verification service. TXT values preserve DNS presentation text, including quoted chunks and escapes.

How fresh are the records?

Answers can be reused only within their DNS lifetime. Each ttl is the remaining number of seconds and decreases on cache hits. A zero TTL is a current answer to use immediately without caching. This is a recursive DNS view; answers can differ by location.

What happens when there is no answer?

A name with no records of the requested type returns 200 with records: []. A nonexistent name returns 404. Temporary DNS failures return 503; honor Retry-After before retrying. A failed lookup stays an error instead of an empty or partial success.

How is DNS priced?

Each call uses one request from your shared API allowance, including a call for all ten supported types. DNS is included on every plan. All record fields are included; Deep adds no further detail.

How does DNS relate to MX and Domain?

DNS returns published records and TTLs. MX gives a compact mail-server list in priority order. Domain checks registration availability and offers registration details.

DNS API pricing

Start building.

One DNS lookup uses one API request, even when you ask for all ten types. Your allowance is shared across ParseAPI products.

Free

Start with a free API key.

Room to grow

Choose your capacity on Plans.

Get startedCompare plans