Edit Template

Product Authority Anchor

Your domain vouches for your key.

The sender’s public key sits in its own DNS, so any verifier can check its Trust Packets with no prior integration.

Authority Anchor · DNS TXT recordIllustrative

2026q1._domainkey.supplier.example.com. IN TXT "v=DKIM1; k=ed25519; p=EXAMPLEKEYONLY"

Name
A selector, the DKIM key location, then the sender’s own domain.
Type
A TXT record. Any resolver can read it. No account or integration is needed.
Value
The public key. The private key stays with the sender and is not exported.

For illustration.

01 · What it is

Published once. Checked by anyone.

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

Who signed?
The signature matches the key in the sender’s DNS.
From where?
The key belongs to the domain the packet says it came from.
Who decides?
Your verifier decides whether it trusts that domain.

02 · The lookup

What the verifier does with the record.

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.

Key found, signature matches
The first check passes. The verifier moves on to the time window.
No record at that name
REFUSED The action does not run, and the refusal is recorded.
Signature does not match the key
REFUSED A packet signed by any other key is not the sender’s.
The sender removed the record
REFUSED From then on, packets signed with that key are refused. This is how a sender revokes, and it needs no one else.

03 · Key custody

The private key stays with you.

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.

Published in DNS

The public key

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

The boundary

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

Check it yourself.

The specification

RFC-3002 and RFC-3001

Key discovery and validation in DNS, and the steps a verifier runs before it trusts a key.

Open the RFC series

Recorded demo

Watch it in the ERP demo

The verifier finds the supplier’s key in DNS before the bank change is checked.

See it work

Pilot

Try it in a sandbox first.

No live customer data sits on UniKey systems.

A UniKey property. © 2026 Swoop In Technologies LLC

Edit Template