DNS propagation checker.

What propagation really is

DNS changes don't travel outwards like a wave. Resolvers around the world store answers for as long as the record's TTL (time to live) says, then ask again. So after you change a record, each resolver picks up the new value when its stored copy runs out. A record with a one-hour TTL mostly updates within an hour; nameserver changes can take a day or two, because the old values are often stored for longer.

Reading the results

• Matches: this service gives the same answer as your nameserver.
• Different: this service gives another answer, usually the old one. Wait for the TTL to pass.
• No record: this service found no record of this type. Common just after adding a new record.
• No reply: this service didn't answer in time. It says nothing about your domain.

How this check works, and its limits

These are public services run by companies in many countries, but most use many servers worldwide and answer from whichever is nearest to our server. So we list providers rather than cities: claiming "Tokyo has updated" would be guesswork. Visitors using their internet provider's DNS may see the change earlier or later.

Sites on a CDN or large hosting platform can give different addresses to different services, even with no change in progress. That's normal. To see all your records, use the DNS lookup. If email is what you changed, check the SPF, DKIM and DMARC checker too.