SharkDNS Docs
Practical guidance for choosing the right DNS query, reading results, and understanding public data limits.
Use DNS Lookup for direct records, Reverse IP for shared IPv4 hosts, Subdomains for inventory, and Reverse NS/MX for infrastructure overlap.
No rows means SharkDNS did not receive a usable public answer from the selected resolver or public source at that time.
The Public API page mirrors the console endpoints and includes a live request builder plus cURL, JavaScript, Python, Go, PHP, and Java examples.
DNS Lookup
Use this for direct DNS record checks, resolver visibility, mail routing review, TXT verification, and quick operational troubleshooting.
Reverse IP
Use this to discover domains observed on the same IPv4 address. Results are useful for shared hosting, infrastructure mapping, and surface review.
Subdomains
Use this to collect public subdomain observations under a root domain and build a cleaner asset inventory.
Reverse NS / MX
Use these tools to find domains sharing authoritative nameservers or mail exchangers with a target domain.
rDNS Search
Use rDNS search to match PTR names by keyword and map host naming patterns back to observed IP addresses.
DNSSEC
Use DNSSEC checks to inspect DS, DNSKEY, RRSIG, and NSEC records and understand whether a domain has DNSSEC coverage.
SSL Certificate
Use SSL checks to inspect the TLS certificate of a domain or IP, including issuer, validity dates, chain trust, TLS version, and cipher suite.
Mail Security
Use mail security checks to validate SPF, DKIM, DMARC, MTA-STS, TLS-RPT, and BIMI, including SPF include expansion and lookup counting.
Blacklist
Use blacklist checks to see whether an IPv4 address is listed on public DNS blocklists and read the listing reasons.
Propagation
Use propagation checks to query a record from public resolvers across North America, Europe, and Asia, and confirm whether a recent change is visible everywhere.
Health Check
Use health checks to audit delegation consistency, nameserver reachability and diversity, SOA timers, MX resolution, and security records such as DNSSEC, SPF, DMARC, and CAA.
ECS Test
Use ECS tests to see how resolvers answer for client subnets in different regions, check echoed scopes, and detect GeoDNS steering.
Takeover
Use takeover scans to find subdomains whose CNAME records point at deleted third-party resources that could be claimed by an attacker.
Maps a domain to IPv4 or IPv6 addresses. Use it to confirm website and service routing.
Shows alias targets. Use it to understand hosted services, CDN targets, and chained names.
Shows mail exchangers and priority. Use it to debug email routing and provider configuration.
Shows authoritative nameservers. Use it to confirm delegation and DNS hosting.
Stores verification and policy text, including SPF, DMARC, DKIM selectors, and ownership checks.
Shows zone authority metadata such as primary nameserver, serial, refresh, retry, and expiry values.
Limits which certificate authorities may issue TLS certificates for a domain.
Maps IP addresses back to hostnames. Use it for reverse DNS and infrastructure naming review.
Service binding records with protocol hints and ECH config. Increasingly used by browsers and CDNs.
Security and advanced record types for DNSSEC, DANE, SSH fingerprint, and naming authority checks.
SharkDNS is designed for public DNS visibility. Discovery results are best-effort and can be incomplete, delayed, or different from private resolver views.
For automation, use the dedicated Public API page. It contains request builders, response examples, and language snippets.
DNS answers can vary by resolver, cache timing, geography, delegation changes, and public data source coverage.
No. Empty results mean SharkDNS did not receive a usable public answer for that query and record type at that time.
The public API does not require an API key and is rate limited to 60 requests per minute per client.
SharkDNS uses live DNS queries plus public/passive datasets for discovery-style features such as reverse IP and subdomain search.