DNS Lookup

A records map a domain to an IPv4 address (e.g., 93.184.216.34). AAAA records map a domain to an IPv6 address (e.g., 2606:2800:220:1:248:1893:25c8:1946). MX records specify the mail servers responsible for accepting email, including a priority value. NS records define the authoritative name servers for the domain. CNAME records create an alias pointing to another domain name, commonly used for CDN or SaaS custom domains. TXT records store arbitrary text and are used for SPF, DKIM, DMARC, and domain verification codes.

TTL is the number of seconds a DNS record is cached by resolvers before they query the authoritative name server again. For example, a TTL of 3600 means resolvers cache that record for one hour. A shorter TTL (e.g., 300 seconds) causes DNS changes to propagate faster but increases the query load on name servers. A longer TTL (e.g., 86400 seconds / 24 hours) reduces DNS traffic but means changes take longer to reach all users. Before a planned server migration, it is a best practice to lower the TTL to 300–600 seconds 24–48 hours in advance.

DNS changes do not take effect instantly because resolvers around the world cache the previous record until its TTL expires. Even after the TTL has passed, some ISP resolvers may continue serving stale data. Full propagation typically takes from a few minutes (for low TTL records) to 24–48 hours. To speed up the process, lower the TTL of the record before making the change. You can use this tool to check the current value from Cloudflare's perspective, or compare results with other regional DNS checkers.

An AAAA record (often called a 'quad-A record') maps a domain name to an IPv6 address, which is 128 bits long (e.g., 2001:db8::1). An A record maps to a 32-bit IPv4 address (e.g., 192.0.2.1). Most modern servers and hosting providers support both, a setup called dual-stack. When a browser resolves a domain, it typically prefers IPv6 (AAAA) when available. Checking your AAAA record with this tool confirms whether your domain is reachable over IPv6.

Select the TXT record type and enter your domain name. Your SPF record will appear as a string starting with v=spf1. For DKIM, you need to query the selector subdomain (e.g., google._domainkey.yourdomain.com) — enter that full subdomain in the lookup field. For DMARC, query _dmarc.yourdomain.com. If these records are missing or misconfigured, emails from your domain may be flagged as spam or rejected by receiving servers.

MX record priority is a numeric value where lower numbers mean higher preference. For example, if you have MX records with priorities 10 and 20, the sending mail server will first attempt delivery to the priority-10 server. If that server is unavailable, it falls back to the priority-20 server. Google Workspace uses priorities 1, 5, and 10 across multiple ASPMX servers to provide redundancy. Microsoft 365 typically uses a single MX record pointing to your-domain.mail.protection.outlook.com.

Look up the A or AAAA record for your domain using this tool. If it shows the new IP address you configured, propagation has reached Cloudflare's DNS network. To confirm propagation from multiple global locations, you can compare results with regional DNS checkers. Also check the TTL value — if it is still high, some resolvers may still be serving cached data. For email setup, check both the MX record and the relevant TXT records (SPF and DKIM) to ensure complete email deliverability.

Yes. This tool sends DNS queries directly to Cloudflare's DNS-over-HTTPS (DoH) API, meaning all communication is encrypted. The domain names you enter are not stored on our servers. We recommend against entering sensitive internal hostnames or private infrastructure domains, as those queries will be sent to Cloudflare's public DNS resolver.