Split long DNS TXT records (like DKIM keys) into 255-character segments for providers that require it. Free, instant, no signup required.
Splits long TXT records (like DKIM keys) into 255-character segments for Google Cloud DNS, AWS Route 53, Azure DNS, and other providers that require manual splitting. Everything runs in your browser, nothing is uploaded.
Most commonly a 2048-bit DKIM public key, but any long TXT value works. Already-quoted records are merged and re-split automatically.
Quoted for Google Cloud DNS, AWS Route 53, and Azure DNS; Plain if your provider accepts one segment per line.
One click copies the split record, ready to paste into your DNS provider's TXT field.
DNS propagation typically takes 5-60 minutes. Then confirm the record resolves correctly with our TXT Record Checker.
Per RFC 1035, a single character-string in a TXT record holds at most 255 octets. Longer values must be published as multiple strings.
When a resolver reads a multi-string TXT record, the segments are concatenated back together, "part1" "part2" is read exactly as part1part2.
Google Cloud DNS and Route 53 require you to quote and split manually; Cloudflare and GoDaddy split automatically. A wrong split breaks DKIM validation.
A 2048-bit DKIM key is cryptographic data. A single missing or duplicated character means every signature fails verification.
Extra spaces, stray quotes, or characters cut off at the wrong point silently break validation, the record looks fine but never verifies.
Discovering a formatting error after publishing means waiting through another propagation cycle to fix it. Get it right the first time.
Everything runs in your browser, your record (and any key material) never leaves your device or touches our servers.
A utility that takes a TXT value longer than 255 characters and splits it into correctly quoted segments that DNS providers accept, so resolvers can rejoin them into the original value.
Google Cloud DNS rejects long unsplit records; AWS Route 53 and Azure DNS require quoted segments. Cloudflare, GoDaddy, and Namecheap handle splitting automatically.
No. Multi-string TXT records are concatenated by resolvers, so the value received by verifiers is byte-for-byte identical to the original. Splitting is purely a storage format.
Modern 2048-bit DKIM keys produce TXT values of roughly 400+ characters, well past the 255-character string limit, so most providers require them to be split into two segments.
You should only ever publish public keys in DNS. That said, the splitter runs entirely in your browser and sends nothing to any server.
Strengthen your domain security with our free lookup tools.
SenderSignal monitors these signals continuously: 48 blacklists, SPF, DKIM, DMARC, TLS and more, with alerts in Slack, email and signed webhooks.