
Open the full headers of almost any email sent through Google and you'll find a header called X-Google-DKIM-Signature. It looks like a DKIM signature, which leads many people to assume it's their domain's authentication — or that it boosts their reputation. Neither is quite right. This guide explains what this header is, how it differs from your domain's DKIM-Signature and from ARC headers, what it does and doesn't mean for deliverability, and what to fix if it's the only signature you see.
Is X-Google-DKIM-Signature Your Domain's DKIM?
💡 TL;DR
The X-Google-DKIM-Signature header is a Google-internal signature added to messages that pass through Google's systems, signed with a Google domain (d=1e100.net). It is not your domain's DKIM signature and isn't meant for other receivers to rely on. What matters for authentication and DMARC is a standard DKIM-Signature header with d= set to your own domain. If that's the only signature you see, your domain's DKIM probably isn't turned on — fix it in the Google Admin console.
Is it your domain's DKIM? No. The header is signed with a Google domain, 1e100.net, not with yours. When a Google engineer explained it on the IETF DKIM mailing list, the point was that Google wanted a way to mark mail that came through its infrastructure without taking "ownership" of the message in the reputation sense — which is why it isn't a regular DKIM-Signature.
Some articles describe the header as something that increases trust or reputation scores for your mail. We haven't found public evidence from Google supporting that, and the explanation above suggests the opposite intent. Treat it as Google's internal marker, not as part of your authentication.
By the end of this, you'll know exactly how to read the X-Google-DKIM-Signature header and what to check instead.
Where You'll See It — and What It Looks Like
You'll find it in the full headers ("Show original" in Gmail) of messages sent through Gmail or Google Workspace. It uses the same format as a standard DKIM signature:
Tag | Typical value | Meaning |
|---|---|---|
v | 1 | Version |
a | rsa-sha256 | Algorithm |
c | relaxed/relaxed | Canonicalization |
d | 1e100.net | Google's signing domain — not yours |
s | A date-like selector | Which Google key was used |
h | A list of headers, often including x-gm-message-state and dkim-signature | Headers covered |
bh / b | Hashes and signature | The cryptographic parts |
Headers are read from the bottom up in terms of time: each server that handles a message adds its lines at the top. So the order you see is newest first, and Google's internal headers usually sit among the lines added when the message left Google's systems.
You'll often see it next to other Google-specific headers such as X-Gm-Message-State and X-Google-Smtp-Source. All of them are internal to Google's mail system.
X-Google-DKIM-Signature vs DKIM-Signature vs ARC
Header | Who signs | Signing domain | Used for your authentication? |
|---|---|---|---|
DKIM-Signature | Your mail platform, for your domain | Your domain (e.g. d=getacme.com) | Yes — this is what receivers and DMARC check |
X-Google-DKIM-Signature | Google, internally | 1e100.net | No |
ARC-Message-Signature / ARC-Seal | Intermediaries such as Google when handling forwarded mail | The intermediary's domain | Helps receivers evaluate forwarded mail; doesn't replace your DKIM |
One message can carry several DKIM-Signature headers — for example, one for your domain and one for a sending service. Receivers check each, and DMARC needs at least one that passes and aligns.
The DKIM-Signature header is the one that matters. For DMARC, its d= domain needs to align with your From domain. The DKIM guide explains alignment in detail.
If X-Google-DKIM-Signature Is the Only Signature You See
This is the practical reason most people look this header up. They open a message from their Google Workspace domain, see a DKIM-like header from 1e100.net, and no DKIM-Signature for their own domain.
That usually means DKIM isn't turned on for the domain in Google Workspace. Without it, your messages aren't signed with your domain, DMARC can't pass on DKIM, and you're relying on SPF alone.
Open the Google Admin console → Apps → Google Workspace → Gmail → Authenticate email.
Select the domain and generate a DKIM record (2048-bit if your DNS host supports it).
Publish the TXT record at google._domainkey.{domain}.
Select Start authentication once DNS has updated.
Send a new test message and confirm a DKIM-Signature header with d={your domain}, and dkim=pass in Authentication-Results.
DNS updates can take a little while to be visible, so if Start authentication doesn't succeed straight away, wait and try again rather than regenerating the key.
Here's the advice we'd push back on: "Google already signs your mail — you don't need to set up DKIM yourself." Google signs with its own internal domain; that doesn't authenticate yours. Set up DKIM for every sending domain.
Reading a Full Header Set Correctly
When checking a message's authentication, read headers in this order and mostly ignore the X- ones.
Authentication-Results (added by the receiving server): look for spf=pass, dkim=pass with header.d= showing your domain, and dmarc=pass.
DKIM-Signature: confirm d= is your domain and s= matches the selector you published.
Received lines: confirm the message went through the platform you expect.
ARC headers: relevant mainly for forwarded mail.
Google's internal signature and other X-Google headers: internal to Google; not part of your authentication checks.
For cold email, a passing, aligned DKIM-Signature on every domain is part of the basics — alongside SPF and DMARC. Our SPF, DKIM, and DMARC guide covers all three, and DNS templates for Google Workspace and Microsoft 365 gives the records per platform.
A Sample Header Walkthrough
Here's a simplified version of what you might see on a properly configured Google Workspace message, top to bottom, and how to read each line.
Header (simplified) | What to check |
|---|---|
Authentication-Results: spf=pass … dkim=pass header.d=getacme.com … dmarc=pass | All three pass, and DKIM passed for your own domain |
DKIM-Signature: v=1; a=rsa-sha256; d=getacme.com; s=google; … | Your domain's signature; selector google matches your published record |
X-Google-DKIM-Signature: v=1; a=rsa-sha256; d=1e100.net; … | Google-internal; nothing to check |
X-Gm-Message-State / X-Google-Smtp-Source | Google-internal tracking; nothing to check |
Received: from mail-…google.com | Confirms the message went through Google |
Now compare a misconfigured domain. Authentication-Results would show dkim=none or a pass only for a domain that isn't yours, and there'd be no DKIM-Signature with d=getacme.com. The Google-internal header would still be present — which is exactly why it misleads people into thinking DKIM is working.
A useful habit: whenever you add a new sending domain, send one test message, open "Show original," and check the first two rows of this table. It takes a minute and catches the most common DKIM problem before any real campaign goes out.
What About Microsoft 365 Senders?
Messages sent from Microsoft 365 generally don't carry Google's internal header unless they've passed through Google's systems along the way. Microsoft 365 has its own equivalent trap: by default it signs with the tenant's onmicrosoft.com domain, which passes DKIM but doesn't align with your From domain. The fix is the same idea — enable DKIM for each custom domain so the signature uses your domain. The DKIM guide covers the two CNAME records Microsoft 365 needs.
Common Misconceptions
Misconception | Reality |
|---|---|
"This header means my DKIM is working" | It's Google's internal signature. Check for a DKIM-Signature with your own domain. |
"It boosts my reputation" | There's no public evidence of that; it isn't designed for other receivers to rely on. |
"I should remove it" | You can't, and there's no need. It's added by Google's systems. |
"It replaces DMARC alignment" | No. DMARC uses your domain's DKIM and SPF results. |
"Microsoft 365 mail will have it too" | Not unless the message passed through Google's systems. |
Litemail configures SPF, DKIM, and DMARC automatically on every domain for its Google Workspace and Microsoft 365 inboxes, so your own DKIM-Signature is in place from the first send. Keep complaints under 0.1%, per Google's email sender guidelines.
Your own DKIM signature, on every domain — Litemail Google Workspace and Microsoft 365 inboxes come with DKIM, SPF, and DMARC configured on your own domains, full admin access, dedicated US and EU IPs, and pre-warmed options. See Pre-Warmed Inbox Plans → About Litemail — Litemail provides pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated DNS, dedicated US and EU IPs, and full admin access. Pre-warmed plans start at $39/month for 5 inboxes; add-on inboxes go as low as $4.99/inbox on the Scale plan. View pre-warmed inbox plans →
Related reading: DKIM Guide · SPF Records for Google Workspace and Microsoft 365 · DNS Templates for Google Workspace and Microsoft 365 · Google Workspace Pre-Warmed Accounts
Key Takeaways
The X-Google-DKIM-Signature header is Google's internal signature, signed with d=1e100.net.
It is not your domain's DKIM and isn't meant for other receivers to rely on.
Your authentication depends on a standard DKIM-Signature with d= set to your domain, aligned with From.
If Google's internal signature is the only one you see, turn on DKIM for the domain in the Google Admin console.
Read Authentication-Results and DKIM-Signature first; treat X-Google headers as internal.
Set up SPF, DKIM, and DMARC on every sending domain.
Frequently Asked Questions
What is X-Google-DKIM-Signature?
A header Google adds to messages passing through its systems, signed with Google's own domain, 1e100.net. It's internal to Google and separate from your domain's DKIM signature.
Does X-Google-DKIM-Signature mean my DKIM is set up?
No. Look for a separate DKIM-Signature header with d= set to your own domain, and dkim=pass in Authentication-Results.
Does Google's internal DKIM header improve deliverability?
There's no public evidence that it does. A Google engineer described it as a way to mark mail through Google's infrastructure without taking reputation ownership.
Why do I only see X-Google-DKIM-Signature on my emails?
Usually because DKIM isn't turned on for your domain in Google Workspace. Generate a key, publish it, and start authentication.
What is 1e100.net?
A Google-owned domain used for its infrastructure, which appears as the signing domain in Google's internal signature header.
Can I remove Google's internal DKIM header?
No, and there's no need — Google's systems add it.
Does Litemail set up DKIM for my domains?
Yes. Litemail configures DKIM, SPF, and DMARC automatically on every domain for its Google Workspace and Microsoft 365 inboxes.
Authentication on Your Domain, Not Just Google's
Litemail inboxes come with DKIM, SPF, and DMARC configured on your own domains, full admin access, dedicated US and EU IPs, and free domain replacement on pre-warmed plans.
Plans from $39/month · Google Workspace and Microsoft 365 · Setup in about 5 minutes
Buy Pre-Warmed Email Inboxes & Domains | Litemail — Pre-warmed Google Workspace and Microsoft 365 inboxes with automated DNS, US and EU IPs, and setup in about 5 minutes. Fresh inboxes from $2.50/inbox; pre-warmed from $4.99/inbox at scale. View plans and pricing →
Related reading: Pre-Warmed Inboxes · Google Workspace Inboxes · Monitor Email Infrastructure Health · Cold Email Deliverability Guide · Litemail Home · Plans and Pricing


