Evidence and handoffs

Capture and share a snapshot

Freeze a lookup result as a read-only, shareable page so a record’s value is preserved for a ticket or handoff.

When to use it

Use this when

  • You want to attach DNS evidence to a bug report or support ticket.
  • You need a stable link to a result that won’t change when the underlying record does.

Steps

Do this

  1. Run any lookupUse any tool, then click Save snapshot in the action bar under the result.
  2. Copy the linkdnsbin stores the query metadata and result JSON and returns a public, read-only snapshot URL.
  3. Share itAnyone with the link sees exactly what you saw, including the resolver and timestamp.
  4. Manage or remove itSave while signed in (or with a dns:create key) to keep a snapshot indefinitely, then list and delete your snapshots from the account page, the REST list/delete endpoints, or the MCP list_snapshots/delete_snapshot tools.

Examples

Copyable commands

REST — create (anonymous)
curl -X POST 'https://dnsbin.ca/api/v1/snapshots' \
  -H 'Content-Type: application/json' \
  --data '{"name":"example.com","type":"A","kind":"lookup","result":{}}'
REST — read
curl 'https://dnsbin.ca/api/v1/snapshots/abc123'
REST — list your snapshots
curl -H 'Authorization: Bearer $DNSBIN_KEY' \
  'https://dnsbin.ca/api/v1/snapshots'
REST — delete one you own
curl -X DELETE -H 'Authorization: Bearer $DNSBIN_KEY' \
  'https://dnsbin.ca/api/v1/snapshots/abc123'

Operational notes

Keep in mind

  • Snapshots are public, read-only pages — don’t capture anything you wouldn’t share.
  • Creation is public and rate-limited — the browser button works without an account. Sending a dns:create API key attributes the snapshot to your account; reading is always public.
  • Retention: anonymous snapshots are deleted after 30 days. Snapshots saved to an account persist until you delete them. Listing needs dns:read; deleting needs dns:delete.