Domain verification records

Looks up the TXT records at the domain's apex through the public resolvers and matches each one against a fixed, versioned list of verification formats (Google, Microsoft 365, Atlassian, Facebook, Apple and more), with the service and the full token. More than one token for a service is reported. Records under subdomains are not looked up.

Updated 2026-10-28

Free, no account, nothing is stored

What this tool checks

The TXT records at the domain are looked up through public resolvers, and each record is matched by its prefix against a fixed list of verification formats:

  • Tokens: the service, the prefix and the whole record.
  • Duplicates: more than one token for the same service.
  • None: no record matches a known format (TXT_VERIFICATION_NONE).

How to read the result

The table lists each token with its service. The tokens are public DNS data, so they are shown in full.

Limitations

  • Only the domain itself is looked up. Verification records under subdomains, such as _github-challenge-... or _amazonses, are not covered.
  • Services that are not on the list are not recognised; their records count only in the total number of TXT records.

Use it from code

API reference for Domain verification records

curl -i "https://api.lookproof.dev/v1/dns/txt-verification?domain=example.com"

A request without payment is answered with 402 Payment Required and the exact price. See the API reference.

Limits

InputDomain
Deadline10 seconds
FreshnessUp to 5 minutes, never longer than the record TTL
Price$0.01 per check

Findings this tool can report

DNS (3)
Check (1)
Txt (3)

Frequently asked questions

What is a verification record?

A TXT record that a service asks you to publish to prove that you control the domain, such as google-site-verification=... or MS=ms12345678. The service looks it up once, or from time to time, and then trusts your account with the domain.

Can I delete old tokens?

Usually, once the service no longer needs them. Some services check the record again later, so ask the service first. Several tokens for one service are often leftovers: TXT_VERIFICATION_DUPLICATE.

Does a token mean the service is in use?

No. It shows that someone set the service up once. TXT_VERIFICATION_FOUND lists the services so you can check them.