Read the TXT records published under a domain name

For web teams checking a launch or tracing a fault, this test provides an immediate point of reference. Read the TXT records published under a domain name.

Read the TXT records published under a domain name. The result highlights the live configuration and the clues that matter for diagnosis.

How to use

Type the domain whose text records you want to read.
Run the lookup and let the answer load on the page.
Go through the values returned and find the one you are after, often a long character string.
Copy that value if you need to compare it with the string another service gave you.
Clear the field to move on to another domain or to check a recent change.

Example

You need to confirm that a verification value has been added for a domain. Run the lookup and compare the string on screen with the expected one, character by character; the smallest difference will stop the verification from working.

Limits and formats

A domain can publish several TXT records, and the tool lists them all without telling you which one serves which purpose.
The value must be compared as it stands: a stray space or a line break is enough to make a verification fail.
A long value can be split into several strings by the DNS, so take that splitting into account before assuming a mistake.

Where processing happens

The domain you pass is handled by the YOORfree server, which queries the public DNS itself and hands back the text records it finds. No file is uploaded, only the domain string travels with the query.

Frequently asked questions

Why do several TXT records show up for one domain?

A domain can publish as many text records as it needs, each one used for a different purpose. The result lists all of them, and you have to pick out the value you are looking for.

Do letter case and spaces matter?

Yes, a text value is compared character by character. Copy it exactly as shown, without adding a space at the start or the end, or the service that checks it may reject it.

Can I confirm here that a record has been removed?

Run the lookup again: if the value no longer appears, it is not published at that moment. A cached copy may still linger elsewhere for a while, depending on the resolvers involved.