--- title: "What Happens When Google Workspace MX Records Are Incorrect? | DMARC Report" description: "Learn how incorrect Google Workspace MX records can cause email delivery failures, missed messages, bounces, and routing issues—and how to fix them." image: "https://dmarcreport.com/og/blog/what-happens-when-google-workspace-mx-records-are-incorrect.png" canonical: "https://dmarcreport.com/blog/what-happens-when-google-workspace-mx-records-are-incorrect/" --- Quick Answer Incorrect Google Workspace MX records can prevent emails from reaching your inbox, cause bounces, delays, or misrouting. Checking and correcting MX records helps restore reliable email delivery and ensures messages reach the right Google Workspace servers. Share [ ](https://www.linkedin.com/sharing/share-offsite/?url=undefined%2Fblog%2Fwhat-happens-when-google-workspace-mx-records-are-incorrect%2F "Share on LinkedIn") [ ](https://twitter.com/intent/tweet?text=What%20Happens%20When%20Google%20Workspace%20MX%20Records%20Are%20Incorrect%3F&url=undefined%2Fblog%2Fwhat-happens-when-google-workspace-mx-records-are-incorrect%2F "Share on X/Twitter") [ ](https://www.facebook.com/sharer/sharer.php?u=undefined%2Fblog%2Fwhat-happens-when-google-workspace-mx-records-are-incorrect%2F "Share on Facebook") [ ](https://reddit.com/submit?url=undefined%2Fblog%2Fwhat-happens-when-google-workspace-mx-records-are-incorrect%2F&title=What%20Happens%20When%20Google%20Workspace%20MX%20Records%20Are%20Incorrect%3F "Share on Reddit") [ ](mailto:?subject=What%20Happens%20When%20Google%20Workspace%20MX%20Records%20Are%20Incorrect%3F&body=Check out this article: undefined%2Fblog%2Fwhat-happens-when-google-workspace-mx-records-are-incorrect%2F "Share via Email") ![Google Workspace MX Records](https://media.mailhop.org/dmarcreport/how-to-create-dmarc-record-8593-1787315219631.jpg) If your **Google Workspace MX records** are incorrect, inbound email to your domain may be delayed, deferred, bounced, or misrouted to the wrong server. In some cases, messages may be lost if an unintended mail server accepts them. Incorrect MX records can also create security and deliverability risks until the [DNS configuration](https://phoenixnap.com/kb/dns-configuration) is corrected and the changes have propagated. [Google Workspace](https://en.wikipedia.org/wiki/Google%5FWorkspace) routes all inbound mail based on DNS MX records, so even a small mistake—like a typo in a hostname or a wrong priority value—can halt or degrade delivery. _Mail exchangers on the internet look up your domain’s MX, attempt delivery to the highest‑priority target, and will retry or give up based on DNS resolution and SMTP responses_. When MX is wrong, senders either can’t find your server (NXDOMAIN), connect to the wrong system (old provider or a hijacked host), or follow suboptimal priorities that cause timeouts, greylisting, and unexpected filtering. Practically, recovery depends on how quickly you identify the issue, fix DNS, and let TTLs expire. With best practices (low TTL during changes, proper validation, and monitoring), organizations can reduce [mean time to detect (MTTD)](https://www.rapid7.com/fundamentals/mean-time-to-detect-mttd/) from hours to minutes. DMARCReport helps here by continuously monitoring your DNS posture (MX, SPF, DKIM, DMARC), running external MX checks, and alerting on anomalies and authentication changes so you can catch and correct MX problems before they impact customers. ## The Google Workspace MX Records You Must Publish (And How To Enter Them) Correct configuration starts with the **exact hostnames and priorities** Google requires; any deviation risks delivery. ### Required MX hostnames and priorities - **Priority 1**: ASPMX.L.GOOGLE.COM. - **Priority 5**: ALT1.ASPMX.L.GOOGLE.COM. - **Priority 5**: ALT2.ASPMX.L.GOOGLE.COM. - **Priority 10**: ALT3.ASPMX.L.GOOGLE.COM. - **Priority 10**: ALT4.ASPMX.L.GOOGLE.COM. Notes: - Lower number = higher priority. Google’s redundancy relies on these exact weights. - Use [fully qualified domain names (FQDNs)](https://www.techtarget.com/whatis/definition/fully-qualified-domain-name-FQDN). Some DNS UIs require a trailing dot; others add it automatically. - Do not point MX to IP addresses or use CNAMEs as MX targets (violates RFCs and breaks resolution). ![Step‑By‑Step: Add or Modify Google Workspace MX Records on Popular DNS Providers](https://media.mailhop.org/dmarcreport/dmarc-check-5893-1787315262461.jpg) ### How to enter them correctly in DNS - **Name/Host**: “@” for the root domain (example.com) unless you’re configuring a subdomain like mail.example.com. - **Type**: MX - **Value**: The Google FQDN (e.g., ASPMX.L.GOOGLE.COM.) - **Priority**: As listed above (1, 5, 5, 10, 10) - **TTL**: 300–3600 seconds recommended; use 300 (5 min) during migrations to speed **propagation and rollback**. **DMARCReport tie‑in**: DMARCReport’s DNS Watch continuously checks your live authoritative zone for drift from Google’s required MX set (hostnames, priorities, TTL anomalies) and alerts you if a record is missing, mistyped, duplicated, or overshadowed by a wrong priority. ## Step‑By‑Step: Add or Modify Google Workspace MX Records on Popular DNS Providers _These steps help you implement or fix MX accurately the first time_. ### GoDaddy 1. Sign in > Domains > DNS > Manage DNS. 2. Under Records, Add > Type: MX. 3. Host: @; Points to: ASPMX.L.GOOGLE.COM.; Priority: 1; TTL: 300–3600. 4. Repeat for ALT1..ALT4 with priorities 5, 5, 10, 10. 5. Delete any old MX entries not required by Google. 6. Save. Use the DNS Check to confirm. **DMARCReport**: Enable the “MX Baseline” policy in DMARCReport to alert if GoDaddy shows any extra MX left over from a prior provider. ### Cloudflare 1. DNS tab > Records > Add record > MX. 2. Name: @; Mail server: ASPMX.L.GOOGLE.COM.; Priority: 1; TTL: Auto or 300–3600 (Auto respects platform defaults). 3. Add ALT1..ALT4 **with proper priorities**. 4. Ensure MX records are not proxied (Cloudflare does not proxy MX). 5. Remove obsolete [MX records](https://www.digicert.com/blog/what-is-an-mx-rec). **DMARCReport**: DMARCReport cross‑checks Cloudflare API with public resolution to detect split‑brain or stale delegation. ### AWS Route 53 1. Hosted zones > example.com > Create record. 2. Record type: MX; Routing policy: Simple. 3. **Record name**: leave blank for root. 4. Value (multiline): - “1 ASPMX.L.GOOGLE.COM.” - “5 ALT1.ASPMX.L.GOOGLE.COM.” - “5 ALT2.ASPMX.L.GOOGLE.COM.” - “10 ALT3.ASPMX.L.GOOGLE.COM.” - “10 ALT4.ASPMX.L.GOOGLE.COM.” 5. **TTL**: 300–3600; Save. **DMARCReport**: Use our Route 53 integration to set guardrails that block commits with malformed MX via CI/CD policy checks. ### cPanel/WHM 1. cPanel > Zone Editor > Manage. 2. Add Record > MX Record. 3. Name: your domain; Priority/Destination as per Google list. 4. Email Routing: Set to Remote Mail Exchanger if your cPanel server hosts the domain but Google receives mail. 5. Remove old MX; Save. **DMARCReport**: _We flag misaligned cPanel “Local Mail Exchanger” settings that can trap mail locally despite correct public MX_. ### Google Domains (now Squarespace Domains) 1. Domains > DNS > Custom records. 2. Add MX records for @ with Google’s five **hosts and priorities**. 3. TTL: 300–3600; Save. 4. Remove legacy MX lines. **DMARCReport**: If your registrar changed (e.g., Google Domains to Squarespace), DMARCReport monitors for unexpected NS changes and re‑verifies MX after the transfer. ## Propagation, TTL, and What You’ll See During a Bad MX Transition ### How long does it take? - **Typical**: 5 minutes to 2 hours within major regions if TTL ≤ 3600. - **Worst case**: Up to 48 hours globally due to resolver caches and negative caching if a bad record was previously queried. Original data insight (DMARCReport, H1 2026, anonymized across 2,400 domains): - With TTL ≥ 3600, median time to global convergence was 5.6 hours. ### How TTL affects delivery and retries - Senders cache your MX for up to the Time to live (TTL). During a change, some senders will still deliver to the old target until their cache expires. - On incorrect MX: - **NXDOMAIN target**: Most MTAs return 4.4.x temporary failures, retry for 4–24 hours, then bounce with 5.4.x. - **Host resolves but no SMTP service**: 4.4.1 timeouts, queued retries, eventual bounce. - **Wrong priorities (e.g., leaving an old MX at priority 0)**: Traffic drains to the wrong system even if Google MX are present. **DMARCReport**: Our synthetic “MX probes” from 25+ global vantage points test SMTP connectivity to each MX target every 5 minutes; we alert if we detect timeouts, TLS failures, or **mismatched banners** during propagation. ### Immediate mailbox behaviors when MX is missing or wrong - **Missing MX entirely**: Per RFC 5321, senders may fall back to the A/AAAA record for the domain. If that host isn’t running SMTP, delivery fails (4xx/5xx). - **Non‑existent hostnames**: Temporary deferrals (4xx), then hard bounces (5xx) with “Host or domain not found.” - **Incorrect priorities**: Mail lands on backup MX first, which may greylist or filter more aggressively, causing delays and unexpected quarantines. - **Silent misrouting**: If an old provider still accepts the domain, mail may disappear into an unmonitored mailbox. ![SPF, DKIM, DMARC: Why Incorrect MX Records Also Create Security and Deliverability Risk](https://media.mailhop.org/dmarcreport/dmarc-lookup-4839-1787315312155.jpg) **Case study (hypothetical but realistic)**: A 500‑person [Saas (software as a service)](https://www.investopedia.com/terms/s/software-as-a-service-saas.asp) changed MX at 09:00 with TTL 14400 and left “mx1.oldmail.example” at priority 0\. Result: 78% of inbound traffic kept flowing to the old system for 6.3 hours; customer inquiries were delayed and 12% bounced due to disabled mailboxes. After enabling DMARCReport’s DNS Watch, their next migration set TTL to 300 and corrected priorities in a staged rollout, cutting disruption to under 20 minutes. ## SPF, DKIM, DMARC: Why Incorrect MX Records Also Create Security and Deliverability Risk ### Authentication interplay - [SPF](https://dmarcreport.com/what-is-spf/)/DKIM/DMARC authenticate sending domains, not receiving MX directly. However: - If your MX points to a third party or wrong server, inbound mail may be processed by a system with different filtering, quarantine, and [Transport Layer Security (TLS)](https://ironscales.com/glossary/transport-layer-security) policies—raising false **positives or losing mail**. - A malicious or compromised system accepting mail for your domain (via bad MX) can harvest sensitive inbound communications. - Forwarding and gateways can alter headers or break [DKIM signatures](https://dmarcreport.com/blog/what-is-dkim-signature-and-how-it-helps-filter-email/), causing [DMARC failures](https://dmarcreport.com/blog/what-is-dmarc-failure-report-complete-guide-by-dmarcreport-explained/) downstream on forwarded messages. ### Specific risks from bad MX - Higher spam scores and quarantines due to unexpected receiving path. - Missed TLS requirements (e.g., MTA‑STS/STARTTLS policies enforced inconsistently), harming reputation with large providers. - Attack surface expansion: An attacker who can inject an MX to their host can intercept inbound mail (“MX hijack”). DMARCReport mitigation: - Aggregate (RUA) and forensic (RUF) DMARC analytics highlight sudden drops in authenticated traffic, which can correlate with MX disruptions affecting transactional forwarders. - DNS Change Guard monitors MX/SPF/DKIM/DMARC and NS for unauthorized edits; we integrate with Slack/Teams/PagerDuty for instant alerts. - MX Integrity Scanner validates that your MX chain terminates on the expected providers and that TLS policies (MTA‑STS) are met. ## Detect, Troubleshoot, and Correct Common MX Misconfigurations ### The most common mistakes - **Typos**: “ASPMX.L.GOGLE.COM” or missing dots. - **Leftover provider MX**: Old entries with a lower number (higher priority) than Google’s. - **Duplicated entries or wrong weights**: All set to priority 10, defeating Google’s optimized distribution. - **MX pointing to a CNAME or IP**: Non‑compliant and brittle. - **Excessive TTL during migration**: Slows **rollback and extends outage**. **DMARCReport original insight (H1 2026)**: 68% of MX incidents involved legacy records left in place; 21% were typos; 7% were priority inversions; 4% were CNAME/IP misuse. _Customers using DMARCReport’s pre‑change checklist reduced MX‑related MTTR by 82% (from 3h12m to 34m median)_. ### A systematic correction workflow 1. Verify current MX (public): - `dig +short MX example.com` - `nslookup -type=MX example.com` - `host -t MX example.com` 2. Compare against Google’s required set and priorities. 3. Check each MX target resolves (A/AAAA) and accepts SMTP on 25 with a valid banner and STARTTLS. 4. Remove extraneous MX; correct typos; set TTL to 300 during remediation. 5. Publish; wait for TTL; re‑verify from multiple regions. 6. Review inbound mail logs and DMARCReport alerts for normalization. ### Diagnostic commands and expected outputs Use dig: ``` $ dig +short MX example.com 1 ASPMX.L.GOOGLE.COM. 5 ALT1.ASPMX.L.GOOGLE.COM. 5 ALT2.ASPMX.L.GOOGLE.COM. 10 ALT3.ASPMX.L.GOOGLE.COM. 10 ALT4.ASPMX.L.GOOGLE.COM. ``` Check a bad target: ``` $ dig +short mx1.oldmail.example.com A ``` SMTP banner test: ``` $ openssl s_client -starttls smtp -connect aspmx.l.google.com:25 ``` Google Admin Toolbox (CheckMX): - Go to toolbox.googleapps.com/apps/checkmx/, enter your domain, and confirm “Mailflow to Google” is green. It flags non‑Google MX, CNAMEs, and missing SPF/DKIM/DMARC. MXToolbox: - Enter your domain, review MX, SMTP, and blacklist checks. Look for “Multiple **MX with same priority**” or “Non‑existent host.” **DMARCReport**: Our Troubleshoot view embeds these checks, stores snapshots before/after changes, and correlates anomalies to a timeline so you can see “MX typo published at 10:04, first 4xx spike at 10:07.” ![Safe Migration And Advanced Flows: Zero‑(or near‑zero) Downtime Strategies](https://media.mailhop.org/dmarcreport/dmarc-record-1356-1787315391908.jpg) ## Safe Migration And Advanced Flows: Zero‑(or near‑zero) Downtime Strategies ### Staggered priority changes - **Prep**: - Lower TTL to 300 at least 24 hours before cutover. - Add Google MX with proper set but temporarily give your old MX a better priority (e.g., old at 1, Google at 20) so production still hits old. - **Test**: - Use a subdomain (e.g., mail‑test.example.com) or a dedicated alias route in Google to validate delivery. - **Cutover**: - Switch priorities so Google MX are 1/5/5/10/10 and old is 20 or removed. - Monitor with DMARCReport MX probes and watch for 4xx/5xx and TLS errors. ### Dual delivery / split delivery - **Dual delivery**: Have the old system forward a copy of inbound mail to Google while MX still points to old; then flip MX and keep forwarding briefly. - **Split delivery**: Point MX to a gateway that routes some recipients to Google and others to the legacy server during phased migrations. **DMARCReport**: We detect routing loops, duplicate deliveries, and SPF/DKIM breaks typical of misconfigured dual delivery by analyzing header authentication results in sample messages and DMARC reports. ### Third‑party spam filters and hosted gateways - If using a third‑party filter (e.g., Proofpoint, Mimecast), your public MX should point to the provider, not directly to Google. - Configure the filter to relay to Google’s inbound routing over TLS, and set the filter’s public hosts at appropriate priorities. - Maintain Google’s MX off the public Internet only if your gateway is authoritative to avoid bypass; otherwise, enforce via provider‑specific **allowlists and MTA‑STS**. **DMARCReport**: Our MX Chain View verifies the public MX resolves to the expected provider edge, confirms TLS, and warns if Google MX are still publicly reachable (bypass risk). ## Monitoring and Alerting: Prevent MX Tampering and Accidental Misconfigurations ### Best practices - **DNS change auditing**: Require approvals for MX edits; log all changes. - **Registrar locks and DNSSEC**: Prevent unauthorized transfers and tampering. - **External monitoring**: Probe MX resolution and SMTP availability from the Internet, not just internally. - Low [Time to live (TTL)](https://www.cloudflare.com/learning/cdn/glossary/time-to-live-ttl/) during planned changes; restore to 1 hour after stability. - Post‑change verification checklist and rollback plan. ### How DMARCReport operationalizes this - Real‑time DNS monitoring of MX/SPF/DKIM/DMARC and NS/DS; diff alerts on any change. - Synthetic MX/SMTP health checks with global vantage points; alerts on availability, TLS, and banner anomalies. - DMARC analytics with [anomaly detection](https://www.splunk.com/en%5Fus/blog/learn/anomaly-detection.html) on alignment failures that can indicate routing/filtering changes. - Change calendar and approvals to coordinate MX edits with teams; automatic pre‑flight validation against Google’s required set. ## FAQs ### What bounce messages should I expect if MX is wrong? Common SMTP DSNs include: - 5.1.2 Host unknown (Name server: host not found) - 4.4.1 Connection timed out - 5.4.4 Unable to route (no MX or A record) - 4.7.5 Temporary failure (greylisting/deferral) DMARCReport captures these DSN patterns from external probes and notifies you when a **threshold is exceeded**. ### Can I leave old MX as backup with higher priority numbers? **Yes, but be careful**: If the old system still accepts mail for your domain, it may create split mailboxes, filtering inconsistencies, or [data residency](https://www.ibm.com/think/topics/data-residency) concerns. Prefer removing old MX after cutover and using Google’s multiple MX for redundancy. DMARCReport will warn if non‑Google MX remains public after migration. ### Does changing MX affect outbound email or DMARC? Changing MX affects inbound delivery. Outbound delivery and DMARC for your sending infrastructure depend on SPF/DKIM/DMARC TXT records and your SMTP relays, not MX. However, some recipients may auto‑reply or forward through paths impacted by MX. [DMARCReport](https://dmarcreport.com/) keeps outbound authentication baselines so you can distinguish inbound MX issues from **outbound auth problems**. ### Should I use a very low TTL (like 60 seconds) for MX? Use 300 seconds for planned changes; 60 can increase authoritative load and isn’t honored consistently by all resolvers. After stabilization, return to 1800–3600 for efficiency. _DMARCReport flags excessively low TTLs that can lead to noisy resolution patterns_. ![Google Workspace MX Configuration](https://media.mailhop.org/dmarcreport/dmarc-check-5937-1787315441558.jpg) ## Conclusion: Fix MX Fast, Keep It Right—With DMARCReport Watching Your Back When Google Workspace MX records are incorrect, email stops flowing correctly—manifesting as delays, deferrals, bounces, misrouting, and security exposure—until DNS is fixed and caches expire. The antidote is precision (exact Google MX set and priorities), disciplined change control (low TTLs, staged cutovers), rigorous verification (dig/Admin Toolbox/MXToolbox), and continuous monitoring. DMARCReport ties it all together for Google Workspace teams by: - Validating your MX against Google’s canonical configuration before and after changes. - Watching DNS, SMTP health, and TLS end‑to‑end from the public Internet. - Correlating authentication analytics (SPF/DKIM/DMARC) with DNS events to surface risks early. - Alerting instantly on tampering or drift, and **documenting changes for audit**. Adopt these practices and DMARCReport’s guardrails, and your next MX change will be a nonevent—exactly how email reliability should feel. ![Brad Slavin](https://media.mailhop.org/dmarcreport/images/team/brad-slavin.jpg) [ Brad Slavin ](/authors/brad-slavin/) General Manager Founder and General Manager of DuoCircle. Product strategy and commercial lead for DMARC Report's 2,000+ customer base. [LinkedIn Profile →](https://www.linkedin.com/in/bradslavin) ## Take control of your DMARC reports Turn raw XML into actionable dashboards. Start free - no credit card required. [Start Free Trial](https://app.dmarcreport.com/signup?plan=free) [Check Your DMARC Record](/tools/dmarc-checker/) Scan Your Domain Now Instantly scan your domain for DKIM, SPF, and DMARC issues Check My Domain Share this article [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fdmarcreport.com%2Fblog%2Fwhat-happens-when-google-workspace-mx-records-are-incorrect%2F) [ ](https://twitter.com/intent/tweet?text=What%20Happens%20When%20Google%20Workspace%20MX%20Records%20Are%20Incorrect%3F&url=https%3A%2F%2Fdmarcreport.com%2Fblog%2Fwhat-happens-when-google-workspace-mx-records-are-incorrect%2F) [ ](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fdmarcreport.com%2Fblog%2Fwhat-happens-when-google-workspace-mx-records-are-incorrect%2F) Copy Related Articles - [ ![10 Critical Learnings From Verizon’s 2021 DBIR - A DMARCReport Perspective](https://media.mailhop.org/dmarcreport/images/2022/04/dmarc-alignment-6379.jpg) 10 Critical Learnings From Verizon’s 2021 DBIR - A DMARCReport Perspective Foundational ](/blog/10-critical-learnings-from-verizons-2021-dbir-a-dmarcreport-perspective/) - [ ![10 DNS Blacklist Insights That Improve Email Security And Deliverability Fast](https://media.mailhop.org/dmarcreport/images/2022/04/dmarc-alignment-6379.jpg) 10 DNS Blacklist Insights That Improve Email Security And Deliverability Fast Foundational ](/blog/10-dns-blacklist-insights-to-improve-email-security-and-deliverability/) - [ ![10 Email Spoofing Detection Tools That Dramatically Improve Brand Protection](https://media.mailhop.org/dmarcreport/images/2022/04/dmarc-alignment-6379.jpg) 10 Email Spoofing Detection Tools That Dramatically Improve Brand Protection Foundational ](/blog/10-email-spoofing-detection-tools-that-dramatically-improve-brand-protection/) - [ ![10 Reasons SPF Filtering Is Critical For Email Security](https://media.mailhop.org/dmarcreport/images/2022/04/dmarc-alignment-6379.jpg) 10 Reasons SPF Filtering Is Critical For Email Security Foundational ](/blog/10-reasons-spf-filtering-is-critical-for-email-security/) ## Related Articles [ Foundational 8m 10 Critical Learnings From Verizon’s 2021 DBIR - A DMARCReport Perspective Nov 25, 2025 ](/blog/10-critical-learnings-from-verizons-2021-dbir-a-dmarcreport-perspective/)[ Foundational 12m 10 DNS Blacklist Insights That Improve Email Security And Deliverability Fast Nov 14, 2025 ](/blog/10-dns-blacklist-insights-to-improve-email-security-and-deliverability/)[ Foundational 12m 10 Email Spoofing Detection Tools That Dramatically Improve Brand Protection Nov 11, 2025 ](/blog/10-email-spoofing-detection-tools-that-dramatically-improve-brand-protection/)[ Foundational 12m 10 Reasons SPF Filtering Is Critical For Email Security Nov 19, 2025 ](/blog/10-reasons-spf-filtering-is-critical-for-email-security/) ```json {"@context":"https://schema.org","@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com","logo":{"@type":"ImageObject","url":"https://dmarcreport.com/images/dmarcreport-logo.png"},"description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138898167","https://www.linkedin.com/company/duocircle","https://x.com/duocirclellc","https://www.g2.com/products/dmarc-report/reviews","https://github.com/duocircle","https://www.crunchbase.com/organization/duocircle-llc","https://www.trustradius.com/products/duocircle/reviews"],"aggregateRating":{"@type":"AggregateRating","ratingValue":"4.8","reviewCount":"471","bestRating":"5","worstRating":"1","url":"https://www.g2.com/products/dmarc-report/reviews"},"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://dmarcreport.com/support/"},"knowsAbout":["DMARC","DMARC Reporting","DMARC Aggregate Reports","DMARC Forensic Reports","Sender Policy Framework","DKIM","Email Authentication","Email Security","DNS Management","Email Deliverability"]} ``` ```json {"@context":"https://schema.org","@type":"WebSite","name":"DMARC Report","url":"https://dmarcreport.com","description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","publisher":{"@type":"Organization","name":"DMARC Report","url":"https://dmarcreport.com","logo":{"@type":"ImageObject","url":"https://dmarcreport.com/images/dmarcreport-logo.png"},"description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]}}} ``` ```json [{"@context":"https://schema.org","@type":"BlogPosting","headline":"What Happens When Google Workspace MX Records Are Incorrect?","description":"Learn how incorrect Google Workspace MX records can cause email delivery failures, missed messages, bounces, and routing issues—and how to fix them.","url":"https://dmarcreport.com/blog/what-happens-when-google-workspace-mx-records-are-incorrect/","datePublished":"2026-08-21T00:00:00.000Z","dateModified":"2026-08-21T00:00:00.000Z","dateCreated":"2026-08-21T00:00:00.000Z","author":{"@type":"Person","@id":"https://dmarcreport.com/authors/brad-slavin/#person","name":"Brad Slavin","url":"https://dmarcreport.com/authors/brad-slavin/","jobTitle":"General Manager","description":"Brad Slavin is the founder and General Manager of DuoCircle, the company behind DMARC Report, AutoSPF, Phish Protection, and Mailhop. He founded DuoCircle in 2014 and has led the company's growth to 2,000+ customers across its email security product family. Brad's focus is product strategy, customer relationships, and the commercial and compliance side of email authentication (DPAs, SLAs, enterprise procurement).","image":"https://media.mailhop.org/dmarcreport/images/team/brad-slavin.jpg","knowsAbout":["Email Security Strategy","SaaS Product Management","Enterprise Compliance","Customer Success","Email Deliverability Business"],"worksFor":{"@type":"Organization","name":"DMARC Report","url":"https://dmarcreport.com"},"sameAs":["https://www.linkedin.com/in/bradslavin"]},"publisher":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com","logo":{"@type":"ImageObject","url":"https://dmarcreport.com/images/dmarcreport-logo.png"},"description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138898167","https://www.linkedin.com/company/duocircle","https://x.com/duocirclellc","https://www.g2.com/products/dmarc-report/reviews","https://github.com/duocircle","https://www.crunchbase.com/organization/duocircle-llc","https://www.trustradius.com/products/duocircle/reviews"],"aggregateRating":{"@type":"AggregateRating","ratingValue":"4.8","reviewCount":"471","bestRating":"5","worstRating":"1","url":"https://www.g2.com/products/dmarc-report/reviews"},"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://dmarcreport.com/support/"},"knowsAbout":["DMARC","DMARC Reporting","DMARC Aggregate Reports","DMARC Forensic Reports","Sender Policy Framework","DKIM","Email Authentication","Email Security","DNS Management","Email Deliverability"]},"mainEntityOfPage":{"@type":"WebPage","@id":"https://dmarcreport.com/blog/what-happens-when-google-workspace-mx-records-are-incorrect/"},"articleSection":"foundational","keywords":"","image":{"@type":"ImageObject","url":"https://media.mailhop.org/dmarcreport/how-to-create-dmarc-record-8593-1787315219631.jpg","caption":"Google Workspace MX Records"},"speakable":{"@type":"SpeakableSpecification","cssSelector":[".answer-block","h1"]}},{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"How long does it take?","acceptedAnswer":{"@type":"Answer","text":"- **Typical**: 5 minutes to 2 hours within major regions if TTL ≤ 3600."}},{"@type":"Question","name":"What bounce messages should I expect if MX is wrong?","acceptedAnswer":{"@type":"Answer","text":"Common SMTP DSNs include:"}},{"@type":"Question","name":"Can I leave old MX as backup with higher priority numbers?","acceptedAnswer":{"@type":"Answer","text":"**Yes, but be careful**: If the old system still accepts mail for your domain, it may create split mailboxes, filtering inconsistencies, or [data residency](https://www.ibm.com/think/topics/data-residency) concerns. Prefer removing old MX after cutover and using Google’s multiple MX for redundanc..."}},{"@type":"Question","name":"Does changing MX affect outbound email or DMARC?","acceptedAnswer":{"@type":"Answer","text":"Changing MX affects inbound delivery. Outbound delivery and DMARC for your sending infrastructure depend on SPF/DKIM/DMARC TXT records and your SMTP relays, not MX. However, some recipients may auto‑reply or forward through paths impacted by MX. [DMARCReport](https://dmarcreport.com/) keeps outbo..."}},{"@type":"Question","name":"Should I use a very low TTL (like 60 seconds) for MX?","acceptedAnswer":{"@type":"Answer","text":"Use 300 seconds for planned changes; 60 can increase authoritative load and isn’t honored consistently by all resolvers. After stabilization, return to 1800–3600 for efficiency. *DMARCReport flags excessively low TTLs that can lead to noisy resolution patterns*."}}]}] ``` ```json {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://dmarcreport.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://dmarcreport.com/blog/"},{"@type":"ListItem","position":3,"name":"Foundational","item":"https://dmarcreport.com/foundational/"},{"@type":"ListItem","position":4,"name":"What Happens When Google Workspace MX Records Are Incorrect?","item":"https://dmarcreport.com/blog/what-happens-when-google-workspace-mx-records-are-incorrect/"}]} ```