DNS Tools

DKIM Snapshot — Current TXT from DNS History

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

How to Use This Tool

  1. Enter the domain or hostname whose DNS you want to snapshot.
  2. dns-history queries multi-type records including TXT at that label.
  3. TXT answers appear in records and byType.TXT arrays.
  4. summary and emailAuth blocks aid mail authentication triage.
  5. queriedAt timestamps capture; note states snapshot scope.
  6. Diff archived exports to track TXT changes during DKIM rollout.

About This Tool

DKIM selectors live in TXT at names like selector._domainkey.example.com, yet operators searching DKIM propagation checker expect worldwide resolver grids. VSPIC DKIM propagation checker runs dns-history with lookupAllDnsRecords on the domain you enter, returning TXT strings in records and byType, summary flags, emailAuth context, queriedAt, and note that this is a current public DNS snapshot — not geographic resolver polling or automatic DKIM selector discovery across every vendor path.

Filter TXT for DKIM-related material at the queried name and in the full export. Archive JSON before and after selector publishes, diff TXT over hours during mail onboarding, and pair with dkim-record-checker when you need structured validation on a specific selector. We do not claim global propagation percentage — snapshot honesty only.

Common use cases

  • View all DNS records of a domain after migration
  • Confirm DNS records after domain changes
  • Test for DNS leaks when using a VPN
  • Debug email delivery with MX and TXT records

Why use VSPIC for ?

  • TXT visible in full zone snapshot context.
  • queriedAt evidence for mail authentication change tickets.
  • Honest framing — no fake global propagation map.
  • Same dns-history path as other propagation siblings.
  • Free export-friendly JSON for diff scripts.
  • Holistic mail DNS alongside MX and DMARC in one export.

Honest scope — DKIM snapshot not global poll

True DKIM propagation testing polls many recursive resolvers for TXT at each active selector. dns-history returns one current public snapshot at the name you submit — all TXT strings returned for that label plus related zone context.

This page confirms what publishes now from our lookup path and supports timed exports you diff yourself — not a worldwide propagation percentage UI.

Finding DKIM material in dns-history output

Scan byType.TXT or records for strings typical of DKIM public keys. summary and emailAuth may surface mail authentication context when parsers detect related material at the queried name.

Most ESPs publish DKIM at selector._domainkey.yourdomain — query that full hostname in the tool when the apex snapshot lacks selector TXT.

DKIM onboarding and selector rotation workflow

Before publishing a new selector: snapshot baseline TXT at the selector label. Publish DNS. Snapshot hourly; diff until public key TXT matches your vendor panel. Send signed test mail after TXT stabilizes in your exports.

Rotation often requires overlapping selectors — archive both selector exports until receivers confirm the new key.

TTL and receiver cache behavior

Major receivers cache DKIM TXT independently. Authoritative update may precede receiver visibility. Wait TTL multiples; re-snapshot and inspect Authentication-Results on live mail.

Pair with DNS TTL checker on the selector hostname when estimating delay.

Why dns-history for DKIM checks

Full snapshot places DKIM-related TXT beside MX, apex SPF, and _dmarc context in exports from apex queries — mail cutovers need holistic documentation. API action dns-history with domain parameter.

Dedicated DKIM checker tools validate one selector with structured found and valid flags; propagation family uses snapshot exports for migration evidence.

Validation limits of snapshot-only checks

Seeing TXT publish does not prove valid RSA/Ed25519 syntax, selector alignment with outbound signing, or that all sending paths sign. Follow with dkim-record-checker and live mail headers.

Empty DKIM TXT at the queried name means none returned on this path — confirm you entered the correct selector hostname.

Relationship to DMARC and SPF propagation pages

DMARC and SPF propagation siblings share dns-history backend with record-type-focused SEO. JSON is identical full snapshot — filter DKIM-related TXT in scripts when diffing.

Run all mail authentication snapshots during major DNS migrations for correlated evidence.

API automation

GET /ip-tools/api/extended?action=dns-history&domain=selector._domainkey.example.com. Extract TXT public key material. Alert when string differs from approved baseline during change windows.

Schedule hourly jobs on each active selector label during onboarding.

Receiver-side propagation reality

Gmail, Microsoft, and regional providers refresh TXT on their own schedules. No single snapshot proves all receivers updated. Combine timed exports, TTL awareness, and signed test messages.

Document honest limits in stakeholder emails to avoid false confidence after one clean scan.

Important notes & limitations

  • NOT global resolver DKIM polling worldwide.
  • Single lookup path — one public resolver vantage.
  • Does not scan all selector._domainkey labels automatically.
  • Enter the selector hostname directly when DKIM lives on a subdomain.
  • Does not validate DKIM key syntax or signing alignment.
  • Receiver caches may use old TXT until TTL expires.

Frequently Asked Questions

Yes. VSPIC offers this DKIM 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.

DKIM usually lives at selector._domainkey.yourdomain. Enter that full hostname — the apex snapshot does not enumerate every selector automatically.

It shows published TXT. Deep syntax and selector validation use dkim-record-checker and live signed mail tests.

Archive repeated dns-history exports at each selector label, diff TXT over time, wait TTL cycles, and verify Authentication-Results headers.

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

Next step for your check

Continue with dkim record checker on VSPIC.

DKIM Record Checker

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