Skip to main content
InfoDNSOWASP A05:2021CWE-200

How to fix: Accumulated SaaS domain-verification TXT records

The domain publishes verification TXT records for five or more distinct SaaS vendors. They match the site-verification, domain-verification, verify and challenge shapes those services use.

Why it matters

The set is a public list of the SaaS platforms this organisation has onboarded, which is directly useful for a targeted phishing campaign: a message naming the exact tools someone actually uses is far more convincing than a generic one. Tokens for services that were trialled and abandoned are worse than useless, because they can leave a dormant claim on the domain inside a vendor account nobody monitors any more.

Verification records are meant to be temporary for many vendors and permanent for a few, and nothing ever prompts you to remove the temporary ones, so they accumulate over years. This is informational: their presence is not a vulnerability. It is a prompt to audit which of these services are still in use, and to close the accounts behind the ones that are not, because a live verification token plus an abandoned account is a standing claim on your domain.

How to fix it

  1. 1List the verification records and match each one to a service that is still in use and still owned by someone.
  2. 2Remove tokens for services that were trialled or retired, and close the corresponding vendor accounts rather than only deleting the record.
  3. 3Where a vendor supports it, prefer a scoped subdomain token over an apex TXT record so the inventory is not published at the apex.

Code examples

List what is published

bash
dig +short TXT example.com | grep -i -E 'verification|verify|challenge'

References

Detected automatically by VulnRadar. The check id is dns-txt-verification-tokens-stale, stable across every scan so you can filter or diff on it.

See every dns check

Questions

How severe is Accumulated SaaS domain-verification TXT records?
VulnRadar rates this info severity in the dns category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id dns-txt-verification-tokens-stale, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Accumulated SaaS domain-verification TXT records map to?
It maps to CWE-200. In the OWASP Top 10 it falls under A05:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for accumulated saas domain-verification txt records

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Accumulated SaaS domain-verification TXT records | VulnRadar