CompleteDNS

CompleteDNS is a DNS research platform that tracks nameserver modifications and domain drops, with over twenty years of history and billions of recorded changes. The CompleteDNS API exposes domain-scoped lookups that return the chronological history of nameserver changes, drop events, and parking status for a given domain. Both a current v2 API and a legacy v1 API are available, authenticated by API key.

CompleteDNS publishes 2 API contracts indexed on the APIs.io network: DNS History API and NS History API. Tagged areas include DNS, DNS History, Domain Intelligence, Domains, and Nameservers.

The CompleteDNS catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.

CompleteDNS’s developer surface includes authentication, developer portal, documentation, signup flow, pricing, and 13 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

34.2/100 thin ▬ flat Agent 20/100 agent aware saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

2 published contracts

DNS DNS History Domain Intelligence DomainsNameserversThreat Intelligence

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 34.2/100 · thin

Contract Quality 11.3 / 21

Developer Ergonomics 5.5 / 17

Access Clarity 4.3 / 17

Operational Transparency 0.9 / 11

Contract Governance 1.4 / 10

Discoverability 5.6 / 9

Regulatory Posture 2.5 / 15

Agent readiness — 20/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 4 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/completedns/"><img src="https://apis.io/badge/completedns/card.svg" alt="CompleteDNS on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 25.0 — up to +15.0 composite points
Developer Ergonomics scores 32.1 — up to +13.6 composite points
Operational Transparency scores 7.9 — up to +12.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/completedns/apis.yml: open an issue on github.com/api-evangelist/completedns to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Domains and DNS (registrars, registries, DNS)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

DNS

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

CompleteDNS DNS History API

Nameserver and drop history for a domain

CompleteDNS NS History API

Nameserver history (legacy) for a domain

Postman Collections 2

Ready-to-run Postman collections for exercising this provider's APIs.

CompleteDNS API v1 DNS History API

POSTMAN

CompleteDNS API v1 DNS History NS History API

POSTMAN

Open Collections 4

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

CompleteDNS API v1 DNS History API

OPEN COLLECTION

CompleteDNS API v1 DNS History NS History API

OPEN COLLECTION

CompleteDNS API v1

OPEN COLLECTION

CompleteDNS API v2

OPEN COLLECTION

CompleteDNS API pricing

Not yet checked against CompleteDNS's own pricing page. Compiled by API Evangelist on 2026-05-04; confirm before you rely on a figure. A free plan or tier is listed.

Plan	Price
Free freemium	Free
Professional paid	Free
Enterprise enterprise	—

Plan details, limits and sources →

Rate limits

Free Tier Default: 10 requests per minute
Free Tier Monthly Quota: 1000 requests per month
Professional Tier Default: 100 requests per minute

Compiled by API Evangelist, not yet checked against CompleteDNS's documentation. All 5 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Completedns Plans Pricing

3 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Completedns Rate Limits

5 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

CompleteDNS

SLA

FinOps 1

Cost, billing, and metering signals for API financial operations.

Completedns Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Completedns Context

0 classes · 3 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

CompleteDNS — jsonschema rules

5 rules · 4 warnings 1 info

SPECTRAL

CompleteDNS API Rules

10 rules · 4 errors 5 warnings 1 info

SPECTRAL

JSON Schema 1

Standalone JSON Schema definitions for this provider's data models.

CompleteDNS DNS History

6 properties

JSON SCHEMA

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Completedns Authentication

apiKey · 1 scheme

SECURITY

Completedns Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Completedns Agentic Access

2 operations

2 operations · 0 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

Portal

Portal

Signup

Signup

Login

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

JSONSchema

JSONSchema

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

JSONLD

JSONLD

Build 1

SDKs, sample code, and the tooling you integrate with

PostmanWorkspace

PostmanWorkspace

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Contact

Contact

Commercial 5

Pricing, plans, and the legal terms of use

Plans

FinOps

Pricing

TermsOfService

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: completedns
name: CompleteDNS
description: CompleteDNS is a DNS research platform that tracks nameserver modifications and domain drops, with over twenty
  years of history and billions of recorded changes. The CompleteDNS API exposes domain-scoped lookups that return the chronological
  history of nameserver changes, drop events, and parking status for a given domain. Both a current v2 API and a legacy v1
  API are available, authenticated by API key.
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: medium
  source:
  - plans
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
position: Consuming
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/completedns.png
url: https://raw.githubusercontent.com/api-evangelist/completedns/refs/heads/main/apis.yml
tags:
- DNS
- DNS History
- Domain Intelligence
- Domains
- Nameservers
- Threat Intelligence
created: '2025-02-09'
modified: '2026-05-19'
specificationVersion: '0.23'
kind: company
apis:
- aid: completedns:completedns-dns-history-api
  name: CompleteDNS DNS History API
  description: Nameserver and drop history for a domain
  humanURL: https://completedns.com/api/documentation/v2
  baseURL: https://api.completedns.com/v2
  tags:
  - DNS History
  properties:
  - type: OpenAPI
    url: openapi/completedns-dns-history-api-openapi.yml
  - type: Documentation
    url: https://completedns.com/api/documentation/v2
  - type: SpectralRules
    url: rules/completedns-rules.yml
  - type: Documentation
    url: https://completedns.com/api/documentation/v1
- aid: completedns:completedns-ns-history-api
  name: CompleteDNS NS History API
  description: Nameserver history (legacy) for a domain
  humanURL: https://completedns.com/api/documentation/v2
  baseURL: https://api.completedns.com/v2
  tags:
  - NS History
  properties:
  - type: OpenAPI
    url: openapi/completedns-ns-history-api-openapi.yml
  - type: Documentation
    url: https://completedns.com/api/documentation/v2
  - type: SpectralRules
    url: rules/completedns-rules.yml
  - type: Documentation
    url: https://completedns.com/api/documentation/v1
common:
- type: Plans
  url: plans/completedns-plans-pricing.yml
- type: RateLimits
  url: rate-limits/completedns-rate-limits.yml
- type: FinOps
  url: finops/completedns-finops.yml
- type: Website
  url: https://www.completedns.com/
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/completedns/overview
- type: AgenticAccess
  url: agentic-access/completedns-agentic-access.yml
- type: DomainSecurity
  url: security/completedns-domain-security.yml
- type: Authentication
  url: authentication/completedns-authentication.yml
- type: Portal
  url: https://completedns.com/
- type: Documentation
  url: https://completedns.com/api/documentation/v2
- type: Signup
  url: https://completedns.com/register
- type: Login
  url: https://completedns.com/login
- type: Pricing
  url: https://completedns.com/pricing
- type: Contact
  url: https://completedns.com/contact
- type: TermsOfService
  url: https://completedns.com/terms
- type: PrivacyPolicy
  url: https://completedns.com/privacy
- type: JSONLD
  url: json-ld/completedns-context.jsonld
- type: JSONSchema
  url: json-schema/completedns-dns-history-schema.json
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

CompleteDNS API — frequently asked questions

Does CompleteDNS have an API?

Yes. APIs.io lists 2 APIs from CompleteDNS, including CompleteDNS DNS History API and CompleteDNS NS History API.

Is there an OpenAPI specification for the CompleteDNS API?

Yes. APIs.io indexes 2 OpenAPI specifications for CompleteDNS, each linked for download from this page.

How do I authenticate with the CompleteDNS API?

CompleteDNS uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Completedns Authentication.

How much does the CompleteDNS API cost?

APIs.io lists 3 pricing plans for CompleteDNS, with each plan's price, limits and inclusions under Pricing on this page.

Is the CompleteDNS API ready for AI agents?

CompleteDNS has a Kin Score of 34.2 out of 100 (thin) and an Agent Readiness score of 19.9 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/completedns"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/completedns/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/completedns/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.