History

Quick-start guides

Comprehensive documentation is on the way. Until then, these short guides highlight the most requested workflows.

Registration status codes

Read EPP status codes with the registration source and operational context.

  1. Keep the exact returned status code: client and server prefixes distinguish registrar-side and registry-side restrictions.
  2. Review the adjacent status description and registration evidence. A transfer or update restriction does not by itself prove that DNS or the website is failing.
  3. For holds, pending operations or an unexpected restriction, check the registrar or registry's own documentation before changing the domain.
Open Pulse

SPF sender authorization

Distinguish a published policy from a message authentication result.

  1. Review the published TXT record and any reported syntax or incomplete-query warnings.
  2. SPF authorizes infrastructure for the envelope sender domain; it is not a direct check of the visible From address.
  3. Use Email Authentication with real message headers to inspect SPF, DKIM and DMARC alignment. A missing or failed DNS query is not a confirmed authentication failure.
Open Email Authentication

DMARC policy and alignment

Read policy, inheritance and testing separately from a message verdict.

  1. Identify which domain supplied the policy and whether it is inherited. Review the exact published record and any incomplete-query warnings.
  2. A DMARC pass depends on aligned SPF or DKIM for a message. The existence of a DMARC record alone is not a pass.
  3. Review the effective policy and testing indication in Email Authentication before drawing enforcement conclusions; receivers can apply their own local policy.
Open Email Authentication

Running a domain lookup

A quick tour of the single-domain search form.

  1. Enter the domain name or hostname you want to check.
  2. Review WHOIS, DNS, and IP intelligence in the results tabs.
Open Lookup tool

Refreshing cached results

Use the new history view to pull fresh data.

  1. Open the history option from the account menu.
  2. Choose “Refresh now” next to the lookup you want to update.
  3. We will rerun the lookup and update the cache automatically.
Open History

Switching to Bulk Tool mode

Access bulk queries when you need to audit multiple domains.

  1. Sign in to your Argus Tool account.
  2. Open the Bulk Tool option from the top navigation.
  3. Upload a CSV file or paste domain names to start the batch query.
Open Bulk Tool

DNS authority and delegation

Understand how the parent zone, child NS records, authoritative responders, and SOA evidence fit together.

  1. Review the parent/child delegation result before assuming the in-zone NS set is reachable.
  2. Inspect authoritative responders and SOA metadata for the infrastructure that supplied the answer.
  3. Treat checks that have not run and missing evidence as unknown, not healthy.
Open DNS lookup

DNS health and history

Interpret health labels using the underlying records, warnings, validator issues, and snapshot activity.

  1. Read the overall label together with website, security, and infrastructure signals.
  2. Review every warning and record issue before relying on a healthy record count.
  3. Use history and comparison when a result may have changed over time.
Open History

Grouped and raw DNS records

Move between purpose-based RRset groups and exact raw values without losing provenance.

  1. Use grouped records to review website, email, authority, and policy concerns.
  2. Switch to Advanced when exact owner names, TTLs, types, and values are required.
  3. Remember that a point-in-time lookup is not necessarily a complete zone transfer.
Open DNS lookup

DNS evidence boundaries

Use resolver, evidence-type, collection, and timing metadata when interpreting absence or disagreement.

  1. Identify which resolver or authoritative endpoint supplied the result.
  2. Check evidence type and collection completeness before treating absence as definitive.
  3. Preserve raw values when comparing parser output or snapshots.
Open DNS lookup

DNSSEC DS and DNSKEY chain

Follow the parent DS fingerprint to the child DNSKEY and understand mismatch boundaries.

  1. Confirm that the parent publishes the intended DS record.
  2. Confirm that the child zone publishes the corresponding DNSKEY.
  3. Compare digest type, algorithm, key tag, and key material, then validate again after propagation.
Open DNSSEC check