Market catalog

Domain Infrastructure Change Monitor

A proposed public-data API and feed for teams that need normalized domain registration, nameserver, DNS, and certificate-transparency changes without running their own monitors.

Request this feed View current demo Open paid API

GET /v1/domains/changes?domain=example.com&since=2026-07-01&include=rdap,certificates

{
  "data": [
    {
      "domain": "example-security.test",
      "changeType": "nameserver_changed",
      "observedAt": "2026-07-02T18:10:00Z",
      "sources": ["RDAP"],
      "evidence": { "nameserver": "ns1.example.net" }
    }
  ],
  "meta": { "sampleOnly": true, "market": "domain-infrastructure" }
}

Buyer Fit

This catalog entry summarizes the buyer fit, sources, and access model for this data product.

Domain and certificate change monitoring for SOC and brand-protection workflows.
Public-source enrichment for security products and internal alert workers.
CSV/report subscription path for non-developer review queues.

Public Data Sources

The initial product would normalize public records into stable polling endpoints and exports.

IETF RDAP JSON response and query standards
IANA RDAP bootstrap registries
Certificate Transparency public log ecosystem

Buyer Workflows

These are the specific self-serve workflows this page is designed to support.

Domain asset change watchlist

Poll public RDAP and certificate changes for owned, supplier, or lookalike domains without maintaining separate parsers.

Certificate issue monitoring

Surface new public certificate events for domains that need brand, phishing, or asset-inventory review.

Infrastructure enrichment

Normalize registrar, nameserver, and source evidence for security logs and incident-response queues.

Specific Workflow Tests

These pages focus on specific buyer workflows.

Workflow page Domain Asset Change API Domain and certificate change watchlists for security tools

Access Model

Pricing starts with narrow, low-touch access paths for qualified buyers.

Review the source coverage, sample response, and likely workflow fit.
Request access when the workflow matches a buyer use case.
Production availability depends on source scope, refresh cadence, and compliance boundaries.

Product FAQ

Is this a private WHOIS or personal data product?

No. This catalog entry is limited to public infrastructure metadata and source-linked changes. It should avoid personal data enrichment and unsupported attribution claims.

Why not build it immediately?

The domain-intelligence market is competitive and abuse-prone. Qualified buyer requests should map to a narrow, source-linked workflow.