# DNS Tools - Domain Age, WHOIS, Expiry & DNS Records Checker (`vero-api/dns-tools`) Actor

Everything about a domain in one run. Paste your domains, tick what you want to know — age, expiration date, last update, availability, owner, registrar, DNSSEC, the full WHOIS record, DNS records — and get one clean row per domain, ready to export as JSON, CSV, or Excel.

- **URL**: https://apify.com/vero-api/dns-tools.md
- **Developed by:** [VeroAPIs](https://apify.com/vero-api) (community)
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 domain checkeds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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 Tools — domain age, WHOIS, expiry & DNS records in one run

Paste a list of domains, tick what you want to know, and get one clean row per domain. Age, expiration date, last update, availability, owner, registrar, DNSSEC, the full WHOIS record, and live DNS records — for one domain or a thousand.

### What you can do

- See how old a domain is, to the day: `31 years, 1 month, 5 days`.
- Catch expiring domains before they lapse, with days-to-expiry you can sort on.
- Check whether a name is still available to register.
- Find out who owns a domain and which registrar it was bought through.
- Confirm DNSSEC is switched on and see the DS records.
- Pull the complete WHOIS record — status codes, name servers, every contact, raw text.
- Read the live DNS records: A, AAAA, CNAME, MX, NS, TXT, SOA, and CAA.
- Works across .com, .org, .io, .app, .dev, .co.uk, .de, .fr and hundreds more extensions.

### How to use it

1. Paste your domains — one per line. Full URLs are fine too.
2. Tick the checks you want. Everything is on by default.
3. Click **Start**.
4. Download your results as JSON, CSV, or Excel.

### What you get

One row per domain, ready to filter in a spreadsheet:

| domain | isAvailable | age | expiresIn | registrar.name | dnssec.enabled |
|---|---|---|---|---|---|
| example.com | false | 31 years, 1 month, 5 days | 10 months, 25 days | RESERVED-Internet Assigned Numbers Authority | true |
| wikipedia.org | false | 25 years, 8 months, 6 days | 3 years, 3 months, 24 days | MarkMonitor Inc. | true |
| bbc.co.uk | false | 31 years, 9 months, 6 days | 8 years, 2 months, 24 days | British Broadcasting Corporation | false |
| some-name-nobody-took-yet.com | true | | | | |

```json
{
  "domain": "example.com",
  "registrableDomain": "example.com",
  "checkedAt": "2026-09-19T10:00:00.000Z",
  "isAvailable": false,
  "registeredAt": "1995-08-14T04:00:00.000Z",
  "age": "31 years, 1 month, 5 days",
  "ageDays": 11359,
  "expiresAt": "2027-08-13T04:00:00.000Z",
  "expiresIn": "10 months, 25 days",
  "expiresInDays": 328,
  "isExpired": false,
  "updatedAt": "2026-08-14T08:01:43.000Z",
  "updatedAgo": "1 month, 5 days",
  "owner": null,
  "registrar": { "name": "RESERVED-Internet Assigned Numbers Authority", "ianaId": "376", "url": null, "email": null, "phone": null },
  "dnssec": { "enabled": true, "dsRecords": [{ "keyTag": 2371, "algorithm": 13, "digestType": 2, "digest": "C988EC…" }] },
  "whois": { "source": "rdap", "statuses": ["client transfer prohibited"], "nameservers": ["a.iana-servers.net", "b.iana-servers.net"], "contacts": [], "raw": "…" },
  "dns": { "a": ["93.184.215.14"], "mx": [], "ns": ["a.iana-servers.net", "b.iana-servers.net"], "txt": ["v=spf1 -all"] }
}
```

Only the checks you tick appear in the row, so a run that only asks for expiration dates gives you a tidy three-column table.

### Use it as an API

Turn on **Standby** and the actor becomes a live endpoint — no run to start, results come straight back in the response.

```bash
## one domain, two checks
curl "https://vero-api--dns-tools.apify.actor/?domain=example.com&tools=age,expiration&token=YOUR_APIFY_TOKEN"

## a batch of up to 100
curl -X POST "https://vero-api--dns-tools.apify.actor/?token=YOUR_APIFY_TOKEN" \
  -H 'content-type: application/json' \
  -d '{"domains":["example.com","wikipedia.org"],"tools":["age","registrar","dns"]}'
```

```json
{
  "results": [{ "domain": "example.com", "registrableDomain": "example.com", "age": "31 years, 1 month, 5 days", "expiresIn": "10 months, 25 days" }],
  "failed": [],
  "checked": 1,
  "skipped": 0
}
```

Perfect for checking a domain the moment someone types it into your form.

### Pricing

You pay only for the domains you check — no subscriptions, no surprises. A line that isn't a domain name is never charged.

### FAQ

**Where does the data come from?** Straight from the official registry of each extension, live at the moment you ask. Nothing is cached, so you always see today's record.

**Can I check subdomains?** Yes. Registration details come from the parent domain, and DNS records come from the exact host you entered — so `www.example.com` shows its own CNAME.

**Why is the owner empty for some domains?** Many registries hide personal details for privacy. You still get the registrar, the dates, and everything else.

**How fast is it?** Ten domains are checked at once. A list of 500 finishes in a minute or two, a thousand in under five.

**Do I need an API key?** No. Paste your domains and run it — there is nothing to sign up for.

**Can I call it from my app?** Yes — switch on Standby and hit the endpoint above. Responses come back in a second or two.

# Actor input Schema

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

The domains you want checked — one per line. Full URLs like https://www.example.com/page work too. Up to 1000 per run.

## `tools` (type: `array`):

Pick the information you want for each domain. Everything is selected by default; untick what you don't need.

## Actor input object example

```json
{
  "domains": [
    "example.com",
    "wikipedia.org"
  ],
  "tools": [
    "availability",
    "age",
    "expiration",
    "lastUpdate",
    "owner",
    "registrar",
    "dnssec",
    "whois",
    "dns"
  ]
}
```

# Actor output Schema

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

One row per domain we could check.

## `failed` (type: `string`):

Lines that weren't domain names or whose registry didn't answer, with the reason for each. Never charged.

# 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": [
        "example.com",
        "wikipedia.org",
        "bbc.co.uk"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("vero-api/dns-tools").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": [
        "example.com",
        "wikipedia.org",
        "bbc.co.uk",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("vero-api/dns-tools").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 '{
  "domains": [
    "example.com",
    "wikipedia.org",
    "bbc.co.uk"
  ]
}' |
apify call vero-api/dns-tools --silent --output-dataset

```

## MCP server setup

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

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/C9gcvoU8Ym3CQjviX/builds/iXPeIEJqT8zAxlyaz/openapi.json
