Generate Brand Indicators for Message Identification DNS records to display your logo in email clients.
This tool assembles a BIMI TXT record from a logo URL and, optionally, a Verified Mark Certificate URL, formatting the tags into the record you publish at default._bimi.yourdomain.com. It does not fetch or validate the logo or certificate; it only builds the string. The thing people most often miss is that BIMI itself does nothing without DMARC already enforced at p=quarantine or p=reject with pct=100 on the domain - a correctly formatted record over an unenforced DMARC policy will simply be ignored by mailbox providers.
A concrete input and expected output from the current implementation.
Input
domain: example.com, selector: default, logo URL: https://example.com/logo.svg, VMC URL: https://example.com/vmc.pem
Expected output
default._bimi.example.com. IN TXT "v=BIMI1; l=https://example.com/logo.svg; a=https://example.com/vmc.pem;"
The tool prepends selector._bimi.<domain> using the domain you supply (not one inferred from the logo or VMC URL, which may be hosted elsewhere), sets the version tag v=BIMI1, and appends the l= (logo) and a= (VMC) tags in order, each terminated with a semicolon.
You supply a selector (default is 'default'), a domain, an HTTPS logo URL, and optionally a VMC URL. The tool concatenates these into 'v=BIMI1; l=<logo>; a=<vmc>;' and prefixes the record name as selector._bimi.domain, matching how a DNS-aware mail receiver looks up BIMI records per sending domain and selector.
It confirms the logo and VMC fields look like well-formed HTTPS URLs before building the string. It cannot confirm the SVG file is a valid SVG Tiny 1.2 Portable/Secure profile image, cannot confirm the VMC chains to a trusted CA, and cannot query your live DNS to confirm DMARC enforcement - those all require checks outside a text formatter.
Most likely your DMARC policy isn't enforced (p=none doesn't count), your SVG isn't in the required Tiny Portable/Secure profile, or the mailbox provider is requiring a certificate in a= that you haven't obtained. The tool only formats the TXT record text; it can't verify any of these prerequisites.
No, the l= logo tag alone produces a valid BIMI record. The a= tag is where you point to evidence of trademark authority - typically a Verified Mark Certificate (VMC), or a Common Mark Certificate (CMC) where a receiver accepts one - and some mailbox providers won't display the logo without a certificate present there. Which providers require it, and which certificate types they accept, changes over time, so leaving a= blank may mean no visible logo at providers that mandate one.
The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.