See whether your TXT record change has spread: 12 public resolvers, queried live, side by side.
Map key: each dot is the country where a resolver's operator is headquartered (number = resolvers), coloured by result. It does not show where the query ran — most of these resolvers are anycast networks with servers in many cities.
These are 12 large public resolvers, queried live over encrypted DNS-over-HTTPS from our servers. Most are anycast networks with many locations, so we show which resolver answered — not a city. Two (CIRA Canadian Shield) are run by the organization that operates .ca. Your ISP's resolver may still show an older answer until its cache expires.
TXT records hold free-form text. They are used for SPF, DKIM and DMARC email authentication and for domain-ownership verification by Google, Microsoft, Facebook and others.
Type your domain in the box above, keep TXT selected and press Search. We ask 12 public DNS resolvers — including two run by CIRA Canadian Shield — at the same moment and show each answer side by side.
Green rows should each show your new text value. A domain can have many TXT records; resolvers may list them in different order, which is fine. If your verification string is missing on some rows, wait for the TTL and re-check before retrying verification.
v=spf1) on one domain — only one is allowed; merge them.Usually minutes, up to the TTL for edits to an existing record.
The verifier's resolver may not have it yet. Check all 12 resolvers here, wait a few minutes and retry.
Yes, many — but only one SPF record.