Running a domain lookup
A quick tour of the single-domain search form.
- Enter the domain name or hostname you want to check.
- Review WHOIS, DNS, and IP intelligence in the results tabs.
Quick-start guides
Comprehensive documentation is on the way. Until then, these short guides highlight the most requested workflows.
Refreshing cached results
Use the new history view to pull fresh data.
- Open the history option from the account menu.
- Choose “Refresh now” next to the lookup you want to update.
- We will rerun the lookup and update the cache automatically.
Switching to Bulk Tool mode
Access bulk queries when you need to audit multiple domains.
- Sign in to your Argus Tool account.
- Open the Bulk Tool option from the top navigation.
- Upload a CSV file or paste domain names to start the batch query.
DNS authority and delegation
Understand how the parent zone, child NS records, authoritative responders, and SOA evidence fit together.
- Review the parent/child delegation result before assuming the in-zone NS set is reachable.
- Inspect authoritative responders and SOA metadata for the infrastructure that supplied the answer.
- Treat checks that have not run and missing evidence as unknown, not healthy.
DNS health and history
Interpret health labels using the underlying records, warnings, validator issues, and snapshot activity.
- Read the overall label together with website, security, and infrastructure signals.
- Review every warning and record issue before relying on a healthy record count.
- Use history and comparison when a result may have changed over time.
Grouped and raw DNS records
Move between purpose-based RRset groups and exact raw values without losing provenance.
- Use grouped records to review website, email, authority, and policy concerns.
- Switch to Advanced when exact owner names, TTLs, types, and values are required.
- Remember that a point-in-time lookup is not necessarily a complete zone transfer.
DNS evidence boundaries
Use resolver, evidence-type, collection, and timing metadata when interpreting absence or disagreement.
- Identify which resolver or authoritative endpoint supplied the result.
- Check evidence type and collection completeness before treating absence as definitive.
- Preserve raw values when comparing parser output or snapshots.
DNSSEC DS and DNSKEY chain
Follow the parent DS fingerprint to the child DNSKEY and understand mismatch boundaries.
- Confirm that the parent publishes the intended DS record.
- Confirm that the child zone publishes the corresponding DNSKEY.
- Compare digest type, algorithm, key tag, and key material, then validate again after propagation.