You generate a shiny new 2048-bit DKIM key in Google Workspace or your ESP, paste it into Namecheap’s Advanced DNS manager, and immediately get smacked with a red error: “Parameter Value is not valid”. Even worse, sometimes Namecheap silently truncates your public key at 255 characters—meaning your emails ship with broken cryptographic signatures and head straight to spam.
Here is how to clean, format, and save that 2048-bit DKIM TXT record in Namecheap without triggering validation bugs or wrecking your deliverability.

The 255-Byte DNS String Limit Behind the Error
Under RFC 1035, a single text chunk inside a DNS TXT record cannot exceed 255 octets (bytes). Old 1024-bit RSA keys easily fit inside this boundary because their base64 string is only about 216 characters. A modern 2048-bit key, however, clocks in around 400 to 450 characters.
Per RFC 4408 and RFC 6376, DNS resolves this by letting you stitch multiple 255-byte strings together inside one TXT record. Mail servers querying your domain will automatically concatenate those pieces back into one long public key before checking signatures.
The headache comes from Namecheap’s UI. Its input validator hates raw zone file formatting. If you copy multi-line BIND output straight out of Google Workspace, Mailgun, or Postmark—complete with quotes and line breaks—Namecheap chokes.
Clean Provider Formatting Before Touching Namecheap
Most email hosts hand you DKIM records pre-formatted for BIND zone files. They wrap everything in parentheses, break strings across several lines, and slap quotes around each chunk. Pasting that directly into Namecheap will fail every time.
Here is the standard export format you usually get from an email provider or OpenDKIM:
google._domainkey IN TXT ("v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0Y3Fq9L..."
"aBC123def456ghi789..."
"...xyzIDAQAB" )Namecheap does not want any of those BIND wrappers. Before pasting anything into your dashboard, strip out:
- The opening and closing parentheses:
(and) - All surrounding double quotes:
" - All line breaks, tabs, and indentation
- Any trailing whitespace at the very end
You need one continuous, flat line starting with v=DKIM1; k=rsa; p= and running straight through to the end of your base64 string (often ending in AQAB or similar).
If you don’t feel like wrestling with manual text selection, a quick Node snippet in your terminal cleans it instantly:
// sanitize-dkim.js
const rawInput = `("v=DKIM1; k=rsa; p=MIIBIjANBgkqh..." "remainderOfKey...")`; const cleanKey = rawInput .replace(/["()rns]+/g, '') .trim(); console.log(cleanKey);That outputs the exact string Namecheap wants. Just like when you configure an A record vs CNAME on a Namecheap root domain, keeping your DNS records free of formatting garbage saves you hours of head-scratching later.
Add the DKIM Record in Namecheap Advanced DNS
Head to your Namecheap account, find your domain under Domain List, hit Manage, and jump into the Advanced DNS tab.
- Scroll down to the Host Records table.
- Click Add New Record.
- Pick TXT Record from the dropdown.
- In the Host field, enter only your selector and subkey. If your provider gave you
google._domainkey.yourdomain.com, enter justgoogle._domainkey. - In the Value field, paste your stripped, single-line DKIM string. No quotes, no breaks.
- Set the TTL to Automatic (or 1 min if you plan to test right away).
- Click the green checkmark to save.
Namecheap’s current backend handles raw strings up to 4096 characters and automatically handles the 255-byte chunking behind the scenes. The trick is simply not giving it manual quotes or line breaks to choke on.
If you run a more complex setup, such as routing mail via a subdomain email custom MX setup in Namecheap, the same logic holds: only put the subdomain-relative prefix in the Host field.
Fix the “Parameter Value is Not Valid” Error
If Namecheap still rejects your entry with a red validation error, check these three edge cases.
1. Hidden Spaces in the Public Key
When you copy base64 text across wrapped terminal lines or web panels, invisible spaces often creep in. A single stray space inside the p=... base64 payload invalidates your key. You can check for rogue whitespace in your terminal:
echo "v=DKIM1; k=rsa; p=MIIBIj...AQAB" | grep -F " "The only valid spaces in DKIM belong right after semicolons (like v=DKIM1; k=rsa; p=...). Removing those spaces entirely—so it reads v=DKIM1;k=rsa;p=MIIB...—is also 100% RFC-compliant and sidesteps touchy regex validators altogether.
2. Semicolon Escaping Issues
Some DNS control panels demand backslash-escaped semicolons (;). Namecheap does not. If your provider gave you instructions saying to write v=DKIM1; k=rsa;, delete the backslashes. If you leave them in, Namecheap treats the slashes as literal characters, corrupting the key for receiving mail servers.
3. Manual Quotation Splitting
Do not try to be clever by pre-splitting your string with quotes like "chunk1" "chunk2" inside Namecheap’s input box. Namecheap doesn’t parse those as delimiters; it saves them as literal quote characters in your DNS payload, completely corrupting your public key.
Verify the Published DKIM Record Using Dig
Skip web-based validation tools for the first few minutes. They love caching bad queries and hide raw syntax errors. Query Namecheap’s nameservers directly with dig to see exactly what is being broadcast.
Run this command, replacing the selector and domain with your own:
dig +noall +answer TXT default._domainkey.yourdomain.com @dns1.registrar-servers.comBy hitting dns1.registrar-servers.com directly, you skip any ISP resolver caching. Your output should look like this:
default._domainkey.yourdomain.com. 1799 IN TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0Y3Fq9L..." "remainderOfKeyAQAB"Look closely at the output: dig displays two distinct quoted strings separated by a space. That confirms Namecheap took your single string and split it into compliant 255-octet chunks automatically. As long as your full base64 string flows uninterrupted across those quotes, your record is clean.
On Windows without BIND utilities installed? Use PowerShell’s Resolve-DnsName instead:
Resolve-DnsName -Name "default._domainkey.yourdomain.com" -Type TXT -Server "dns1.registrar-servers.com" | Select-Object -ExpandProperty StringsAvoid the Double-Domain Trap
This is easily the most common mistake I see: pasting your full domain into Namecheap’s Host field. If your domain is indiehackershop.com and your provider says to add:
Host: s1._domainkey.indiehackershop.comTyping s1._domainkey.indiehackershop.com into Namecheap’s Host input causes Namecheap to append your domain a second time. What actually gets published is:
s1._domainkey.indiehackershop.com.indiehackershop.comWhen Gmail or Proton queries s1._domainkey.indiehackershop.com, they get an immediate NXDOMAIN. DKIM fails, and your emails drop into junk folders. Keep the Host value strictly trimmed to s1._domainkey.
If you have split infrastructure—like pointing a Namecheap subdomain to separate hosting—make sure your selector lives on the exact host segment handling outbound mail for that address.
Testing Authentication and Key Integrity
Once dig returns the full key, test the live signature by actually sending an email. That proves your sending server’s private key matches the public key you just published.
Send a message to a personal Gmail account. In Gmail, open the email, click the three dots next to the Reply arrow, and select Show original.
Check the summary table near the top. You want to see:
DKIM: 'PASS' with domain yourdomain.com
SPF: 'PASS' with IP ...
DMARC: 'PASS'If DKIM reports FAIL with rsa-sha256 signature verification failed, the key in your DNS does not match what your mail server signed with. That almost always means a character was clipped during copy-pasting or a random space snuck into the base64 string.
Frequently Asked Questions
Can I use two separate TXT records instead of splitting one record?
No. Never create two separate TXT records under the same Host name for one selector. Resolvers won’t glue them together; they’ll treat them as conflicting answers and reject both. The multi-chunk split has to exist within the value payload of a single record.
Why does my ESP suggest CNAME instead of TXT for DKIM?
Platforms like SendGrid, AWS SES, and Postmark prefer CNAME records because it hands key rotation and length limits off to them. If your provider supports CNAME DKIM, take it—it’s way less maintenance. But Google Workspace and self-hosted setups require TXT records.
How long does Namecheap take to propagate DKIM changes?
On Namecheap’s authoritative servers, it updates almost instantly (within a few seconds if TTL is low). However, public resolvers like Cloudflare (1.1.1.1) or Google (8.8.8.8) will cache older queries according to your domain’s previous TTL, which can take anywhere from 5 to 60 minutes.
Does a 2048-bit key improve email deliverability over 1024-bit?
Yes. Both Google and Yahoo now treat 1024-bit RSA keys as outdated, and some strict receiver policies flag them directly. A 2048-bit key is the current baseline requirement for clean inbox placement.
If you’re cleaning up other records across your zone file, read our walkthrough on pointing a root domain to a CNAME in Namecheap with ALIAS records to avoid common apex domain conflicts.

