DNS Lookup
Query DNS records using Google's public DNS-over-HTTPS API
More Tools
Showing 8 of 95 related tools
Quick Start Guide
Get up and running in 30 seconds
Quick Start Guide
- 1
Enter a Domain
Type a domain name like example.com or subdomain.example.com. No protocol prefix needed — just the bare domain.
- 2
Choose Record Types
Select one or more record types: A (IPv4), AAAA (IPv6), CNAME, MX (mail), TXT (SPF/DKIM), NS (nameservers), SOA, PTR (reverse). Multiple selections query all at once.
- 3
Click Lookup
Hit the Lookup button (or press Enter) to query Google's public DNS-over-HTTPS API. Results appear with record values, TTLs, and response times.
- 4
Batch Lookup
Switch to Batch mode to query multiple domains at once. Enter one domain per line or comma-separated. All selected record types are queried for every domain.
What is DNS?
Understanding DNS records
DNS (Domain Name System) translates human-readable domain names (google.com) into machine-readable IP addresses (142.250.80.46). It is the phonebook of the internet.
Common DNS Record Types
- A: Maps a domain to an IPv4 address (e.g. 93.184.216.34)
- AAAA: Maps a domain to an IPv6 address
- CNAME: Alias from one domain to another (www → example.com)
- MX: Mail exchange servers with priority values
- TXT: Arbitrary text, often used for SPF, DKIM, domain verification
- NS: Authoritative nameservers for the domain
- SOA: Start of Authority — primary NS, admin email, serial, timers
- PTR: Reverse DNS — maps an IP back to a domain name
DNS-over-HTTPS
This tool uses Google's public DoH endpoint (dns.google/resolve) to perform lookups directly from your browser. DoH encrypts DNS queries over HTTPS, preventing eavesdropping compared to traditional plaintext DNS (port 53).
Common Use Cases
When you need DNS lookups
Domain Migration Verification
After changing DNS providers or migrating a domain, verify that A, CNAME, MX, and NS records point to the correct targets before and after TTL expiry.
Email Deliverability Debugging
Check MX records to confirm mail routing, TXT records for SPF and DKIM, and ensure no conflicting records that cause mail to be rejected or marked as spam.
SSL Certificate Validation
Verify CNAME or TXT records required for domain validation by certificate authorities (Let's Encrypt, AWS ACM). Confirm propagation before requesting cert issuance.
CDN & Load Balancer Setup
Confirm CNAME or A records point to CDN endpoints (CloudFront, Cloudflare) and verify NS delegation for sub-domains used by third-party services.
How to Use This DNS Lookup Tool
Step-by-step DNS queries
This tool queries Google's public DNS-over-HTTPS (DoH) API directly from your browser. No server-side proxy is involved — your browser makes HTTPS requests to dns.google.
Single Domain Lookup
Enter a domain name and select one or more record types. Press Enter or click Lookup. Results display each answer with its name, type, TTL (time to live in seconds), and value. Response time is measured from your browser to Google's DNS server.
Batch Lookup
Toggle Batch mode to query multiple domains at once. Enter one domain per line or separate with commas. Each domain is queried for all selected record types. This is useful for auditing DNS across multiple properties or checking propagation for several sub-domains.
Understanding TTL
TTL (Time To Live) indicates how long DNS resolvers should cache the record. A TTL of 300 means 5 minutes of caching. After changing a record, you may need to wait for the old TTL to expire before the new value propagates worldwide. During migrations, lower TTL beforehand to speed up propagation.
Response Time
The displayed response time measures the round-trip from your browser to Google's DoH API. It includes network latency and Google's internal DNS resolution time. Typical times range from 20-100ms depending on your location.
Frequently Asked Questions
DNS lookup explained
Frequently Asked Questions
Security & Privacy
How your queries are handled
DNS queries are sent from your browser directly to Google's public DNS-over-HTTPS API (dns.google). No data passes through OpenKit.tools servers.
- Encrypted in transit: All queries use HTTPS, preventing network-level eavesdropping.
- No server proxy: Your browser connects directly to Google DNS. We have no backend that handles or logs your queries.
- No storage: Domain names and results are not saved, logged, or tracked by OpenKit.tools. Refresh the page to clear everything.
- Google's privacy policy applies to queries sent to their DoH endpoint. See dns.google for details.
Safe for checking production domains, sensitive infrastructure, and pre-launch configurations.
By the Numbers
Performance metrics