SPF
Authorize the servers allowed to send mail for your domain — a single v=spf1 TXT record at the apex, with ip4/ip6, provider includes and a softfail or fail policy. Open the SPF generator →
Record Studio builds correct SPF, DKIM, DMARC, BIMI, TLSA/DANE, MTA-STS, TLS-RPT, CAA, SMIMEA, security.txt and Null MX records — and does more than generate them: load a record you already publish and it is validated in place, colour-graded and with the certificate details behind it, using the same rules as the free domain security check. New to these records? The email authentication and mail server TLS & DANE guides explain what each one does and how it is scored.
All generators run entirely in your browser; key pairs and certificate digests are computed locally with the Web Crypto API, and nothing you type into a generator – IP addresses, certificates or freshly generated DKIM private keys – ever leaves your device. The one exception is the optional "Load current record" button: it sends only the domain you want to read to our server, which looks it up in public DNS (over HTTPS for security.txt and MTA-STS) – just like a scan – and returns it. The TLSA generator's "Fetch certificate from your server" button additionally has our server open a TLS connection to the host and port you enter, to read that server's public certificate (it never sees a private key). Internationalized domain names with non-ASCII characters are converted to their punycode A-label form, because DNS records must use it.
Authorize the servers allowed to send mail for your domain — a single v=spf1 TXT record at the apex, with ip4/ip6, provider includes and a softfail or fail policy. Open the SPF generator →
Generate an RSA-2048 or Ed25519 signing key pair in your browser and build the <selector>._domainkey TXT record — the private key is shown once and never transmitted. Open the DKIM generator →
Tell receivers what to do with mail that fails SPF and DKIM — a _dmarc TXT record with policy, reporting and alignment. Follows DMARCbis (RFC 9989), so no deprecated tags. Open the DMARC generator →
Publish your brand logo for authenticated mail — a <selector>._bimi TXT record with the logo URL, optional VMC and the new avp tag. Requires enforced DMARC. Open the BIMI generator →
Pin a certificate or public key in DNS so clients can verify a server independently of CAs — for SMTP, HTTPS and any TLS port. Digests are computed in your browser; needs DNSSEC. Open the TLSA / DANE generator →
Bind an S/MIME certificate to an email address in DNS — the DANE counterpart of TLSA for email. Owner name is <hash>._smimecert; digests are computed in your browser. Needs DNSSEC. Open the SMIMEA generator →
Require encrypted, certificate-verified SMTP delivery — the _mta-sts TXT record plus the mta-sts.txt policy file, both produced here. Open the MTA-STS generator →
Collect daily reports about TLS and MTA-STS/DANE delivery problems — a _smtp._tls TXT record pointing at your report addresses. Pairs naturally with MTA-STS or DANE. Open the TLS-RPT generator →
Declare which certificate authorities may issue for your domain — an allow-list CAA RRset that CAs must honour before issuance, with optional wildcard ban and violation reporting. Open the CAA generator →
Tell researchers how to report a vulnerability — a machine-readable /.well-known/security.txt file with Contact and Expires, validated strictly against RFC 9116. Open the security.txt generator →
Shut down spoofing of a domain that sends no mail — a Null MX (RFC 7505), a fail-all SPF record and a DMARC reject policy, generated together. Web records stay untouched. Open the Null MX generator →