Check TXT records instantly across multiple global resolvers to validate your domain's text strings.
TXT records are heavily used to verify domain ownership and enforce email security. Enter your domain name above to instantly query its active TXT records. This tool helps you quickly spot missing SPF records, broken DMARC policies, or unverified third-party services.
v=spf1, your email delivery will fail. A domain must only have one SPF record. If you need to authorize multiple services, you must merge them into a single string._dmarc.yourdomain.com. Similarly, DKIM uses selectors (e.g., selector._domainkey.yourdomain.com). Query those specific hostnames to find their TXT records.Learn exactly how TXT records are used for SPF, DKIM, and DMARC, and understand the 255-character string limits.
Read the TXT WikiTXT records store free-form text in DNS. They are widely used for email authentication (SPF, DKIM, DMARC), domain verification, and service configuration. TXT values can be long and are often split into 255 character chunks by DNS servers. This lookup shows the combined TXT content so you can verify the exact published string.
Common TXT issues include missing quotes, incorrect include mechanisms in SPF, or publishing multiple conflicting SPF records. DKIM and DMARC are often placed under specific subdomains such as selector._domainkey and _dmarc. Always verify the exact hostname being queried, and ensure the value matches what your provider expects.
If you need related checks, try SPF check lookup and SPF/DMARC record generator validator.
DNS servers split long TXT strings into chunks. The lookup usually joins them for display. The published content is still equivalent as long as the order is correct.
No. You should publish only one SPF record per domain. Multiple SPF records can cause permanent error results and reduce deliverability.
DMARC is published as a TXT record on _dmarc.yourdomain. It does not live at the apex.
The selector might be wrong, or the record is published at the wrong hostname. Check the selector._domainkey.domain format and verify that the selector matches your mail provider settings.
Yes. Many services use TXT records to verify domain ownership. Make sure the value matches exactly and allow for DNS propagation time.
During setup, use a short TTL like 300 seconds. After verification, you can increase TTL to reduce resolver load.