DNSPeek Inspect DNS configuration and resolver behavior.
The DNS servers in use, and whether each one answers.
- Status
- Available now
- Price
- Free · MIT license
- Requires
- macOS 13 or later
- Permissions
- None
- Network
- Only when you run a check
- Account
- Not needed
- Telemetry
- None
The problem
Pages hang or a domain will not resolve. Which DNS servers is your Mac actually asking, and are they answering?
The solution
DNSPeek shows the DNS servers macOS uses for ordinary lookups, the interface and reachability behind them, search domains and the other resolvers (per-domain and multicast). Press Run lookup to resolve a name through macOS and to ask each server directly. It also lists /etc/hosts entries and /etc/resolver files, the usual reason a domain resolves to the wrong address, and says when one applies to the name you look up. It is read-only and never changes DNS settings or those files.
Features
- Local overrides /etc/hosts entries someone added and /etc/resolver per-domain resolvers, with a warning next to a lookup they affect
- The DNS servers in use, in order, with their interface and reachability as macOS reports it
- Search domains, per-domain resolvers, and the multicast (.local) and scoped resolvers explained
- Run lookup resolve a name the way apps do, then ask each server directly and see who answers, how fast and with what status
- Only the name you type is ever queried, only when you press the button
- Read-only it never changes DNS settings
- Copy the configuration for a support thread
How it works
- Open DNSPeek from the launcher.
- Read the DNS servers in use.
- Press Run lookup to test a domain against your resolver and each server.
Privacy
- Reads
- The system resolver configuration (scutil --dns); DNS lookups only when you press Run lookup
- /etc/hosts and the files in /etc/resolver (read-only)
- Access
- None.
- Network
- Nothing about your Mac is sent to any server, and there is no account and no telemetry. DNSPeekmakes network requests only when you ask it to run a check. The name you type is sent to your Mac's DNS servers, which are often outside your home network (a public resolver or your ISP).
Installation
DNSPeek is part of MacPeek. Install MacPeek, open Manage utilities and make sure DNSPeek is switched on (it is on by default). There is nothing separate to download.
Open source
MacPeek and every utility in it are MIT-licensed. Read the code on GitHub, or see how a utility is built.
Frequently asked questions
What does DNSPeek do?
DNSPeek shows the DNS servers macOS uses for ordinary lookups, the interface and reachability behind them, search domains and the other resolvers (per-domain and multicast). Press Run lookup to resolve a name through macOS and to ask each server directly. It also lists /etc/hosts entries and /etc/resolver files, the usual reason a domain resolves to the wrong address, and says when one applies to the name you look up. It is read-only and never changes DNS settings or those files.
What does DNSPeek read from my Mac?
The system resolver configuration (scutil --dns); DNS lookups only when you press Run lookup; /etc/hosts and the files in /etc/resolver (read-only).
Does DNSPeek need any permissions?
None.
Does DNSPeek send my data anywhere?
No information about your Mac is sent anywhere, and there is no account and no telemetry. DNSPeek makes network requests only when you ask it to run a check. The name you type is sent to your Mac's DNS servers, which are often outside your home network (a public resolver or your ISP).
Is DNSPeek free?
Yes. DNSPeek is part of MacPeek, which is free and open source under the MIT license.
Related guides
Get DNSPeek with MacPeek.
Free and open source.