# Domain Name and DNS Configuration Change Auditor (`lavgroup/domain-name-dns-configuration-change-auditor-8824961`) Actor

Automated monitoring and alerting for domain name status and DNS record changes to detect unauthorized or risky alterations.

- **URL**: https://apify.com/lavgroup/domain-name-dns-configuration-change-auditor-8824961.md
- **Developed by:** [Taku Anan](https://apify.com/lavgroup) (community)
- **Categories:** AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 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/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

## Domain Name and DNS Configuration Change Auditor

This Apify Actor monitors DNS records and domain WHOIS information for a list of domains, detecting changes and potential security risks by comparing current snapshots with the previously stored data.

### Features

- Asynchronously fetches DNS records (A, MX, NS, TXT) and WHOIS data for each domain
- Compares with previously stored snapshots to detect changes
- Flags security risk levels based on changes
- Outputs JSON reports including snapshots, diffs, timestamps, and risk indicators
- Designed for scheduled runs to enable automated alerting and monitoring

### Input

```json
{
  "domains": ["example.com", "github.com"]
}
```

- `domains` (required): List of domain names to monitor

### Output

JSON array of reports, each containing:

- `domain`: domain name
- `timestamp`: ISO UTC timestamp of scan
- `whois`: current WHOIS info snapshot
- `dns`: current DNS records snapshot (A, MX, NS, TXT)
- `diffs`: detected changes vs previous run
- `risk_level`: string indicator (`low`, `medium`, `high`)

### Usage

Run on Apify platform with the provided input. Results are pushed to the default dataset.

### Installation

Provided as an Apify Actor with all dependencies in `requirements.txt`.

### Limitations

- WHOIS fetching uses the `whois` Python package which might have rate limits or incomplete data
- DNS queries timeout after 5 seconds

### License

MIT

# Actor input Schema

## Actor input object example

```json
{}
```

# Actor output Schema

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

Results stored in the default dataset.

# 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("lavgroup/domain-name-dns-configuration-change-auditor-8824961").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("lavgroup/domain-name-dns-configuration-change-auditor-8824961").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 lavgroup/domain-name-dns-configuration-change-auditor-8824961 --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lavgroup/domain-name-dns-configuration-change-auditor-8824961"
        }
    }
}
```

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/luD9Ms8tzkV2b7kk5/builds/iuEUMqpYVCb90ca82/openapi.json