Cloudflare
DNS over HTTPSWaiting for a response
Systems, SaaS, websites and landing pages built around your project.
Discuss my projectHosting, domains, email and security for your online presence.
Explore Zovvi CloudDigital marketing, campaigns and paid advertising to connect with your audience.
Discuss my projectTell us what you need. We’ll help you find the next step.
WhatsApp+55 (11) 99149-8980[email protected]Your services, invoices and support in one place.
Sign in to the Client PortalView invoicesAccess your invoices through the portal.DNS propagation checker
Check where your domain points with lookups from several countries. Compare what each network point receives and see whether the new value appears.
Waiting for a response
Waiting for a response
TTL is the cache time reported in the response, in seconds. It is not a countdown to complete propagation.
This lookup compares Cloudflare and Google. It does not represent every country or internet provider.
Your browser queries Cloudflare and Google Public DNS over HTTPS. The network selects the serving endpoints; we do not measure specific geographic locations.
Look up the A record to check your website’s IPv4 address. If your provider supplied IPv6, choose AAAA.
Use MX to see which servers receive your domain’s email. This lookup does not test sending or message delivery.
Look up TXT for the name given by the service. SPF, DKIM and DMARC may use different names and records.
Check that it matches your provider’s instructions. Other caches may still return a different response.
Compare the values and TTL. CDNs and load balancing can also cause differences; it does not always mean an error.
Check the name and record type. A network failure, NXDOMAIN and a missing record are different situations.
Publishing a website or moving to a new host? Explore Zovvi Cloud hosting for your project, with SSL, professional email and a management panel.
Explore hostingThis lookup checks DNS. It does not change records or speed up cache updates.No. They show what the queried probes or resolvers returned at that moment. Other providers and caches may return something different. Without knowing the correct value, matching responses do not confirm a correct configuration either.
This tool does not calculate that time. It depends on caches, the previous TTL, delegation and configuration. The displayed TTL belongs to the response received; it is not a clock for the entire internet.
Yes. Enter its full name, such as www.example.com or _dmarc.example.com. Each name and record type is queried separately.
The resolver reported that the queried name does not exist. Check the spelling, zone and delegation. That response may be cached and is different from a connection failure when contacting the lookup service.
Caches updated at different times are one possibility. Services using CDNs, geographic distribution or load balancing may also return different sets. Compare them with the configuration provided by whoever manages the domain.
No. It only reads public DNS responses. To change records, use the panel managing your DNS zone. Website access, SSL certificates and email delivery require separate checks.