DOMAIN AND NETWORK TOOLS

Check your DNS. Find the source of the problem.

Compare DNS records and check your domain, SSL certificate and connection in one place.

DNS Check

Advanced options 2/56 selected

Enter one record per line. A match requires the complete record set; extra or missing records count as different. For MX, include both priority and server name. Leave this blank to view records without comparing them.

DNS resolvers 2/56 selected

Results appear as they become available. Querying many servers can take a few minutes.

Servers in Türkiye12
Global providers4
Other countries40

No servers match your search.

Country and city labels are provider inventory information, not verified measurement locations. Queries run from the application server.

Google and Cloudflare are selected by default. Change resolvers and expected records in advanced options.

Security verification

Checked by Cloudflare to limit automated queries.

Turkey DNS propagation map

Explore results from your selected Turkish resolvers by city.

The map shows approximate city locations from the inventory. Queries originate from the application server; these are not independent measurements from those cities.

Select Turkish resolvers to see results on the map.

02 / RESULTS

Query results

Your results will appear here

Enter the information above and start the query.
Data will appear here when it is ready.

Your query is running

Complete the verification above if needed. Your previous results are preserved.

New results are added to the list as they arrive.

What would you like to check?

Continue with the right tool for your needs.

Understand your results

Glossary

IP details

Security verification

How do you check DNS propagation?

After changing a DNS record, enter the domain, record type and new expected value. For example, if you changed your A record to 8.8.8.8, enter 8.8.8.8 in the expected records field and select the resolvers you want to check.

For multiple A, AAAA, NS or MX records, enter each record on a separate line. Order does not matter. Use 10 mail.example.com for MX. TXT chunks within a single record are joined; case and whitespace remain significant.

Matches: the record set is exactly as expected. Different: extra, missing or different values; this alone does not prove the record is old. Not found: the domain or requested record type has no records. Query unavailable: a timeout or provider error; this does not mean the record is missing.

TTL specifies how long the resolver may cache a record, in seconds. The displayed TTL is from the time of measurement. It is not a countdown or a completion time for the entire internet. The application caches responses for up to 60 seconds, bounded by the record TTL. Cached results keep the original measurement time.