# DNS Records Audit (`conserving_mastodon/dns-records-audit`) Actor

A full DNS record inventory (A, AAAA, MX, NS, TXT, CAA, SOA, CNAME) over DNS-over-HTTPS, with the misconfigurations that matter flagged: missing CAA, no MX, apex CNAME, missing SPF/DMARC, no IPv6, no DNSSEC, single nameserver. Charged only on completed audits.

- **URL**: https://apify.com/conserving\_mastodon/dns-records-audit.md
- **Developed by:** [Chris Arsenault](https://apify.com/conserving_mastodon) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$150.00 / 1,000 completed audits

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?

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 Audit

**The whole DNS zone at a glance, with the misconfigurations that matter flagged.** One call inventories a domain's A, AAAA, MX, NS, TXT, CAA, SOA, and CNAME records over DNS-over-HTTPS, then checks the things teams forget: a missing **CAA** record (any certificate authority can then issue a cert for your domain), no MX, an illegal apex CNAME, missing SPF/DMARC, no IPv6, no DNSSEC, and single-nameserver setups with no redundancy.

### What you get

Summary plus one row per record:

```json
{
  "domain": "example.com",
  "record_types_present": ["A", "MX", "NS", "SOA", "TXT"],
  "caa_present": false,
  "spf_present": true,
  "dmarc_present": true,
  "dnssec": false,
  "issues": [
    "No CAA record: any certificate authority can issue a certificate for this domain.",
    "DNSSEC not enabled (no DNSKEY)."
  ]
}
```

### Use cases

- **Onboarding and migrations**: confirm a zone is complete and correct before and after a DNS change.
- **Security posture**: CAA and DNSSEC are quiet but real controls; this surfaces their absence.
- **Agents doing infrastructure due diligence**: a full-zone read as one tool call.

This complements the **Email Deliverability DNS Audit** (which grades SPF/DKIM/DMARC in depth) with the whole-zone view and certificate-issuance controls.

### Honesty notes

- Resolution runs over Cloudflare and Google public DoH; no zone transfer, nothing modified.
- A domain that does not resolve reports cleanly and **you are not charged**; billing is per completed audit.

Built by 1450 Enterprises, alongside Domain Intel and the Email Deliverability DNS Audit.

# Actor input Schema

## `domain` (type: `string`):

The domain to inventory (e.g. example.com). URLs are accepted and reduced to the domain.

## Actor input object example

```json
{
  "domain": "example.com"
}
```

# Actor output Schema

## `results` (type: `string`):

Summary: record types present, key presence flags (CAA, SPF, DMARC, DNSSEC), and misconfiguration issues. Then one row per DNS record.

# 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 = {
    "domain": "example.com"
};

// Run the Actor and wait for it to finish
const run = await client.actor("conserving_mastodon/dns-records-audit").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 = { "domain": "example.com" }

# Run the Actor and wait for it to finish
run = client.actor("conserving_mastodon/dns-records-audit").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 '{
  "domain": "example.com"
}' |
apify call conserving_mastodon/dns-records-audit --silent --output-dataset

```

## MCP server setup

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

```

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/6IqxOpn8wac410uNe/builds/1sEu9QpoKrR1jnBxJ/openapi.json