# DNS Lookup API – Bulk A, MX, NS, TXT Records (`fluyeporlaweb/dns-records-lookup`) Actor

Bulk DNS lookup API via Cloudflare DoH: A, AAAA, MX, NS, TXT, CNAME, SOA. No WHOIS PII. No login. Enrich domains for SEO and ops. MCP-ready.

- **URL**: https://apify.com/fluyeporlaweb/dns-records-lookup.md
- **Developed by:** [Pablo Navarro](https://apify.com/fluyeporlaweb) (community)
- **Categories:** Developer tools, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 dns records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## DNS Lookup API – Bulk A, MX, NS, TXT Records

**DNS lookup API** for **bulk A, AAAA, MX, NS, TXT, CNAME and SOA** records via **Cloudflare DNS-over-HTTPS**. No WHOIS, no registrant emails — only public DNS resource records. MCP-ready for SEO and ops.

### What does it do?

- One dataset row per resource record.
- Domain, type, value, TTL and MX priority.
- Resolver identifier (Cloudflare DoH).

### Use cases

- **KYB / merchant checks**: verify MX/SPF/DMARC TXT.
- **Migrations**: inventory DNS before cutover.
- **Security**: spot suspicious TXT/NS changes.
- **Automations**: enrich domain lists without WHOIS PII; call from AI agents via MCP.

### Input

| Field | Description |
|---|---|
| `domains` | Hostnames to resolve. Example: example.com, google.com |
| `recordTypes` | Default A,AAAA,MX,NS,TXT,CNAME. Example: MX, TXT |
| `maxItems` | Cap on RR rows returned. |

Example input:

```json
{
  "domains": [
    "example.com",
    "cloudflare.com",
    "wikipedia.org"
  ],
  "recordTypes": [
    "A",
    "MX",
    "NS",
    "TXT"
  ],
  "maxItems": 30
}
```

### Output

Real output (sample from a prior run on 27 Oct 2026, Europe/Madrid):

```json
[
  {
    "domain": "example.com",
    "type": "A",
    "value": "172.66.147.243",
    "ttl": 71,
    "priority": null,
    "resolver": "cloudflare-dns.com"
  },
  {
    "domain": "example.com",
    "type": "A",
    "value": "104.20.23.154",
    "ttl": 71,
    "priority": null,
    "resolver": "cloudflare-dns.com"
  }
]
```

Export as JSON, CSV or Excel, read through the API, or send to Google Sheets, Make, Zapier, n8n or webhooks. You can also run this Actor from AI agents through the Apify MCP server.

### Pricing

Pay per event: **$0.50 per 1,000 DNS records plus $0.00005 per run start.** There is no extra platform usage charge beyond Apify’s normal platform fees if any apply to your plan.

### FAQ

**Is WHOIS included?** No. WHOIS often contains personal contacts and is excluded on purpose.

**Which resolver?** Cloudflare `cloudflare-dns.com` DNS-over-HTTPS JSON API.

**Can AI agents use it?** Yes. Call through the Apify API or Apify MCP server.

### Data source and license

Source: public DNS data via [Cloudflare DNS over HTTPS](https://developers.cloudflare.com/1.1.1.1/encryption/dns-over-https/make-api-requests/dns-json/). No WHOIS/personal registration data. Not affiliated with Cloudflare.

This Actor is not affiliated with or endorsed by the data source. You are responsible for using the data in line with the source's license and terms.

# Actor input Schema

## `domains` (type: `array`):

Hostnames to resolve. Example: example.com, google.com

## `recordTypes` (type: `array`):

Default A,AAAA,MX,NS,TXT,CNAME. Example: MX, TXT

## `maxItems` (type: `integer`):

Cap on RR rows returned.

## Actor input object example

```json
{
  "maxItems": 500
}
```

# Actor output Schema

## `items` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("fluyeporlaweb/dns-records-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("fluyeporlaweb/dns-records-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call fluyeporlaweb/dns-records-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,fluyeporlaweb/dns-records-lookup"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/KxnLcaOy6Znb1cbT9/builds/zgargaTPOuE5q5cLT/openapi.json