Look up mail exchanger records for any domain — free, instant, no sign-up. Enter a domain name to see its live domain’s mail servers and their priority, useful for troubleshooting email, websites and domain moves. Results come straight from the DNS system, with TTL values shown so you know how long resolvers will cache them.
What does this tool do?
The mx record lookup queries live DNS for a domain and shows mail exchanger records. It is the fastest way to answer “where does this domain point?” — whether you are checking that a website migration pointed the A record correctly, verifying that MX records will deliver email after a move, or confirming TXT records for domain verification. Results come straight from the DNS system, with TTL values shown so you know how long resolvers will cache them.
Because it reads live data — your actual connection, the domain’s actual records — the answer reflects right now, not a cached guess. Re-check after changes (new router, DNS update, browser upgrade) to confirm they took effect.
The interface keeps things practical: the inputs are “Domain name” and “Record type”; the “rtype” control offers “A (IPv4)”, “AAAA (IPv6)”, “CNAME”, “MX (mail)”, “NS (name servers)”, “TXT (SPF, verification)”, “SOA” and “CAA” and more; “Look up” runs the tool. Results update live as you work — there is no waiting and nothing to submit.
How do I use this tool?
The answer appears as soon as the page loads; use the steps below to interpret it or dig deeper.
- Type the domain name (e.g. example.com) into the input field.
- Run the lookup.
- Read the records, TTL values and resolved IP addresses.
- Re-run after DNS changes to confirm they have propagated.
How does it work?
The tool sends a DNS-over-HTTPS query to a public resolver and parses the JSON response into a readable table. Because it queries live DNS rather than a cached database, the answer reflects the domain’s current configuration — including recent changes, subject to each record’s TTL. Multiple record types are fetched so one lookup covers web, mail and verification records together.
Live lookups query the same public infrastructure your browser uses — DNS resolvers, TLS handshakes, registry data — so answers reflect the internet as it is right now. Browser-reported values come straight from the APIs your browser exposes to every site.
Use cases in Pakistan
Pakistani freelancers and agencies use DNS lookups on every site migration: confirming a client’s domain points to the new host before cancelling the old one, checking MX records so business email keeps working during a move, and verifying TXT records for Google Search Console or Microsoft 365 setup. Bloggers diagnose “email going to spam” by inspecting SPF/DKIM TXT records, and buyers check a domain’s name servers before purchase. It is also the first step when a .pk domain stops resolving.
As Pakistan’s internet grows — more fibre, more 4G, more online businesses — these small diagnostics become everyday literacy: the difference between a five-minute fix and an afternoon of confusion when something does not load.
Limitations
Results reflect public DNS as seen by the resolver used — your ISP’s cache may differ until the TTL expires, so “not updated yet” usually means propagation, not an error. The tool reads public records only; it cannot see private internal DNS or diagnose server-side problems beyond what DNS publishes. DNSSEC validation status is not checked here.
Networks are dynamic: IPs change, DNS propagates, certificates renew. A reading is a snapshot — re-check when diagnosing, and confirm critical changes from a second vantage point (mobile data vs Wi-Fi) when it matters.
Frequently asked questions
How long does DNS propagation take?
As long as the record’s TTL (often 5 minutes to 24 hours), plus ISP caching. If this tool shows the new value but your browser shows the old site, wait out the TTL or flush local DNS. If a reading looks wrong, re-check from a second connection (mobile data vs Wi-Fi) — comparing the two usually reveals whether the issue is local or general.
What is a TTL?
Time To Live — how long resolvers may cache a record, in seconds. Lower TTLs (e.g. 300) propagate changes faster; higher ones reduce lookup load. It is shown beside each record above. Screenshot or copy the result when reporting issues; precise technical details get faster, better support responses than descriptions.
Why do my MX records matter?
MX records tell the world where your domain’s email is delivered. Wrong MX records mean lost email — always verify them after moving email providers or hosts. Re-run after any change — new router, DNS edit, browser update — to confirm the change actually took effect.
The lookup shows nothing. Is the domain broken?
Possibly the domain is unregistered, expired, or has no records of that type. Check the spelling, try the plain domain without www, and confirm the domain is registered. If a reading looks wrong, re-check from a second connection (mobile data vs Wi-Fi) — comparing the two usually reveals whether the issue is local or general.
Is my lookup private?
The domain you query is sent to a public DNS resolver to fetch its public records — that is how DNS works. Nothing else about you is stored. Screenshot or copy the result when reporting issues; precise technical details get faster, better support responses than descriptions.
Can I check .pk domains?
Yes. The tool works for .pk, .com.pk and any other public TLD, since it queries the global DNS system. Re-run after any change — new router, DNS edit, browser update — to confirm the change actually took effect.
Updated October 2026 · Built and tested by Sharjeel Tahir · How our tools are tested