key-drop.com (A) DNS Records

Type a domain, pick a record type, and watch its DNS answers come back from resolvers across the globe.

Results 0 / 18
Enter a domain to start

Why people use it

A no-nonsense DNS lookup that just works, wherever you are.

Answers in a blink

Records come straight from public resolvers, so you get live values with almost no wait.

Straight from the source

Queries hit Google, Cloudflare and regional resolvers directly — no stale middle layer.

See it on the map

Watch each location light up as it resolves, so propagation gaps are obvious at a glance.

DNS Checker by the numbers

Active nodes
18
Record types
10
Languages
4
Total lookups
67,476
Total visitors
19,279
Availability
7/24

Checking propagation in three steps

1

Type the domain

Drop in the hostname you want to check, like example.com.

2

Choose the record

Pick A, AAAA, MX, TXT or any other type from the list.

3

Run the check

Hit Check and watch the answers roll in from every region.

The DNS record types, in plain English

A

Maps a domain to an IPv4 address such as 93.184.216.34.

AAAA

Maps a domain to an IPv6 address for modern networks.

MX

Tells the internet which mail servers handle email for the domain.

NS

Lists the authoritative name servers responsible for the zone.

TXT

Holds free-form text, most often SPF, DKIM and domain verification data.

CNAME

Points one hostname at another as an alias.

SOA

Start of Authority — the master record with serial and refresh settings.

PTR

The reverse of an A record: maps an IP back to a hostname.

SRV

Announces the host and port for a service like SIP or XMPP.

CAA

States which certificate authorities may issue SSL certificates for the domain.

Understanding DNS propagation

Every time you point a domain to a new server, update an MX record or add a TXT entry for email, that change has to travel to thousands of DNS resolvers around the world. Until it does, some visitors reach the new destination while others still land on the old one. That in-between window is what people mean by DNS propagation.

Because resolvers cache answers for the length of a record's TTL, propagation isn't instant. A low TTL set a day before the change means most caches refresh within minutes; a long TTL can keep the old value alive for up to 48 hours. Checking the same record from several regions at once is the simplest way to see how far along you are.

When a global lookup helps

  • After moving a site to a new host or IP address.
  • When switching email providers and updating MX or SPF records.
  • While issuing an SSL certificate that depends on a CAA or TXT record.
  • To diagnose why a domain loads for some people but not others.

Run the check, compare the values each location returns, and once they all agree you can be confident the change has fully propagated.

Frequently asked questions

It's the time it takes for a DNS change to reach resolvers everywhere. Depending on your TTL it can be a few minutes or up to 48 hours.

Some resolvers have already picked up the new record while others are still serving the cached one. That's propagation in progress.

Yes. Choose the AAAA type to look up a domain's IPv6 addresses from every location.

Make sure the domain is registered, its name servers are set correctly and the record you're checking actually exists in the zone.

Lower the record's TTL a day or two before you make the change. Caches will expire sooner and pick up the new value faster.

Completely. There's no sign-up, no limits and no cost — check as many domains as you like.

Get in touch

Questions, feedback or a bug to report? Send us a message.

0 / 1000