schedule 14-min read

gappssmtp.com in Email Headers: What It Means for DMARC

DMARC AI editorial team · Last updated

Seeing gappssmtp.com in a DKIM signature? It means Google Workspace signed without your own DKIM key, so DKIM does not align for DMARC. How to fix it.

01

What does gappssmtp.com mean in an email header?

A gappssmtp.com domain in an email header means Google Workspace signed the message with a Google-owned DKIM key instead of a key for your own domain. The signature usually passes, but its d= domain does not match the From domain, so DMARC cannot use it. The domain is relying on SPF alone until custom DKIM is enabled.

You typically spot it in Gmail's "Show original" view or in a DKIM-Signature header, as a domain that ends in gappssmtp.com and is derived from your primary domain, for example example-com.20230601.gappssmtp.com. This guide explains how to read it, why it matters for DMARC under RFC 9989, how to replace it with an aligned google._domainkey key, and how an MSP (managed service provider) finds every affected client from DMARC aggregate reports. For DKIM fundamentals, start with the DKIM guide.

02

Key takeaways

  • A d= value ending in gappssmtp.com is a Google signing domain, not yours. dkim=pass with that domain does not count towards DMARC.
  • Without an aligned DKIM signature, Workspace mail passes DMARC only through SPF, and SPF usually fails when mail is forwarded.
  • The fix is to generate a key under Apps > Google Workspace > Gmail > Authenticate email, publish it at google._domainkey, then click Start authentication.
  • Google's current Admin Help pages do not name gappssmtp.com. Treat the naming pattern as observed behaviour, not documented behaviour.
  • In aggregate reports, look for auth_results/dkim/domain values ending in gappssmtp.com next to policy_evaluated/dkim of fail.
03

What does a gappssmtp.com DKIM signature look like?

It looks like an ordinary DKIM signature with a Google domain in the d= tag. The d= value is commonly your domain with dots replaced by hyphens, followed by a date-like label and gappssmtp.com. Gmail's summary in "Show original" shows the same domain on the DKIM line.

A public example appears in a 2024 WordPress.org systems team discussion, where Gmail reported mail from wordcamp.org as:

DKIM:  'PASS' with domain wordcamp-org.20230601.gappssmtp.com

After the team set up DKIM in the Admin console, the same thread reports that test mail passed DKIM with the domain wordcamp.org. That before-and-after is the whole story of this article in two lines.

In the raw headers of a message from a client domain, the relevant parts look like this (signature values shortened):

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=example-co-uk.20230601.gappssmtp.com; s=...;
        h=from:to:subject:date:message-id; bh=...; b=...
Authentication-Results: mx.receiver.example;
       dkim=pass header.d=example-co-uk.20230601.gappssmtp.com header.s=...;
       spf=pass smtp.mailfrom=example.co.uk;
       dmarc=pass (p=NONE) header.from=example.co.uk

Notice that DMARC still passes here, but only because SPF passed for example.co.uk. The exact date label and selector are chosen by Google and can differ between tenants or change over time, so do not hard-code 20230601 in alerting rules. Match on the gappssmtp.com suffix instead.

04

Is gappssmtp.com documented by Google?

Not in the current Admin Help pages. Google's Set up DKIM and Troubleshoot DKIM issues articles explain how to create your own key but do not mention gappssmtp.com or describe a fallback signing domain.

The behaviour was described by Google in the past. A 2016 Google Groups thread quotes an earlier version of Google's DKIM help article: "We now sign all email traffic not signed with DKIM originating from Google Cloud domains with d=*.gappssmtp.com." That text no longer appears on the current pages, and public examples like the one above show the signatures still being applied.

The practical position for an engineer: the signature is real, Google controls it, and you cannot configure or rely on it. Plan as if it does not exist, and give every sending domain its own key.

05

Why does a gappssmtp.com signature not help DMARC?

Because DMARC only counts a DKIM pass when the signing domain aligns with the From domain. A d= value under gappssmtp.com has a different Organizational Domain from example.co.uk, so it fails both relaxed and strict alignment, however valid the cryptography is.

RFC 9989 is explicit about this. Section 4.4.1 says a message produces a DMARC pass "if any DKIM-Authenticated Identifier aligns with the Author Domain", and explains why unaligned signatures are ignored: "a message can bear a valid signature from any domain, even one used by a bad actor." Relaxed alignment (the default, adkim=r) only requires the same Organizational Domain; strict alignment requires an identical domain. A Google domain meets neither. The alignment guide walks through both modes.

RFC 6376 itself only proves that the holder of the key for the d= domain took responsibility for the message. It says nothing about the From address. That link between signer and visible sender is exactly what DMARC adds, and exactly what a gappssmtp.com signature cannot provide.

Result in headers Counts for DMARC? Why
dkim=pass header.d=example.co.uk Yes Signing domain matches the From domain
dkim=pass header.d=mail.example.co.uk Yes, with adkim=r Same Organizational Domain
dkim=pass header.d=example-co-uk.20230601.gappssmtp.com No Google's domain, different Organizational Domain
spf=pass smtp.mailfrom=example.co.uk Yes Workspace uses your domain as the envelope sender
06

What happens to DMARC when the mail is forwarded?

It usually fails. Forwarding changes the connecting IP address, so SPF for your domain no longer passes at the final receiver. With only an unaligned gappssmtp.com signature left, there is no aligned identifier, and a domain at p=quarantine or p=reject sees legitimate mail junked or bounced.

This is the real cost of leaving default signing in place. Direct mail from Workspace looks healthy, because the Google Workspace SPF record produces an aligned SPF pass. The failures show up only on indirect paths: a recipient's auto-forward to a personal mailbox, a mailing list, or a security gateway that relays mail onward. An aligned DKIM signature normally survives forwarding when the message body and signed headers are left unchanged, which is why DMARC needs both. The forwarding guide covers the mechanics, and why DMARC fails when SPF passes covers the opposite case.

Google's sender guidelines also matter here. The Email sender guidelines require all senders to personal Gmail accounts to set up SPF or DKIM, and bulk senders (more than 5,000 messages a day) to set up SPF, DKIM and DMARC, with the From domain aligned with either the SPF or the DKIM domain. A gappssmtp.com signature does not satisfy the DKIM requirement for your domain.

07

How do I find gappssmtp.com in a message header?

Open the message in Gmail on a computer, click More next to Reply, choose "Show original", and read the DKIM line in the summary at the top. In the raw text below it, search for gappssmtp and check the Authentication-Results header for header.d= or header.i=.

Google's Trace an email with its full header page gives the same steps. In Outlook or another client, export the raw source and look for three things:

  1. The DKIM-Signature header. The d= tag is the signing domain. If it ends in gappssmtp.com, Google signed with its own domain.
  2. The receiver's Authentication-Results header. The topmost one added by the receiving system is the one to trust. Look at dkim= and its header.d= or header.i=.
  3. The dmarc= result and header.from. If dmarc=pass appears while the only DKIM pass is for gappssmtp.com, the pass came from SPF.

Paste the full header into the email header analyzer to see the signing domain, the alignment result and the hop path in one view. The MSP guide to reading email headers explains how to tell which Authentication-Results header belongs to which hop.

08

How do I replace gappssmtp.com with my own DKIM key?

Generate a key for the domain in the Google Admin console, publish it as a TXT record at google._domainkey, wait for DNS to update, then click Start authentication. Once the status reads "Authenticating email with DKIM", new mail is signed with d= set to your own domain.

The steps on Google's Set up DKIM page, condensed:

  1. In the Admin console, go to Menu > Apps > Google Workspace > Gmail and click Authenticate email. Generating a key needs super administrator access.
  2. In the Selected domain menu, choose the domain.
  3. Click Generate New Record. Choose 2048 bit length if the DNS host supports it, otherwise 1024. Leave the prefix selector as google unless the domain already uses that selector.
  4. Copy the host name and TXT value into the domain's DNS.
  5. Back in the Admin console, click Start authentication. Google notes it can take up to 48 hours for DKIM authentication to start working after the record is added.

The published record looks like this:

google._domainkey.example.co.uk.  3600  IN  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqh...IDAQAB"

Some practical notes for client work:

  • Timing on new tenants. Google says you must wait 24 to 72 hours after turning on Gmail before the key is available in the Admin console. Build that into onboarding instead of leaving it as a forgotten follow-up.
  • 2048-bit keys and long TXT values. Some DNS panels need the value split into several quoted strings. RFC 6376, Section 3.6.2.2 says strings in a TXT record must be concatenated before use, so a split value is fine as long as no characters are lost.
  • Every domain needs its own key. Google states: "You must get a unique DKIM key from the Admin Console for each domain." Secondary domains that send mail stay on default signing until each has its own key.
  • Do not click Start authentication early. If signing starts before the TXT record resolves, receivers see a signature they cannot verify.
  • Verify, then record. Send a test to a Gmail account, confirm dkim=pass header.d=example.co.uk, and log the selector and key length in the client's documentation.

How to set up DKIM covers the general process across providers, and our DKIM validator checks the published key at google._domainkey.

09

How do MSPs find clients still signing with gappssmtp.com?

Search the DMARC aggregate reports. In each record, a DKIM entry under auth_results whose domain ends in gappssmtp.com, combined with policy_evaluated/dkim of fail for Google's sending IPs, identifies a Workspace domain without its own DKIM key.

RFC 9990 defines both fields, and the distinction matters. auth_results/dkim reports the raw verification result for each signature, while policy_evaluated/dkim is defined as "the result of the DKIM DMARC Identifier Alignment test". A typical affected record looks like this:

<record>
  <row>
    <source_ip>209.85.220.41</source_ip>
    <count>212</count>
    <policy_evaluated>
      <disposition>none</disposition>
      <dkim>fail</dkim>
      <spf>pass</spf>
    </policy_evaluated>
  </row>
  <identifiers>
    <header_from>example.co.uk</header_from>
  </identifiers>
  <auth_results>
    <dkim>
      <domain>example-co-uk.20230601.gappssmtp.com</domain>
      <result>pass</result>
    </dkim>
    <spf>
      <domain>example.co.uk</domain>
      <result>pass</result>
    </spf>
  </auth_results>
</record>

The raw DKIM result is pass, but the aligned result is fail, and the message passed DMARC on SPF alone. Records from forwarders for the same domain will often show spf failing too, which is where real mail starts to fail DMARC. The aggregate reports guide explains the rest of the schema.

A workable portfolio routine:

  1. Filter. Across all client domains, list records where any auth_results/dkim/domain ends in gappssmtp.com.
  2. Confirm. Check DNS for a TXT record at google._domainkey (or the client's custom selector) and the status on the Authenticate email page.
  3. Prioritise. Fix domains at p=quarantine or p=reject first, then any domain where reports show forwarded mail failing DMARC.
  4. Change control. Treat the DNS record and Start authentication as one change with a rollback note, and recheck reports a week later to confirm aligned DKIM passes from Google's IPs.
  5. Prevent recurrence. Add "custom DKIM active" to the Workspace onboarding checklist and to any process that adds a secondary domain.

This fits the wider rollout in the DMARC for Google Workspace implementation guide. DMARC AI processes aggregate reports across client tenants, so this pattern shows up as DKIM alignment failures by source rather than something you have to grep for in XML.

10

Does this change under DMARCbis or UK guidance?

No. RFC 9989, which obsoletes RFC 7489, keeps the same rule: only aligned identifiers count, and the default DKIM alignment mode is still relaxed. The UK NCSC says the same in plain terms and recommends 2048-bit keys.

The NCSC's DKIM guidance says "You should configure DKIM on domains you send email from" and "We recommend you use a 2048-bit key." It also recommends rotating keys periodically. For a Workspace client moving from p=none to p=quarantine to p=reject, an aligned Google DKIM key should be in place before enforcement, not discovered afterwards through forwarding complaints. The DMARCbis guide for Google Workspace clients covers the rest of the DMARCbis changes for these tenants.

11

Frequently asked questions

Is gappssmtp.com spam or a sign of spoofing?

No. A gappssmtp.com domain in a DKIM signature on mail from your Workspace tenant is Google signing on your behalf. It is not a compromise or a third-party sender. It does mean your domain has no aligned DKIM, which makes your own mail more fragile under DMARC enforcement and offers no extra protection against spoofing.

Can I delete or turn off the gappssmtp.com signature?

You cannot configure it directly, and there is no need to. Once you generate your own key, publish it and click Start authentication, Google signs outgoing mail with your domain. Observed examples show the gappssmtp.com domain disappearing from the DKIM result after custom DKIM is switched on.

Why does DMARC pass even though DKIM shows gappssmtp.com?

Because SPF passed and aligned. Google Workspace uses your domain as the envelope sender, so an SPF pass for your domain satisfies DMARC on direct mail. The gappssmtp.com DKIM pass contributes nothing. When the message is forwarded and SPF fails, nothing aligned is left, and DMARC fails.

Do secondary domains in Google Workspace need their own DKIM key?

Yes. Google states that you must get a unique DKIM key from the Admin console for each domain. Choose each sending domain in the Selected domain menu on the Authenticate email page, publish its record and start authentication. A secondary domain without its own key keeps signing with a Google domain.

Should I use a 1024-bit or 2048-bit key?

Use 2048-bit whenever the DNS host supports it. Google recommends 2048-bit in its sender guidelines, the NCSC recommends 2048-bit keys, and Gmail requires at least 1024 bits. Choose 1024-bit only when the DNS provider cannot store the longer TXT value, and plan to move up later.

12

Next steps

Search the last 30 days of aggregate reports for DKIM domains ending in gappssmtp.com, list the affected client domains, and schedule custom DKIM for each one through normal change control. Then confirm in the reports that Google's sending IPs show an aligned DKIM pass before tightening any DMARC policy.

Related articles

Related tools

Ready to Implement?

Get authenticated mail moving in minutes: start free, book a guided demo, or talk to the team about your stack.