# DNS Records Lookup & Monitor — Bulk DNS to JSON/CSV (`q_services/dns-records-lookup`) Actor

Resolve A, AAAA, MX, TXT, NS, CNAME, SOA and CAA records for any list of domains. Fast, reliable, schedule-ready for DNS monitoring.

- **URL**: https://apify.com/q\_services/dns-records-lookup.md
- **Developed by:** [Q Services](https://apify.com/q_services) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.30 / 1,000 results

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## DNS Records Lookup & Monitor — Bulk DNS to JSON/CSV

Résout les enregistrements DNS (**A, AAAA, MX, TXT, NS, CNAME, SOA, CAA**) pour n'importe quelle liste de domaines, et retourne un dataset propre prêt à exporter en JSON, CSV ou Excel.

Idéal pour : monitoring DNS, détection de changement non autorisé, audit de migration, inventaire d'infrastructure.

**Exemple de résultat :**

```json
{
    "domain": "apify.com",
    "recordType": "MX",
    "status": "NOERROR",
    "records": ["10 aspmx.l.google.com.", "20 alt1.aspmx.l.google.com."],
    "recordCount": 2,
    "scrapedAt": "2026-07-10T10:30:00.000Z"
}
```

### Comment l'utiliser

1. Collez votre liste de **domaines**
2. (Optionnel) Choisissez les **types d'enregistrements** à interroger
3. Cliquez sur **Start** — les résultats apparaissent dans l'onglet *Dataset*

Astuce : planifiez un run quotidien (onglet *Schedule*) pour surveiller tout changement DNS.

### Combien ça coûte ?

| Événement | Prix |
|---|---|
| Démarrage du run | 0,005 $ |
| Par enregistrement résolu | 0,0003 $ |

**Exemple : 100 domaines × 8 types = 800 résultats ≈ 0,25 $.**

### Champs retournés

| Champ | Type | Toujours présent ? |
|---|---|---|
| `domain` | texte | Oui |
| `recordType` | texte | Oui |
| `status` | texte (NOERROR, NXDOMAIN…) | Oui |
| `records` | liste de textes | Oui (vide si aucun) |
| `recordCount` | nombre | Oui |
| `error` | texte | Non (présent seulement en cas d'erreur réseau) |
| `scrapedAt` | date ISO | Oui |

### Limitations

- Résolution via DNS-over-HTTPS (Cloudflare) — reflète la vue publique du DNS, pas forcément votre résolveur local
- Ne résout pas les enregistrements internes/privés non publiés

### FAQ

**Puis-je l'utiliser via API ?** Oui, chaque Actor Apify est appelable par API et via MCP.

**Est-ce légal ?** Le DNS est un annuaire public. L'Actor n'interroge que des données publiquement résolvables.

# Actor input Schema

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

Liste de domaines à résoudre (avec ou sans https://). Exemple : example.com, mon-site.fr

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

Types DNS à interroger. Par défaut : tous les principaux.

## Actor input object example

```json
{
  "domains": [
    "apify.com"
  ],
  "recordTypes": [
    "A",
    "AAAA",
    "MX",
    "TXT",
    "NS",
    "CNAME",
    "SOA",
    "CAA"
  ]
}
```

# 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 = {
    "domains": [
        "apify.com"
    ],
    "recordTypes": [
        "A",
        "AAAA",
        "MX",
        "TXT",
        "NS",
        "CNAME",
        "SOA",
        "CAA"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("q_services/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 = {
    "domains": ["apify.com"],
    "recordTypes": [
        "A",
        "AAAA",
        "MX",
        "TXT",
        "NS",
        "CNAME",
        "SOA",
        "CAA",
    ],
}

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

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

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

```

## CLI example

```bash
echo '{
  "domains": [
    "apify.com"
  ],
  "recordTypes": [
    "A",
    "AAAA",
    "MX",
    "TXT",
    "NS",
    "CNAME",
    "SOA",
    "CAA"
  ]
}' |
apify call q_services/dns-records-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=q_services/dns-records-lookup",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

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