Verify MX Records for HubSpot

Why MX Record Verification Matters for HubSpot Users

You just set up a custom domain in HubSpot. Great. Now incoming emails from leads and customers need a clear path. But if your MX record configuration is off by a single character, those messages vanish into the void.

Outbound emails from HubSpot are predictable. Inbound? Not unless your MX records are verified and correct. A misconfigured MX record means missed opportunities, delayed responses, and support teams playing catch-up. It’s silent, but it’s costly.

Verifying MX record configuration for HubSpot connected domains isn't just a technical step — it’s an operational necessity. When inbound mail routing fails, it’s not the sales team’s fault. It’s infrastructure. And this guide shows you how to catch it before it breaks your pipeline.

Key takeaways

MX records must point to your email provider’s servers, not HubSpot, to receive inbound emails.
A single typo in an MX record can cause all inbound emails to be lost or flagged as spam.
Verifying MX configuration ensures HubSpot’s inbound email system works as expected across external mail servers.

What Happens if MX Records Are Invalid or Missing?

If your HubSpot-connected domain lacks a valid MX record, emails sent to that domain won’t reach inboxes. Messages may bounce, forms stop capturing leads, and customer support via your brand domain fails. This breaks trust, delays responses, and can damage your reputation. Let’s break down why.

Delivery Fails Before It Starts

MX records are the roadmap for email delivery. Without them, mail servers don’t know where to deliver messages. If the record is missing or points to an unreachable server, incoming messages are rejected or silently dropped. This is not a minor glitch—it’s a hard failure at the network level. According to RFC 5321, the foundation of SMTP, no mail transfer happens without a valid MX target.

HubSpot Form Submissions Can Be Lost

HubSpot relies on your domain’s MX record to properly route incoming emails from forms or support tickets. If the record is invalid, HubSpot cannot receive confirmation emails or track responses. You might see no error in HubSpot, but the form submitter gets no response—leading to frustrated users and lost engagement. A missing or wrong MX record breaks this flow silently.

Even worse, if you use your brand domain (like [email protected]) for customer inquiries, invalid MX records mean customers don’t get replies. That’s not just a technical issue—it’s a customer service failure. For sales and service teams, this erodes credibility and slows response times.

It’s not just inbound mail that suffers. Outbound emails from HubSpot may also face deliverability issues if your domain’s configuration is inconsistent. ISPs like Gmail and Outlook check DNS records—including MX—as part of their spam filters. An incomplete or misconfigured domain can flag your entire sending reputation.

Before you send emails or rely on form submissions, verify your MX records. Use tools like MailTester’s inbox placement test to simulate messages and check if your domain’s configuration allows delivery. You can also test individual domains with the real-time verification API, or batch-validate your entire list with bulk email verification.

How to Verify MX Record Configuration for HubSpot Domains

You can verify your HubSpot domain's MX record by logging into your domain’s DNS provider, locating the MX record, ensuring it points to inbound.hubspot.com or mail.hubspot.com with a priority of 10, saving the changes, and waiting up to 48 hours for propagation. This step ensures inbound emails reach HubSpot’s servers correctly, preventing delivery failures and improving inbox placement for your campaigns.

Step-by-Step: Confirm Your MX Record with HubSpot

Log into your domain’s DNS provider — use your account at GoDaddy, Cloudflare, Namecheap, or another registrar. This is where you manage your domain’s email routing.
Navigate to the DNS records section — look for a tab or menu labeled "DNS Management," "Zone File," or "DNS Records." This is where MX, SPF, and DKIM settings are configured.
Locate your domain’s MX record — search for a record type marked as "MX" (Mail Exchange). It may be listed under a name like @, your domain, or subdomain. If multiple records exist, ensure only one is active, or set priorities correctly.
Verify the mail server destination — the MX record value must point to inbound.hubspot.com or mail.hubspot.com. Using the wrong server redirects emails to incorrect services, causing delivery failures.
Check that the priority is set to 10 — HubSpot requires a standard priority of 10. This determines the order in which mail servers are tried. If priority is misconfigured (e.g., 0 or 50), messages might not be routed properly.
Save changes and wait for propagation — after updating, save your changes. DNS propagation typically takes 1 to 48 hours, depending on your provider’s TTL settings. Use tools like MxToolbox to verify live updates.

Why This Matters for Delivery and Deliverability

Incorrect MX records break inbound email handling — even if your sender reputation is strong, messages to your HubSpot-connected domains may fail to reach their destination. This creates gaps in lead capture, weakens customer engagement, and can indirectly hurt your domain reputation.

Tools like MailTester’s inbox placement tester can help validate whether your configurations result in real inbox delivery, not just DNS success. Regular checks are a standard practice in maintainable email systems.

Proper MX configuration is a foundational layer — no amount of well-written email will reach the inbox if the mail routing is broken.

For teams managing bulk sends or integrated marketing workflows, validating records with every domain change reduces risk. Consider using an email verification service like MailTester’s bulk verification to catch invalid or incorrectly configured email addresses before sending. You can check thousands of leads at once and identify delivery issues early.

How MailTester Validates MX Record Configuration

You can verify MX record configuration for HubSpot connected domains using real-time DNS checks that confirm the record exists, points to HubSpot’s mail servers, and is properly formatted with correct priorities. MailTester returns results in seconds with clear pass/fail status and precise feedback on what’s wrong—no guesswork.

Real-Time DNS Inspection

When you test a domain, MailTester performs an immediate query against public DNS servers to retrieve the MX record. This isn’t a cached or simulated lookup—it’s a live check that mirrors how email providers see your domain in real time.

We probe the exact record structure: type (MX), name (domain), priority number, and target (e.g., inbound-smtp-eu-west-1.amazon.com). If the target differs from HubSpot's accepted mail servers, we flag it immediately. Even small errors like a trailing dot or missing space in the target break delivery.

What the Test Flags

Missing MX records are caught instantly—no record means inbound messages will fail. Incorrect targets, like pointing to a legacy SMTP server or a non-HubSpot domain, are highlighted with specific warnings. Priority issues, such as using 10 when the system expects 0 or 5, are also detected.

These problems aren't just theoretical. According to RFC 5321 (the core SMTP standard), MX records must be correctly formatted and directed to valid, responsive mail servers. A misconfigured record leads directly to inbound mail rejection or indefinite delay.

For teams using HubSpot, a single misconfigured MX record can break lead capture forms, customer support emails, and campaign tracking. MailTester identifies and reports these flaws before they impact your send volume or response time.

Each test result shows exactly what passed, what failed, and how to fix it—no ambiguity. You get actionable feedback, not vague diagnostics.

Whether you’re verifying one domain or hundreds, you can run bulk checks through our email list verification tool or integrate real-time validation into your workflow with our email verification API. Test inbox placement with confidence using our inbox placement tool. All with 98.9% accuracy, and credits that never expire.

Common MX Record Mistakes with HubSpot

You're likely missing emails, seeing poor deliverability, or hitting unexpected bounces because your MX records aren't correctly configured for HubSpot. Legacy settings, priority errors, typos, or duplicate records all break inbound mail flow. Fixing these is a quick win — and checking them regularly keeps your domain trustworthy. Let's walk through the most common issues.

Legacy and Incorrect MX Settings

Using an old MX record from a previous email provider (like Gmail or Outlook) prevents HubSpot from receiving inbound emails. HubSpot requires mail.hubspot.com as the target.
Setting a priority higher than 10 reduces delivery priority. MX records should use a priority of 10 or lower — priorities above 10 are treated as low priority, meaning messages may be delayed or dropped.
A common spelling error is mail.hubspot.com vs. mailhubspot.com. Even a single character misstep breaks the MX lookup chain and stops delivery.
Multiple MX records with conflicting priorities (e.g., one at 10 and another at 5) confuse mail servers. Always use a single, correct MX record pointing to mail.hubspot.com with priority 10.

Validation and Verification

Even if your record looks right on paper, it must resolve correctly at DNS level. A record may be wrong on the control panel but propagate correctly across the internet — or vice versa. Use a real-time DNS check with a trusted tool like MXToolbox to validate the actual result.

When you're setting up HubSpot, verify every MX record before relying on it. For bulk domains or frequent changes, run pre-send checks with a service like MailTester’s bulk verification—not just for email addresses, but for domain-level deliverability health.

How to Use MailTester’s Integration with HubSpot

You can verify MX record configuration for HubSpot connected domains by linking your HubSpot account to MailTester via the HubSpot Marketplace app. Once connected, your domains sync automatically, allowing you to run bulk MX verification, check DNS status across your portfolio, and export clean reports. This process ensures your sending domains are properly configured to avoid delivery issues.

Connect your HubSpot account to MailTester using the app in the HubSpot Marketplace. This grants MailTester read access to your domains and their associated DNS settings. The integration is secured via OAuth, a standard method used to protect user data.
Select the domains you want to verify. After connecting, MailTester automatically pulls your HubSpot-connected domains. You can now choose which domains to include in your MX validation scan, letting you focus on active or high-priority sending domains.
Run a bulk MX verification. With your domains selected, initiate a bulk verification using MailTester’s DNS validation engine. It checks your MX record configuration in real time, confirming if they’re pointing to valid mail servers and properly prioritized.
Review results and export reports. In your MailTester dashboard, filter results by domain, status, or error type (e.g., missing MX, invalid server, misconfigured TTL). You can export a CSV report with domain status, MX results, and timestamps — useful for audit trails or internal sharing.
Use the real-time API during onboarding. For new domain setups in HubSpot, embed the MailTester API to verify MX records instantly. This prevents sending failures by catching misconfigurations before your first campaign goes live. You can check the status of any domain using a simple API call.

The 5 steps described in “How to Use MailTester’s Integration with HubSpot”, in order.

Why This Matters for Deliverability

MX record misconfigurations are a leading cause of email delivery failures. According to the RFC 5321 specification, proper MX resolution is required for mail servers to accept inbound messages. A single incorrect or missing MX can result in bounces, poor sender reputation, or inbox placement failure across ESPs like Gmail and Outlook.

MailTester’s integration with HubSpot ensures you’re not relying on guesswork. Instead, you validate actual network behavior. This helps identify issues like catch-all domains, greylisting, or role account usage—common pitfalls that affect engagement and deliverability. You’ll catch these before they hurt your sender score.

Next Steps and Tools

Use the bulk verification feature to audit your full domain list: verify your full email list. For automated processes, integrate the real-time API: verify domains on demand. Want to test inbox placement before sending? Use our inbox placement tester. All plans include 100 free verifications, and credits never expire — see full details at pricing.

When to Re-Verify MX Records After Changes

Always re-verify MX record configuration for HubSpot connected domains immediately after making DNS changes, switching email providers, migrating infrastructure, launching campaigns, or receiving bounce messages. MX records can take time to propagate, and even small misconfigurations can block inbound emails. Use a live verification tool to confirm your setup is working before relying on it for lead capture or support.

When to Act Immediately

After updating DNS entries for your domain — even minor changes to MX priority or target can break delivery.
When migrating email infrastructure or switching providers — outdated or inconsistent MX records cause inbox failures.
Before launching any new campaign or lead form in HubSpot — verify the domain’s MX setup to ensure inbound emails from prospects aren’t rejected.
When you receive bounce messages indicating "Mailbox not found" or "Connection refused" — these often point to incorrect or missing MX records.

Why Verification Matters

MX records tell the internet where to deliver email for your domain. If they point to a non-existent or misconfigured server, inbound messages fail silently. According to RFC 5321, proper MX resolution is a fundamental step in reliable email delivery. Delays in propagation can last up to 48 hours, but verification ensures your configuration takes effect correctly before you depend on it.

Let’s be clear: DNS is not static. It’s a distributed system with caching — even if you configure correctly, intermediaries may still serve stale data. That’s why you shouldn’t trust a change just because it's been published.

Real-time verification tools like MailTester’s bulk verification can validate your domain’s MX response across multiple email providers, catching issues early. The same applies to MailTester’s API, which lets developers insert verification into automated workflows.

Don't assume DNS is correct. Verify it — especially when it affects lead capture.

Running a test campaign or form? Use MailTester’s inbox placement tester to simulate real delivery and confirm both MX records and inbound deliverability are functioning. This catches problems before your sales team sees a drop in lead volume.

What MailTester’s MX Verification Tells You Beyond 'Valid/Invalid'

You don't just get a yes/no on MX validity—MailTester checks if the record actually routes to a live mail server, confirms proper DNS propagation, flags misconfigured or non-HubSpot targets, and warns about outdated or unreachable servers. This goes beyond surface-level checks to catch real delivery risks before they impact your campaigns.

It Confirms Active, Correct Mail Server Targets

Not every MX record is functional. A valid DNS record doesn’t mean the server responds. MailTester verifies that the target domain in the MX record resolves to an actual, active mail server. If the server doesn’t accept connections or is unreachable, you’ll see a warning—even if the DNS is technically correct.

HubSpot relies on specific infrastructure. If your MX record points to an old or unassigned email system, your inbound emails won’t deliver. MailTester surfaces these issues early, so you don’t assume a setup is working just because DNS says it is.

It Catches Propagation Delays and Misconfigurations

DNS changes don’t take effect instantly. Even if your MX record appears correct in a tool like MXToolbox, it might not have propagated globally yet. MailTester tests from multiple geolocations to detect this delay, helping you avoid false positives during setup.

Some records point to non-HubSpot domains, like old email providers or unused subdomains. MailTester flags these as high-risk, even if they’re technically valid. A target like mail.example.com with no known mail service behind it can cause delivery failures or trigger spam filters.

For instance, an MX record listing mail.google.com for a domain not associated with Google’s systems will fail delivery—even if the DNS is correct. MailTester detects such mismatches and alerts you to fix them before sending to that domain.

These checks matter. According to RFC 5321, the SMTP standard, mail servers must respond to connection attempts. If they don’t, the sender must fail with a clear error—MailTester simulates this step so you don’t need to wait for real bounces.

Every verified domain gives you confidence. Use MailTester’s bulk verification to spot problems across your list, or integrate our real-time API for on-the-fly validation. You’re not just checking syntax—you’re testing real-world deliverability.

How MX Verification Fits into HubSpot Domain Hygiene

You verify MX record configuration for HubSpot connected domains to ensure inbound emails can actually reach your inbox. Without correct MX records, messages fail silently or bounce, breaking customer communication. This check is foundational—valid MX records are the first line of defense in preventing delivery failure for both sending and receiving email.

MX Records: The Backbone of Inbound Reliability

When you connect a custom domain to HubSpot, you’re relying on DNS to route emails correctly. MX records tell mail servers where to deliver incoming messages. If these records are incorrect, missing, or misconfigured, inbound emails from leads or customers never land in your inbox—no matter how good your CRM setup is.

Let’s say you’re sending campaign replies through a HubSpot-connected domain. If the MX record isn’t set properly, replies bounce before they reach your team. That’s not just a nuisance—it erodes sender reputation over time, especially if those bounces are flagged as undeliverable by receivers.

Hygiene Goes Beyond the Inbox: Sending and Receiving Integrity

MX validation isn’t just about inbound flow. It’s part of a broader hygiene strategy that includes verifying individual email addresses and monitoring domain reputation. A domain with broken MX records often signals poor maintenance practices, which can indirectly weaken sender reputation.

Combine MX checks with real-time email verification—like using MailTester’s bulk verification or API—and you reduce sending failures. Valid addresses + valid MX records mean fewer bounces, better inbox placement, and sustained deliverability. In practice, this means fewer emails lost, fewer reputation risks.

According to the SMTP specification (RFC 5321), mail servers must accept or reject messages based on the presence and validity of MX records. The process is automated, and failures at that layer aren’t recoverable. That’s why checking MX records is not optional—it’s a baseline check.

For teams using HubSpot, this validation belongs in the onboarding workflow. It prevents the common mistake of assuming “if we’re using the domain in HubSpot, it should work.” It doesn’t. Not until the MX record is live and correct.

With MailTester, you can test inbox placement across providers via inbox placement tests, and integrate verification directly with HubSpot through our integrations—keeping your lists clean and domains reliable.

Why Use MailTester Instead of Free DNS Tools for HubSpot Verification

Free DNS tools tell you if an MX record exists—but not whether it’s correct for HubSpot. MailTester goes further: it validates the record against HubSpot’s official mail server list and explains mismatches. This saves time, prevents bounces, and keeps your sender reputation intact.

Not All MX Records Are Created Equal

Many free tools just check for the presence of an MX record. That’s not enough. A record might exist but point to outdated or incorrect servers—common with misconfigured domains or outdated DNS entries. MailTester doesn’t just scan; it cross-references every result against HubSpot’s known mail infrastructure, so you know if the record is valid in practice, not just in theory.

Let’s say your domain’s MX record points to an old mail server instead of HubSpot’s. A free tool will still say "record found." MailTester will flag it as invalid and explain why: "Record points to mx1.oldhost.com, not HubSpot’s approved IPs." This level of feedback helps you fix misconfigurations quickly and avoid deliverability issues.

Accuracy You Can Trust

MailTester’s 98.9% accuracy rate comes from real-time, multi-server verification. It doesn’t rely on cached data or outdated checks. Instead, it tests your domain’s MX configuration across actual mail servers that handle inbound traffic—similar to how email providers validate senders.

Industry standards like RFC 5321 and RFC 5322 define how mail servers should authenticate and route messages. Tools that ignore these standards or skip live validation often return false positives. MailTester aligns with these principles by testing actual server responses, not just DNS syntax.

If you're managing email campaigns in HubSpot, you need to know whether your domain is set up to receive messages reliably. Free tools can’t offer this insight. With MailTester, you get not just a yes/no answer, but a technical breakdown.

For teams using HubSpot at scale, this makes verification faster and more accurate. You can verify entire lists, integrate with your workflow, or test deliverability before sending. See how it works: bulk verification, real-time API checks, or inbox placement testing.

Start with 100 free verifications. Credits never expire. No setup, no risk. See pricing and take control of your domain verification today.

Final Steps: Maintain Reliable Inbound Email with HubSpot

Verification isn't a one-time task. Domains change, configurations shift, and inbound email reliability depends on consistent checks.

Use MailTester to verify all HubSpot-connected domains quarterly. This prevents unexpected bounces and maintains deliverability. Set up automated checks using the real-time API for new domain integrations—catch issues before they impact your inbox.

When a check fails, use the in-app AI assistant to interpret error messages and identify root causes. Keep a log of verified configurations for audits and team onboarding. Consistency builds trust with email providers and customers alike.

Sources

Google reported 265 billion fewer unauthenticated messages sent to Gmail users in 2024 — a 65% reduction — after its bulk-sender rules took effect, with 500,000+ top domains publishing DMARC records in response. — Google (via MailOver bulk-sender requirements guide) (2024)
Sending from a domain with at least three months of history improves inbox placement by 28% compared with a brand-new domain. — Woodpecker data (via WarmForge deliverability statistics) (2025)

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

Does MailTester verify MX records for all HubSpot domains?

Yes. You can verify any domain connected to HubSpot through the integration or by entering it directly in the MailTester dashboard.

What should the MX record target be for HubSpot domains?

The correct target is inbound.hubspot.com or mail.hubspot.com, with a priority of 10.

How long does it take for MX changes to propagate?

Propagation typically takes 1 to 48 hours, depending on your DNS provider and TTL settings.

Can I verify MX records before connecting a domain to HubSpot?

Yes. Verify the record ahead of time to avoid configuration errors during onboarding.

Does MailTester detect temporary DNS glitches?

Yes. It identifies unresolved records and propagation delays, but will not flag transient issues as permanent failures.

Can MailTester help with outbound email problems in HubSpot?

Only indirectly. It helps with inbound delivery by validating MX records but does not test SPF, DKIM, or DMARC.

Is there a limit to how many domains I can verify with MailTester?

No. You can verify any number of domains via bulk verification, API, or the HubSpot integration.

How accurate is MailTester's MX verification?

MailTester reports 98.9% accuracy based on real-time testing across multiple mail server endpoints.

Can I use MailTester’s API to verify MX records automatically?

Yes. The real-time verification API supports MX record checks as part of automated workflows.

Do I need prior DNS knowledge to use MailTester for MX verification?

Not if you use the integration or AI assistant. The tool explains results without assuming technical expertise.

Are free MX tools as reliable as MailTester?

No. Free tools often only confirm the existence of a record — not whether it's correct for HubSpot.

What happens if MailTester says my MX record is invalid?

Review your DNS provider settings for typos, incorrect targets, or outdated priorities, then re-check after updating.