osintverse-community/dns-records
Looks up a domain's A, AAAA, CNAME, MX, NS, TXT, SOA and CAA records
No key · Docker
8 tools. 7 run with ot in a sandbox on Windows, macOS and Linux; 1 with otlite on Linux and macOS, no Docker. Compare them side by side ↓
DNS records are public and never redacted, which makes them the most reliable facts about a domain: where its website and mail are hosted, which cloud and security services it uses (from TXT verification records and CNAMEs), and whether its mail is protected against spoofing. The tools below read those records through ordinary resolvers.
Windows, macOS and Linux, with Docker or Podman. Each tool runs in a read-only container that can reach only the sites it declares, and every result comes back in the same JSON shape.
Looks up a domain's A, AAAA, CNAME, MX, NS, TXT, SOA and CAA records
Resolves a domain's DNS records (A, AAAA, CNAME, NS, TXT, MX, SOA, CAA) through public resolvers
Enumerates a domain's DNS: standard records, SRV services, zone transfer checks and DNSSEC
Checks a domain's SPF, DMARC, MX, BIMI and DNSSEC records and reports problems
Identifies the cloud, email, CDN and security services a domain uses from its DNS records
Looks up a domain's WHOIS/RDAP, DNS, mail security, TLS, HTTP headers, tech stack and SEO in one JSON report
Finds a domain's subdomains and DNS records, or an IP's reverse DNS, network and hosted domains, via HackerTarget
ot install osintverse-community/dns-records osintverse-community/dnsx osintverse-community/dnsrecon osintverse-community/checkdmarc osintverse-community/radarInstalls the first 5 in one go; ot auto d:… then runs every installed tool that takes a domain and saves the results. No ot yet? Install it in one line.
Linux and macOS. otlite installs each one with pip or git into its own virtualenv, pinned to a version it has tested: otlite install fierce.
| osintverse-community/ | dns record, domain | None | Online, passive | No | Python | No reports yet | 171 |
| osintverse-community/ | dns record, domain, ip | None | Online, passive | No | Docker | No reports yet | fewer than 10 |
| osintverse-community/ | dns record, domain, ip | None | Contacts the target | No | Docker | No reports yet | fewer than 10 |
| osintverse-community/ | dns record, domain, ip | None | Online, passive | No | Docker | No reports yet | fewer than 10 |
| osintverse-community/ | dns record, domain, ip, organization… | None | Online, passive | No | Docker | No reports yet | fewer than 10 |
| osintverse-community/ | certificate, dns record, ip, organization… | None | Contacts the target | No | Docker | No reports yet | fewer than 10 |
| osintverse-community/ | dns record, organization | None | Online, passive | No | Docker | No reports yet | fewer than 10 |
Facts from each tool's manifest and what people report about whether it works. "Reaches" says whether a run stays offline, reads public sources, sends requests about the target, or may notify them.
Every registry tool here runs on your machine in a sandbox, and ot auto d:… runs all the installed ones on one value.
A lookup goes through public resolvers to the domain's name servers, as every visitor's does, so it doesn't stand out. A zone transfer attempt (dnsrecon checks for one) is different: it asks the name server directly, and dnsrecon's row says it contacts the target.
Verification tokens for the services the domain uses (Google Workspace, Microsoft 365, Atlassian, marketing tools), its SPF policy naming who may send its mail, and sometimes notes left by administrators.
No. ot runs each tool on your own machine in a read-only container that can only reach the sites the tool declares, and results stay in your results folder. The registry only counts installs.
Most tools here work without one; the row says "Key required" when one is needed, and ot keys set stores it in your OS keychain so only that tool's container sees it.
SubdomainsEvery known URLLook-alike domainsWHOIS recordEmail addressesAll domain tools