đ§ Route 53 TXT Record Splitter
Automatically format long DNS TXT records for AWS Route 53
đ§ Related Tools
Frequently Asked Questions
Why does Route 53 require TXT record splitting?
AWS Route 53 enforces a 255-character limit per TXT record string, as defined in RFC 4408. This is particularly problematic for DKIM public keys (which typically start with v=DKIM1;p=) and long SPF records that reference multiple email providers. The solution is to split the value into multiple quoted strings of 255 characters or fewer â DNS servers automatically concatenate them when serving the record, so the end result is functionally identical.
What records typically need splitting?
The most common cases are: DKIM records â authentication keys (v=DKIM1;p=...) are frequently 500â1000+ characters long; SPF records â complex policies with many include: references can exceed 255 characters; DMARC records â detailed reporting configurations with long RUA/RUF addresses; and domain verification tokens â some third-party services issue tokens that exceed 255 characters. If your record is under 255 characters, no splitting is needed.
How does the split format work?
The tool splits your TXT record into chunks of 255 characters or fewer and wraps each chunk in double quotes, separated by spaces â for example: "string1" "string2" "string3". When you paste this into the Route 53 "Value" field, AWS stores the multi-part string correctly. Receiving DNS resolvers automatically concatenate the quoted strings when they serve the record, so the value read by SPF validators, DKIM verifiers, and other tools matches the original unsplit value.
Does splitting affect how the record works?
No â splitting is transparent to DNS consumers. The DNS protocol allows a single TXT record to consist of multiple character strings, and resolvers are required to concatenate them before returning the value to the application. DKIM validators, SPF checkers, and domain verification tools all receive the full concatenated value and process it as if it had never been split. This behaviour is defined in RFC 4408 (SPF) and RFC 6376 (DKIM).
Need help with your email authentication setup?
This tool is provided by OSH.co.za, specialists in email deliverability consulting and Google Workspace administration. We help businesses ensure their emails reach the inbox, not the spam folder. Visit our domain checker tool for comprehensive email deliverability analysis including SPF, DKIM, DMARC, MX records, and blacklist checking.
Privacy Policy
Data Collection: This Route 53 TXT Record Splitter processes data to provide results. When you paste a TXT record and submit it for splitting, the data is processed entirely server-side to return the formatted output. We do not store, log, or transmit your TXT record data beyond what is necessary to return your results. We do not store, log, or share the domain names or data you submit beyond what is necessary to return your results.
Data Usage: Your input is used solely to generate results. No data is saved, analysed for profiling, or shared with third parties. Each new check operates independently.
DNS Lookups: To check your domain, we perform DNS queries via Google's DNS-over-HTTPS (dns.google). These queries are subject to Google's Privacy Policy. Only the domain name is transmitted â no personally identifiable information.
Support Requests: If you submit a support request, your name, email address, and message are transmitted securely to our support team via SMTP2Go. This information is used solely to respond to your query.
Analytics: We may collect anonymized usage statistics (page views, tool usage frequency) to improve functionality. This does not include the domain names you check or any personally identifiable information.
Contact: For privacy enquiries or questions, please contact us at support@osh.co.za or visit osh.co.za/contact.