Start with the live form
Enter a domain, URL, IP, email, or record and get a focused result without setup.
Review WHOIS/RDAP snapshots DomScan observed after fresh live lookups. Compare registrar, nameserver, expiry, status, DNSSEC, transfer-lock, and privacy/redaction signals.
GET /v1/whois/history?domain=example.com
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Enter a domain, URL, IP, email, or record and get a focused result without setup.
Outputs highlight statuses, risks, records, and next actions instead of raw provider noise.
Use the request and response examples to turn a one-off check into an API call or recipe.
Each page is shaped around a practical operational question, not just a raw lookup.
See the current DNS, registration, security, pricing, or reputation evidence.
Compare the result with related checks so the next move is easier to trust.
Copy examples, open linked tools, or move into API documentation when you need scale.
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
Start from the curl and HTTP samples, then map the parameters into your application code.
See how many snapshots were returned for the selected limit. DomScan stores at most one observation per UTC day.
Summarize observed registrar, nameserver, expiry, status, and privacy/redaction differences.
Review returned observations from newest to oldest. This is not registrant history and does not prove ownership or a transfer.
GET /v1/whois/history?domain=example.com&limit=50{
"total_snapshots": 12,
"first_seen": "2023-01-01",
"summary": { "registrar_changes": 1, "nameserver_changes": 3 }
}The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
DomScan WHOIS History is an observation log, not a global archive. A fresh, successful RDAP-backed GET /v1/whois or GET /v2/whois lookup can add at most one normalized snapshot per domain per UTC day. Cached responses, bulk requests, history reads, and traditional WHOIS-only fallbacks do not add snapshots.
DomScan automatically compares the observed registrar name, expiry value, nameservers, status codes, DNSSEC, transfer-lock state, and privacy/redaction detection. It stores creation and update dates but does not compare them automatically, and it does not store historical registrant identity or contact fields. Snapshots do not prove domain ownership or a transfer.