tamper[box]

SaaS Stack from DNS

Find service clues in public DNS.

Records read locally · lookups on our server

    Services

      Every TXT record

      Findings

        Capabilities and processing

        Enter a domain or paste TXT records (bare values, quoted strings or dig output). A domain is sent to our server, which reads its public TXT records; pasted records are read in your browser.

        Verification tokens are matched against more than 30 services and grouped by what the service is for, each with the token that names it. The mail services in the SPF record are listed separately, and tokens that look like verification records for services not in the catalog are kept apart.

        Example workflow

        The page opens on harbor-supply.example, a sample domain with verification tokens for six services. Google appears twice. Multiple tokens may represent legitimate accounts; ownership and current use cannot be inferred from DNS alone.

        Limits and interpretation

        A token shows that someone with DNS access once connected the domain to an account, not that the account is still in use. Services that verify with a CNAME or a subdomain record are not read. Nothing is stored.

        Related tools

        All tools · Privacy