Start with the live form
Enter a domain, URL, IP, email, or record and get a focused result without setup.
Review day-level DNS values observed by prior successful DomScan lookups. Beta coverage is not an internet-wide passive DNS archive.
GET /v1/dns/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.
DomScan DNS History is a beta observation log populated by successful DNS lookups. It can show day-level added and removed events, but it can miss changes between lookups, includes no external passive DNS sources, and does not prove ownership or intent.
Filter the timeline to a single RR type like A, MX, or TXT.
Set the maximum stored history rows evaluated (default 100, maximum 1000). The response says when this window is truncated.
GET /v1/dns/history?domain=example.com&type=MX&limit=10{
"total_changes": 2,
"first_seen": "2026-07-08",
"last_seen": "2026-07-09",
"current_records": {
"MX": ["mail.example.com"]
},
"history": [
{
"date": "2026-07-09",
"record_type": "MX",
"changes": [{ "action": "added", "value": "mail.example.com" }]
}
],
"beta_notice": "Lookup-driven DomScan observations only; no external passive DNS sources."
}The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
DomScan DNS History is a beta observation log populated by successful DNS lookups. It can show day-level added and removed events, but it can miss changes between lookups, includes no external passive DNS sources, and does not prove ownership or intent.