VSPIC
Developer Tools

TXT Snapshot — Current Records from DNS History

Current TXT snapshot from dns-history — not multi-resolver global propagation polling

How to Use This Tool

  1. Enter the domain or hostname whose TXT you want to snapshot.
  2. dns-history queries multi-type records including TXT.
  3. TXT strings appear in records and byType.TXT arrays.
  4. summary.txtCount summarizes volume for quick triage.
  5. queriedAt timestamps capture; note explains snapshot limits.
  6. Diff archived JSON to track TXT changes during propagation windows.

About This Tool

TXT records carry SPF, site verification, DKIM keys, and DMARC-adjacent strings — yet TXT caches propagate unevenly across resolvers. VSPIC TXT propagation checker runs dns-history, returning all TXT strings in records and byType.TXT, summary.txtCount, queriedAt, and note that this is a current public DNS snapshot — not a worldwide propagation heatmap or passive DNS archive.

Review published TXT at query time, archive exports before and after verification token or SPF edits, and diff over hours during rollouts. We are explicit: snapshot honesty only, not fake global polling.

Common use cases

  • •Inspect HTTP headers and user-agent strings
  • •Analyze email headers for phishing investigation
  • •Generate strong passwords for staging environments

Why use VSPIC for ?

  • All TXT strings at the queried name in one snapshot.
  • summary.txtCount for quick volume checks.
  • queriedAt evidence for verification and auth change tickets.
  • Honest framing — no misleading global map.
  • Full zone context when querying apex labels.
  • Free export-friendly JSON structure.

Honest scope — TXT snapshot not global poll

True TXT propagation testing polls many recursive resolvers for string agreement. dns-history returns one current public snapshot — every TXT answer at the queried name from our lookup path.

Repeated snapshots you save approximate propagation tracking without a fake worldwide percentage UI.

Reading TXT from dns-history output

byType.TXT lists each string with host and TTL when returned. summary.txtCount indicates how many TXT rows appeared. SPF, site verification, and DKIM material may coexist — filter by prefix or content.

queriedAt attaches to change tickets. note reiterates snapshot versus historical archive distinction.

TXT migration and verification workflows

Before adding Google or Microsoft verification TXT: snapshot baseline. Publish new string. Snapshot hourly; diff until expected token appears. Remove old token only after services confirm verification.

SPF and DMARC also live in TXT — use sibling propagation pages when those are the primary focus.

TTL and cache effects on TXT

Receivers and CDNs cache TXT independently. Authoritative update may precede visibility elsewhere. Wait TTL multiples; re-snapshot before closing verification tickets.

DNS TTL checker on the affected hostname helps estimate delay.

Why dns-history for TXT checks

Full snapshot places TXT beside MX, NS, and A in apex exports — holistic cutover documentation. API action dns-history with domain parameter.

Dedicated txt-record-lookup queries TXT only; propagation family uses full snapshot for migration evidence.

Multiple TXT records at one name

DNS allows many TXT strings at the same owner name. Snapshots list all returned — do not assume a single string. Verification tokens often coexist with SPF.

Accidentally deleting unrelated TXT during edits is a common outage cause — diff exports to catch collateral changes.

Relationship to SPF and DMARC propagation pages

SPF and DMARC propagation siblings filter SEO language for mail authentication. Backend is identical dns-history — JSON is the full snapshot.

Filter v=spf1 and review _dmarc via emailAuth when mail-focused.

API automation

GET /ip-tools/api/extended?action=dns-history&domain=example.com. Parse byType.TXT. Alert when sorted TXT set diverges from approved baseline during change windows.

Store exports in Git for TXT change audit trails.

Sensitive TXT in exports

Verification tokens and DKIM public keys in snapshots are sensitive in aggregate exports. Treat files like credentials-adjacent reconnaissance data.

Public DNS already exposes TXT — snapshots consolidate for convenience.

Important notes & limitations

  • NOT global resolver TXT polling worldwide.
  • Single lookup path — one resolver vantage.
  • Multiple TXT strings require manual identification by purpose.
  • Does not validate SPF, DKIM, or verification token semantics.
  • Long TXT split across strings shown as resolver returns them.
  • External caches may serve old TXT until TTL expires.

Frequently Asked Questions

Yes. VSPIC offers this TXT propagation checker at no cost with no account required. Results load in real time.

We do not permanently store your queries on our servers. Some tools run entirely in your browser; others fetch public data for the request only.

Yes. Open the page in any modern phone or tablet browser. Results work on Wi‑Fi and mobile data.

No. dns-history returns a current TXT snapshot from one public lookup path — not worldwide propagation polling.

dns-history with a domain parameter.

Archive repeated dns-history exports, diff TXT strings over time, wait TTL cycles, and confirm dependent services accept the new values.

It shows published TXT strings. Deep validation uses SPF checker, DMARC checker, and vendor verification panels.

DNS allows multiple TXT at one name. Snapshots list all returned — identify each by content or prefix.

No. Only current DNS at query time. Build timeline by saving your own snapshots.

Next step for your check

Continue with txt record lookup on VSPIC.

TXT Record Lookup

Related Tools

Explore more free VSPIC tools for IP, DNS, security, and network diagnostics.

Browse all toolsComparison guides

Trusted by Users Who Value Privacy

Always Free

No premium plan ever

100% Private

Files processed in browser

Instant Results

Convert in seconds

Works Everywhere

Any device, any OS