For merchants and companies

Your own domain as a bb84 recipient

Customers and AI assistants pay you at shop.example, not at an address. One TXT record in your DNS zone, secured by DNSSEC, is all it takes, with no account at bb84. This page checks every step and shows you what is still missing.

Check your setup

Enter the domain you want to be paid at. We read your DNS records, build the DNSSEC proof chain the way ENS does, and resolve the domain exactly as the bb84 app will.

The address is on the Keys tab of the bb84 app (0x…). With it we fill in the record below and compare it with what your domain publishes.

How to set it up

Three steps at your registrar or DNS provider. No transaction, no wallet software, no key besides your DNS login.

1

Enable DNSSEC

In your registrar's or DNS provider's settings, switch on DNSSEC for the domain. Many providers sign the zone and publish the DS record for you (Cloudflare, Hetzner, Namecheap, GoDaddy, IONOS with DNS Pro or Domain Guard). If the DNS is hosted elsewhere, you copy the DS record to the registrar.

  • Pick ECDSA P-256 (algorithm 13) or RSA/SHA-256 (8). Ed25519 (15) and SHA-384 (14) cannot be verified by ENS.
  • Publishing can take a few hours. Come back and check.
2

Add one TXT record

Create a TXT record named _ens under your domain (_ens.shop.example) with this content. Put your own bb84 address in it; the field above fills it in for you.

TXT record
ENS1 dnsname.ens.eth a[e42069000]=0x<your bb84 address>

Name: _ens (some panels want the full name _ens.shop.example). Type: TXT. TTL: anything. For a subdomain such as pay.shop.example the record is _ens.pay.shop.example.

3

Wait, then check and test

After the DNS change has propagated (TTL, usually minutes), run the check above until every step is green. Then open the bb84 app, go to Spend and type your domain: it shows “Domain verified via DNSSEC” next to the recipient. An AI assistant connected to bb84 can pay you the same way.

Alternative: import the domain into ENS on-chain

If you already use ENS with your domain or want an on-chain resolver of your own, you can import it instead: TXT _ens.shop.example = a=0x<your Ethereum address>, then app.ens.domains → Import DNS name (one Ethereum transaction). Afterwards set the bb84 address as the address record for coin type 2189552648 (ENSIP-11 for chain 42069000); the Ethereum address record is optional.

Which one?

  1. TXT only (gasless): nothing to pay, changeable any time in your DNS panel, ENS reads the record with its DNSSEC proof on every lookup. Recommended.
  2. On-chain import: costs gas once, records live in an ENS resolver you control, and the name works in every ENS wallet without the DNS gateway.

Questions

Why DNSSEC?

A DNS name exists in ENS only behind a valid DNSSEC proof chain from the root down to your record. That is what turns “shop.example” into a verifiable statement of the domain's owner: a payment to your domain provably reaches whoever controls it in the DNS, not whoever registered a similar-looking name first.

Does bb84 contact my servers?

No. bb84 only queries public DNS resolvers and ENS's resolver gateways over https. Your web server, shop software or mail setup are not involved and nothing needs to be installed.

What does “ENS upgrade pending” mean?

After the 2026 rollover of the DNS root key, ENS's currently active DNSSEC oracle no longer accepts any DNS proof. The ENS DAO is replacing oracle and registrar (forum thread). Until that executes, new DNS names cannot resolve through ENS, yours included. Everything on your side can be prepared now; the check tells you when your chain is valid against the new oracle.

Which bb84 address should I publish?

Any address of your bb84 wallet (Keys tab). For a shop, a dedicated address with the merchant flag is best: payments then come with buyer protection and your statements stay tidy. If you delete that address later, publish a new one first: payments to a deleted address are locked for good.

Can I use a subdomain?

Yes. pay.shop.example works like the domain itself; the record is then _ens.pay.shop.example. The subdomain only has to be inside your signed zone.

Is there an API?

The check behind this page is GET https://bb84.com/api/ens/mainnet/check/<domain> (JSON, rate-limited), the ENS-side state GET /api/ens/mainnet/dns-status, and what the app resolves GET /api/ens/mainnet/resolve/<domain>. Details for developers and AI assistants: bb84.com/developers.