EMAIL / ISSUER

Build Chrome Email Verification discovery — then publish it yourself.

For mailbox providers and IdP teams who need Chrome to find their issuer. Fill your domains once, get a paste-ready DNS TXT, well-known JSON, and Pages headers — all in your browser, nothing uploaded.

Start tool Runs in your browser · nothing uploaded

One form → three artifacts

Copy DNS, download issuer JSON, grab a Content-Type recipe. No signup.

Local only

Domains and endpoints never leave this tab. We never ask for private keys.

Guides that match the tool

How-to, FAQ, and real publish scenarios sit next to the generator.

Open the generator

Enter email domain + issuer host + endpoints. Copy, download, deploy.

How to publish

Eight executable steps: DNS format, dual algs, Pages headers, curl check.

Use cases

Mailbox provider, enterprise IdP, and SDK reference packs.

FAQ

iss= rules, redirects, BIMI/SPF boundary, privacy, what this is not.
What the pack contains (for implementers)
  1. DNS TXT — _email-verification.<email-domain> TXT "iss=<issuer-host>" on the mailbox zone.
  2. Well-known JSON — https://<issuer-host>/.well-known/email-verification with issuance endpoint, JWKS URI, and signing_alg_values_supported (Ed25519 + EdDSA for the Chrome 154–156 window).
  3. Pages _headers recipe — so the extensionless file is served as application/json.

This is not ZeroBounce-style address validation. Origin Trial tokens for relying parties are separate — renew them on the Chrome OT portal (tokens issued before the extension may expire around 2026-11-17).