Google Workspace DKIM Setup: Fix "Not Authenticating Email"
The short answer (what's causing it)
Without custom DKIM, Workspace signs with a default gappssmtp.com key that doesn't align with your domain for DMARC. The status stays "Not authenticating" until you publish the TXT record and click Start authentication.
Step-by-step fix
- Admin console → Apps → Google Workspace → Gmail → Authenticate email.
- Generate a new record (2048-bit if your DNS host supports long TXT values; selector
googleby default). - Publish the TXT at
google._domainkey; split into 255-char strings if your host requires. - Return to the console and click Start authentication.
- Test and scan.
Record examples (replace example.co.uk with your domain)
google._domainkey.example.co.uk. TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqh..."
Examples are illustrative templates, not values for your domain. Test changes at
p=none/ staging first.
Check yours free in seconds
Run the free 20-check SuperTool on your domain: no signup, no install, public DNS only. Relevant checks: DKIM, DNS TXT.
Scan my domain free (20-check SuperTool) → £24 Sovereign DMARC (T0 RUA), SPF, MTA-STS & PHP2Shell Remediation Pack → £5 Website Launch Special Quick-Fix Pack →One-off download via PayPal guest checkout, no subscription. Packs contain DNS/config templates and scripts you run yourself.
Frequently Asked Questions
1024 or 2048-bit?
2048-bit where your DNS provider allows it.
How long until it works?
Google notes it can take up to 48 hours after publishing.
Related FaultyPacket guides & tools
- Free 20-check SuperTool
- Zero-downtime DMARC p=reject, SPF & MTA-STS rollout
- Business Building 101: domain, MX & DMARC
Authorised use: only scan domains you own or are authorised to inspect. Results are point-in-time public DNS observations.