How do I set up Google Workspace records at Namecheap?

Manually — Namecheap's Gmail preset is flagged in its own knowledgebase as 'temporarily not working. Please configure your records for Google Workspace using the Custom MX option', and no Namecheap article covers Workspace SPF, DKIM or DMARC. The manual set: verify the domain with Google's TXT; replace all MX with Google's current single record, smtp.google.com at priority 1 (the legacy five-record set still works if already in place and mail flows); publish one SPF record merging include:_spf.google.com (checked live, it costs exactly one lookup) with any other senders; generate DKIM in the Google Admin console (choose 2048-bit) and publish the TXT at google._domainkey; then publish your own DMARC at _dmarc starting at p=none. If Namecheap Private Email was on the domain, its MX pair and ~all SPF must be removed first or both systems break.

How do I enter a 2048-bit DKIM key at Namecheap without breaking it?

A 2048-bit DKIM value is longer than one 255-character DNS string, so it legitimately lives as two chunks inside one TXT record — a readback showing two quoted chunks is the CORRECT form, not an error. Namecheap publishes no TXT length limit and contradicts the blogosphere about splitting: its own DKIM article describes entering the value across two fields manually, while third-party guides claim the form splits automatically. The safe procedure: paste the whole console value (no quotes, no brackets, no line breaks), then verify by public lookup — the concatenated chunks must match the Admin console value character-for-character. Only if that readback fails should you re-enter using Namecheap's documented manual split. Never fix a length problem by silently downgrading to a 1024-bit key or by creating two separate TXT records at the same name.

Google Workspace · Namecheap · Full setup

Google Workspace on Namecheap: complete authentication, entered by hand (because the preset is broken)

First published 20 October 2026 · Google's values re-verified from Google's pages today; Namecheap behaviour from its knowledgebase read in full. Host-sibling of Workspace on Cloudflare and M365 on Namecheap.

Do not fix the wrong thing first. Namecheap's Mail Settings offers a Gmail preset — and Namecheap's own knowledgebase flags it: “Gmail — temporarily not working. Please configure your records for Google Workspace using the 'Custom MX' option.” Meanwhile no Namecheap page covers Workspace SPF, DKIM or DMARC at all (their coverage is fragmented across four partial articles), and current blogs describe a “Google Workspace one-click preset that populates all 5 MX records” — contradicted by Namecheap's text on both counts: there is no such preset, and Google's current set is one record. This ladder is the whole job, by hand.

Pre-check: the Private Email collision (Google edition)

If this domain ran Namecheap Private Email, its preset records collide with Google's exactly as they did with Microsoft's (Article #42): its MX pair must go (Google's MX must stand alone), its ~all SPF must be replaced, not joined (two SPF records = PermError), and a pre-existing _dmarc blocks rung 5 until you decide whose it is. Two differences to note honestly: Private Email's DKIM TXT sits at a different selector — stale, not colliding — and its autodiscover CNAME has no Google counterpart: Google publishes no autodiscover record, so don't hunt for one because the Microsoft guide had one.

The ladder (Namecheap grammar: relative Host, `@` = root, TTL Automatic = 30 min)

Mail Settings → Custom MX. The sanctioned route while the Gmail preset is down (Namecheap's own instruction).
Verify the domain with Google's TXT (Host @, the value from the Admin console's verification step).
MX: delete every existing MX; add one: Host @ → smtp.google.com, priority 1 — Google's current instruction, which Namecheap's KB independently prints for post-April-2023 subscribers. Exception: a domain already running the legacy five-record Google set with mail flowing may keep it — Google tolerates it in place. Mixed or half-migrated sets are the failure; complete either shape. Then Activate Gmail in the Admin console.
SPF: one TXT at @: v=spf1 include:_spf.google.com ~all — merge other senders' includes into this same record (Articles #3/#18). Live check today: Google's include still resolves flat — it costs exactly 1 lookup, whatever older guides claim.
DKIM: Admin console → generate (choose 2048-bit, selector google) → publish the TXT at Host google._domainkey using §DKIM below → Start authentication in the console.
DMARC: TXT at _dmarc: v=DMARC1; p=none; rua=mailto:you@yourdomain — yours to publish (Google's guidance agrees; no preset does it), then climb per Article #4, reading reports per Article #36.

§DKIM — the 2048-bit record at Namecheap, without folklore

A 2048-bit value exceeds one 255-character DNS string, so it lives as two chunks inside one TXT record. Namecheap states no TXT limit anywhere in its KB; its only DKIM article describes a manual two-field split, while third-party guides claim the form splits automatically. Neither claim gets promoted here — this procedure survives both:

Paste the whole console value — no quotes, no brackets, no manual line breaks.
Read it back publicly. Success looks like ONE TXT record whose two quoted chunks, concatenated, match the console value character-for-character. A two-chunk display is the correct form of a 2048-bit record — do not “fix” it.
Only if the readback mismatches: re-enter using Namecheap's documented manual split (first field as much as fits, remainder in the second), then read back again.
Never resolve a length scare by downgrading to 1024-bit silently, splitting into two separate TXT rows at the same name, or trimming “duplicate-looking” characters — each manufactures the Article #19 failure.

Verify

Admin console: Gmail activated; DKIM status Authenticating email; Google's own Check MX (Toolbox) walks the set — inherited from Article #7's pass.
Readbacks: single Google MX only; one SPF; google._domainkey TXT matching the console in full; one _dmarc.
Headers: test mail shows dkim=pass with d= your domain, spf=pass, dmarc=pass (the §DKIM readback + this stamp together are the proof; the console's “up to 48 hours” is Google's stated onset window).

Traps

Trap	Reality
The blogosphere's “one-click 5-MX preset”	Doesn't exist (KB-checked). Google's set is one record; the blogs are describing 2019.
Adding Google's MX beside Private Email's	Split delivery between two providers — the pre-check exists because this is the default state of migrated Namecheap domains.
“Fixing” the two-chunk DKIM display	That's the correct wire form of a 2048-bit record. The readback comparison is the only judgement allowed.
Hunting for Google's autodiscover record	There isn't one. Cross-reading the M365 guide creates this ghost; client setup for Google runs through Google's own discovery, not a record you publish.

FAQ

We still have the old five MX records and everything works. Change?

Google tolerates the legacy set in place. Change only for a reason (consistency, a migration) — and if you change, change completely: the single record plus deleting all five, never a blend.

Which TTL?

Namecheap's Automatic (30 min) throughout this set — no document in this combination demands otherwise. (The 1-hour DKIM floor belonged to Microsoft's troubleshooter in the Cloudflare combination, not this one — combinations differ, and the guides keep them separate for exactly this reason.)

Verification failed but the TXT “looks right.”

Namecheap's verification article is written for cPanel hosting and hands BasicDNS users to its generic host-records article — panel confusion is the usual cause: confirm you're editing the domain's Advanced DNS (BasicDNS), that Host is exactly @, and read the record back publicly before re-trying Google's check.

Sources

Google Workspace Admin Help — MX setup (single smtp.google.com record + Activate Gmail) · SPF setup (value; no legacy-include warning exists on the page — recorded as an honest negative) · DKIM setup · Namecheap Knowledgebase — KB 322 (Mail Settings; Gmail preset warning verbatim; MX for post-Apr-2023 subscribers), KB 434 (host-record grammar; Automatic = 30 min), KB 10296 (verification, cPanel-scoped), KB 10383 (DKIM manual split) · Live DNS (Google's SPF chain cost, 2026-10-20) · Packs #7/#42 (mechanics inheritance, collision map).

Verification note: Google's values, the preset warning and Namecheap's KB scope were confirmed on 20 October 2026. Whether Namecheap's form splits long TXT values automatically is contradicted between Namecheap's article and third-party guides — §DKIM's paste-then-readback procedure is written to be correct under either behaviour.

Did this guide work for you?

Your reaction tells us whether this guide solved the problem it promised to solve.