Stays with the sender
The private key
The private key stays in your DKIM signer or a dedicated HSM or cloud KMS key and is not exported.
Product · Authority Anchor
The sender’s public key sits in its own DNS, so any verifier can check its Trust Packets with no prior integration.
2026q1.
For illustration.
01 · What it is
Like a passport, a Trust Packet™ needs no prior API relationship and no bilateral agreement.
The sender publishes its public key in its own DNS. Any verifier can look it up, check the signature on a packet, and decide whether it trusts that domain.
What it proves
02 · The lookup
When a Trust Packet arrives, the verifier reads the record from DNS, through more than one resolver, before it checks anything else.
Everything delegated beneath a revoked key is refused with it.
03 · Key custody
Stays with the sender
The private key stays in your DKIM signer or a dedicated HSM or cloud KMS key and is not exported.
Published in DNS
A DNS TXT record at the DKIM location. No shared secret, no API key exchange, no integration built between the two parties beforehand.
Where it ends
If an attacker controls the signing infrastructure, UniKey does not defeat that. A device approval above a threshold closes most of the gap.
04 · Read it, watch it
The specification
Key discovery and validation in DNS, and the steps a verifier runs before it trusts a key.
Open the RFC seriesRecorded demo
The verifier finds the supplier’s key in DNS before the bank change is checked.
See it workThe other parts
How it works, start to finishPilot
No live customer data sits on UniKey systems.
A UniKey property. © 2026 Swoop In Technologies LLC