Nomlen logo
Free Tool· 8 record types · global propagation

DNS lookup tool check any domain's records

Look up A, MX, TXT, NS and every other record in one shot — with email health scoring built in.

8 record typesEmail health scoreNo login needed
Look up any domain’s DNS records
Try google.com, github.io, or your own domain.
DNS checker features

A complete DNS lookup tool

Every record type, every region, one page.

8 record types

A, AAAA, CNAME, MX, TXT, NS, SOA, and SRV records — all queryable from a single input, with no command line needed.

Global propagation view

See how your records have propagated across DNS servers worldwide and spot regions still serving stale data.

Migration verification

Just changed hosts or updated nameservers? Confirm the new records are live everywhere before you announce the move.

Parsed record details

TTLs, priorities, and targets laid out in readable tables instead of raw dig-style output.

Stop second-guessing.

Find your domain in the next 30 seconds.

Free forever. No login required. 1,100+ TLDs in one query — plus AI suggestions and the premium marketplace.

1,147
TLDs
200ms
Avg lookup
100
Suggestions/query
FAQ

DNS checker FAQs

DNS propagation is the time it takes for your DNS changes to spread to resolvers worldwide. It is governed by the record's TTL: a 300-second TTL means about five minutes, while 86400 seconds can mean up to 24 hours before every resolver serves the new value.
Query the domain from DNS servers in many locations and compare answers — that is exactly what a propagation checker does. When servers across regions return your new record, the change has fully propagated and you can stop waiting. Lower the TTL a day before big changes so propagation completes faster.
An A record maps a hostname directly to an IPv4 address; a CNAME maps a hostname to another hostname, which is then resolved. You cannot use a CNAME at the domain apex — that is why roots use A records and www often uses CNAME.
MX records tell the internet which servers accept email for your domain, with priority numbers setting the order — lower number, higher priority. If the primary mail server is down, senders fall back to the next MX entry in line.
Resolvers cache answers for the record's TTL, and they do not all refresh at the same moment. A resolver that cached the old answer shortly before your change may keep serving it until that cache expires, while another network queries the authoritative server immediately. This is normal during propagation; compare several resolvers and wait for the previous TTL before concluding that a change failed.
No. A CNAME says that a hostname is an alias for another hostname, so it cannot coexist with an A, AAAA, MX or TXT record at the same name. This rule causes a common problem at the bare domain, where mail and verification records may also be required. Use an A or AAAA record there, or a provider-supported ALIAS or flattening feature.
Start with MX records to confirm where mail should be delivered, then inspect TXT records for SPF and DMARC policies. DKIM uses selector-specific TXT or CNAME records rather than one universal record. A missing MX record, an SPF record that does not authorize the sending service, or a strict DMARC policy can each cause delays, spam-folder placement or outright rejection.