Why SMTPUTF8 Compliance Is Non-Negotiable for Global Brands in 2026

You’re sending an email to a customer in Tokyo. The address is さくら@みずほメール.jp. It’s valid. It’s real. But your SMTP server rejects it. Not because it’s wrong — because it’s not UTF-8 compliant.

That’s the reality for brands still running outdated email infrastructure in 2026. As global email traffic expands beyond Latin scripts, support for non-ASCII characters isn’t optional — it’s a delivery requirement. SMTPUTF8 isn’t a feature upgrade. It’s a survival tool.

Configuring SMTP servers for SMTPUTF8 compliance in 2026 isn’t about flexibility. It’s about ensuring your messages reach inboxes across Japan, Germany, Arabic-speaking regions, and beyond — without failure, delay, or reputational damage.

Key takeaways

  • Gmail, Outlook, and Yahoo now require UTF-8 support for non-Latin email domains; legacy systems with ASCII-only validation will fail deliveries.
  • Failure to support SMTPUTF8 leads to authentication issues, higher bounce rates, and faster sender reputation degradation.
  • Global brands must proactively configure SMTP servers for UTF-8 processing to avoid delivery drops in markets with non-ASCII email usage.

How SMTPUTF8 Works: A Technical Breakdown of Extended Email Address Support

You can use non-ASCII characters—like Cyrillic, Arabic, or Han—in email addresses thanks to SMTPUTF8. This extension to SMTP allows Unicode in both local parts and domains, breaking the old 7-bit ASCII restriction. It's negotiated during the SMTP handshake via the SMTPUTF8 command, and if unsupported, the server will reject the address even if it’s otherwise valid.

The Handshake Signal: How Support is Detected

When a sender connects to an SMTP server, the client checks whether the server supports SMTPUTF8 by sending the SMTPUTF8 capability during the initial EHLO exchange. If the server responds with 250 SMTPUTF8, it confirms it can process Unicode addresses. Without this, your message may be rejected, even for otherwise correct addresses.

That’s why global brands with non-Latin domains or local parts must verify server readiness. If your server supports it, your message can route properly. If not, the connection fails early—often with a vague error. This is especially common with older or misconfigured systems.

Why It Matters for Global Brands

Domains in Russian, Chinese, Arabic, or Indian scripts are now common. Without SMTPUTF8, users in those regions can’t receive emails at their native-language addresses. This isn’t just about localization—it’s about deliverability. A valid email address can still be blocked if the receiving server doesn’t support Unicode processing.

For example, an email to пользователь@реклама.рф or क्रिकेट@स्पोर्ट्स.ईलो will fail if the destination server only understands ASCII. This leads to high bounce rates, poor inbox placement, and damaged sender reputation—especially for brands expanding into new markets.

Even if your email list uses valid non-ASCII addresses, sending to servers that don’t support SMTPUTF8 results in silent failures. That’s why verification isn’t just about format—it’s about whether your address will be accepted at the destination. Tools that check address syntax alone won’t catch this mismatch.

Let’s be clear: compliance isn’t optional for brands using non-Latin scripts. The IETF formally defined SMTPUTF8 in RFC 6531, and support is required for modern email delivery. But adoption across infrastructure remains uneven.

Before sending to international audiences, verify not just address format—but whether your SMTP server and your recipients’ servers support SMTPUTF8. Use a service that checks deliverability across real infrastructure, not just syntax.

For bulk lists with non-ASCII addresses, test deliverability through real SMTP connections. You can use inbox placement testing to see how your messages land in real inboxes across major providers—including Gmail, Outlook, and Yahoo—with full tracking of rejection reasons, including protocol-level failures.

SMTPUTF8 and Sender Reputation: The Hidden Cost of Non-Compliance

Domains that fail SMTPUTF8 checks during delivery are often treated as technically undermaintained, triggering spam filters and undermining sender reputation. Over time, repeated failures degrade performance scores across reputation systems, which track delivery success across protocols. Once reputation declines due to configuration issues, recovery is slow—even after fixes are applied—because systems prioritize long-term behavior over isolated corrections.

Why SMTPUTF8 Matters Beyond Syntax

SMTPUTF8 isn’t just about handling non-ASCII characters—it’s a signal of technical health. Major mailbox providers like Gmail and Outlook use SMTPUTF8 readiness as a subtle benchmark. A server that fails the check during delivery is flagged as lacking in operational rigor, even if the email content is benign.

Let’s be clear: reputation systems don’t operate on isolated events. They assess patterns over days, weeks, and months. Each failed SMTPUTF8 handshake adds weight to a negative profile. And because these systems correlate delivery behavior with server configuration, the root cause—even a misconfigured TLS handshake—can get blamed on poor governance.

Reputation Is Cumulative. Fixes Are Not Instant.

Once a sender’s reputation drops due to protocol-level issues like missing SMTPUTF8 support, recovery isn't automatic. The system needs sustained positive behavior—consistent delivery, low bounce rates, high engagement—over time to reverse the damage.

This is why early attention to SMTPUTF8 compliance isn’t just a technical chore. It’s part of preserving sender legitimacy. A server that still uses legacy configurations in 2026 risks being treated as outdated, even if the message itself is acceptable.

As RFC 6531 states, SMTPUTF8 is the standard for extending SMTP to support internationalized email addresses. Its adoption is no longer optional for global brands aiming for reliable inbox placement. Ignoring this standard reduces the margin of safety for high-volume senders, especially those using third-party platforms or hybrid infrastructure.

If you’re managing bulk sends or integrating with tools like Mailchimp or SendGrid, ensure your SMTP server configuration includes proper UTF8 support. The cost of compliance is low compared to the risk of being silently quarantined. Use a verification service to test deliverability across protocols before deployment.

Test your deliverability across real inboxes with a full inbox placement report. It’ll show you not just whether your message lands in the inbox, but also how your server configuration affects routing signals—like SMTPUTF8 readiness—across major email providers.

Configuring SMTP Servers for SMTPUTF8: A Step-by-Step Process

You can enable SMTPUTF8 on your MTA by verifying it supports the extension, updating the configuration file to enforce TLS and HELO checks, enabling SMTPUTF8 via mailer-specific settings (like smtpd_smtputf8_enable=yes in Postfix), testing advertised capability with tools like openssl s_client, and confirming delivery with actual UTF-8 email addresses like 你好@example.com. Let’s walk through each step.

Ensure MTA Support and Basic Configuration

  1. Confirm your MTA supports SMTPUTF8. Postfix, Exim, and patched versions of Sendmail include native support. Check your MTA’s documentation or release notes for SMTPUTF8 inclusion. RFC 6531 defines the baseline requirements.
  2. Verify TLS and HELO enforcement. In your MTA config (e.g. main.cf for Postfix), ensure smtpd_enforce_tls = yes and smtpd_helo_required = yes. These prevent insecure or spoofed mail sessions and are prerequisites for reliable SMTPUTF8 handling.

Enable SMTPUTF8 and Validate Functionality

  1. Enable the SMTPUTF8 extension. For Postfix, add smtpd_smtputf8_enable = yes in your main.cf. This allows the server to advertise and process UTF-8 encoded addresses during EHLO negotiation.
  2. Test capability during EHLO. Use openssl s_client -connect yourdomain.com:587 -starttls smtp and check the response after EHLO. Look for SMTPUTF8 in the list of supported extensions. If missing, the setting is not applied or the MTA lacks full support.
  3. Send a UTF-8 test email. Use a known valid UTF-8 address like 你好@example.com. If delivery succeeds and the recipient receives the email with the correct encoding, the setup is effective. If not, check logs for errors related to encoding or DNS resolution.

SMTPUTF8 isn’t just about support—it’s about reliability at scale. Global brands sending to international audiences must ensure their infrastructure can handle non-ASCII addresses without blocking or rejecting valid inboxes. Failure to verify this can lead to high bounce rates, poor deliverability, or delivery delays.

Even small misconfigurations in UTF-8 handling can cause mail to be silently rejected or misrouted—especially in regions where non-Latin scripts are common.

After confirming SMTPUTF8 works in your test environment, monitor logs and delivery reports. Real-world validation with diverse domains is essential. Use tools like inbox placement testing to verify that emails land in inboxes, not spam folders, across platforms like Gmail, Outlook, and Apple Mail.

How Email Verification Prevents SMTPUTF8 Failures Before They Happen

You can stop SMTPUTF8 delivery failures before they happen by verifying every email address in your list before sending. A tool like EmailListChecker.io checks for invalid syntax, non-Latin characters that older SMTP servers can't handle, and domain-level issues such as missing PTR records or unsupported email extensions. This prevents your messages from being rejected, delayed, or bounced due to UTF-8 incompatibility. By filtering out risky addresses early, you reduce bounce rates, protect sender reputation, and ensure your global campaigns stay in inbox.

Validating Syntax and Scope Upfront

When you send to an email address with non-Latin characters—like café@example.de or 用户@域名.中国—your SMTP server must support SMTPUTF8 to process it. Not all servers do, especially older or misconfigured ones. Sending to such addresses without verification leads to immediate failures or greylisting. EmailListChecker.io identifies these addresses during bulk validation, flagging potential issues before transport. This isn’t about guessing; it’s about checking the address against known SMTP standards such as RFC 6531, which defines UTF-8 SMTP extensions.

Let’s say your list includes 12,000 international subscribers. A single address with an unbalanced Unicode sequence or an unsupported TLD like .xn--90a3ac will crash the connection if your server lacks UTF-8 processing. Without pre-checks, you risk triggering a blocklist, damaging reputation, or being flagged as a non-compliant sender. With verification, you catch those flaws before the first delivery attempt.

Domain and Infrastructure-Level Checks

Even if an address has valid syntax, the domain may lack essential records. EmailListChecker.io checks for missing PTR records, DNS issues, or blacklisted domains—common hurdles for global delivery. If your mail server can't resolve the MX record or the domain has a failed SPF check, the SMTP connection will fail during authentication, regardless of UTF-8 support.

More than syntax, SMTPUTF8 depends on the entire delivery stack. A catch-all mailbox might accept the message but never deliver it. A disposable domain will discard it. A role-based address like [email protected] may be valid but useless for outbound engagement. EmailListChecker.io detects these edge cases during bulk processing. You’ll see exact reasons: "invalid domain", "catch-all detected", or "unverified TLD".

By integrating verification into your workflow—via the bulk verification tool or the real-time API—you ensure only deliverable, compatible addresses enter your pipeline. You’re not just filtering spam; you’re building a reliable delivery system. This isn't a one-off fix. It’s how global brands consistently send to international audiences without hitting SMTPUTF8 walls.

Using EmailListChecker.io to Validate SMTPUTF8-Friendly Addresses at Scale

You can upload global email lists with non-ASCII addresses—like 你好@domain.com or 🌍@example.org—and use EmailListChecker.io’s bulk verification to filter out invalid, catch-all, or role-based addresses before sending. The tool checks DNS, MX records, SMTP handshake behavior, and real-world mailbox responses to determine deliverability. This prevents SMTPUTF8 errors by identifying addresses that would fail during outbound transmission.

Check real-world deliverability across international domains

SMTPUTF8 enables internationalized email addresses, but not all servers handle them correctly. Let’s say your list includes addresses with Chinese, Cyrillic, or special characters in the local part. EmailListChecker.io doesn’t just validate syntax—it simulates the full delivery path. It probes the MX records, checks if the domain accepts non-ASCII input, and verifies whether the mailbox will actually receive the message, not just accept the address on paper.

For example, domains with outdated mail systems may reject SMTPUTF8 addresses even if they’re technically valid. EmailListChecker.io detects this behavior by analyzing real-time responses from mail servers, flagging addresses that would cause hard bounces or delivery failures during actual campaigns. This is especially important for brands with global audiences who use names like სახელი@საიტი.გე or გამოწერა@მაილი.მო.

Integrate verification into your data pipeline

If you add email addresses during onboarding, use the real-time API to validate them instantly. Every new address—regardless of language—is checked against live mail server behavior before it ever reaches your sending infrastructure. This eliminates the risk of misconfigurations that could trigger SMTPUTF8 errors across multiple messages. With the API, you can filter out problematic addresses before they hit your campaign, saving time and protecting sender reputation.

For teams using Mailchimp, Klaviyo, or HubSpot, integration options ensure consistent verification across your ecosystem. You don’t need to manually audit every list. Automate validation during sign-up or import, ensuring only deliverable, fully compliant addresses are used. The same logic applies to email list cleanup: upload your full list, and the system removes addresses likely to cause SMTPUTF8-related failures.

For a deeper look at how internationalized email is handled at scale, refer to the IETF’s specification in RFC 6531, which defines SMTPUTF8. It’s not enough to accept foreign characters; the entire delivery path—DNS, MX, and server implementation—must support them. EmailListChecker.io helps you validate that. Verify your full list to catch these edge cases early, before they cause deliverability issues in 2026.

What Each Verification Verdict Means in the Context of SMTPUTF8

Each verification result tells you more than just whether an email is valid—it reveals how well that address handles international characters, DNS setup, and delivery infrastructure. Valid means the server accepts mail and likely supports UTF-8. Invalid means it doesn’t even parse correctly. Catch-all and risky domains expose deeper deliverability risks, especially when sending globally. Use these verdicts to filter your lists before scaling transactional or marketing campaigns.

Key Verdicts and Their SMTPUTF8 Implications

  • Valid: The address passes syntax checks, the domain resolves, and the mail server accepts inbound messages. This indicates a high likelihood of SMTPUTF8 support—especially if the domain is configured with modern DNS records. Such addresses can reliably receive messages with non-ASCII characters (like é, ñ, 或, ა). Test with a real SMTPUTF8-enabled client to confirm.
  • Invalid: The email is malformed (e.g., missing @, invalid character in local part) or the domain doesn’t exist. These typically cannot handle UTF-8 at all, as the address fails to parse into a valid SMTP envelope. Including these in your list will result in early bounces and harm sender reputation.
  • Catch-all: Any email at this domain succeeds, even if it doesn’t exist. This increases the risk of sending to invalid users, especially in international domains where non-ASCII usernames are common. Catch-all domains rarely have proper SPF or DMARC enforcement, and often block or delay deliveries. Avoid for transactional or personalized sends. Run your entire list through bulk verification to flag these early.
  • Risky: The domain accepts non-ASCII domains but has inconsistent SPF records, missing DKIM, or unreliable MX setup. This may allow delivery but with high bounce or spam filtering rates. Use an inbox placement test to simulate real delivery behavior before full deployment.

Why This Matters in 2026

As global email usage grows with non-Latin scripts, SMTPUTF8 compliance is no longer optional. Domains that don’t support it will block or reject messages with international characters. According to RFC 6531, SMTPUTF8 defines how mail systems handle UTF-8 in headers and addresses. Failure to comply leads to delivery failure, especially across regions like East Asia, the Middle East, and Eastern Europe.

Use verification tools that test for actual SMTPUTF8 support, not just syntax. Tools like inbox placement tests simulate delivery through real inboxes and give you data on how your messages land—critical when sending to markets where UTF-8 is standard. Don’t assume a domain supports UTF-8 just because it uses non-Latin characters in its name. Always verify.

Integrating EmailListChecker.io with SendGrid, Mailchimp, and HubSpot

You can prevent delivery failures and maintain sender reputation by validating emails before syncing to SendGrid, Mailchimp, or HubSpot. Use EmailListChecker.io’s real-time API to filter invalid, catch-all, or UTF-8-unsafe addresses during list ingestion. This keeps your workflows intact while reducing bounces and improving inbox placement across global domains.

Pre-validate data before syncing to major platforms

When you’re preparing a list for SendGrid or Mailchimp, don’t assume your source data is clean. Even seemingly valid emails can fail due to syntax quirks or non-ASCII character issues that break SMTPUTF8 compliance—especially in 2026, where international domains with extended characters are increasingly common. Instead, run your list through EmailListChecker.io’s bulk verification or API before upload. This catches malformed addresses, role accounts (like admin@), and domains that don’t accept mail before a single message is sent.

For Mailchimp or SendGrid, integration is straightforward: send your list to the EmailListChecker.io API, which returns a verified dataset with clear verdicts—valid, invalid, catch-all, or risky. Then sync only the valid entries. This stops spam traps, disposable domains, and greylisted addresses from ever reaching your sending infrastructure. The result? Lower bounce rates and fewer inbox placement issues.

Filter lead data in HubSpot and automated pipelines

In HubSpot, bad emails enter your funnel through forms, CRM imports, or third-party sources. Let’s make sure they don’t become delivery liabilities. Use EmailListChecker.io’s API or Zapier integration to automatically validate leads as they’re captured. This adds a verification gate without slowing your process.

For example, a form submission triggers a Zapier workflow that sends the email to EmailListChecker.io. If the address fails verification, it's rejected or tagged—never added to a campaign. This prevents wasted sends and protects your sender reputation, especially when using UTF-8-unsafe characters common in non-Latin scripts.

When you apply verification at the point of entry or in your automation pipelines, you enforce quality across every touchpoint. Your deliverability improves because you’re not sending to risk-prone addresses. And because EmailListChecker.io preserves your existing workflows—no need to rebuild your CRM syncs or campaign logic—it’s easy to adopt. You gain reliability without complexity.

For full control, use EmailListChecker.io’s real-time verification API or bulk verification to process large datasets. For real-time lead validation, check out integration options including Zapier and native APIs. All integrations work with SendGrid, Mailchimp, and HubSpot, and help ensure SMTPUTF8 compliance by filtering out addresses that may trigger rejection in global mail systems.

SMTPUTF8 compliance isn’t optional for global brands in 2026. Standards like RFC 6531 define how internationalized email should be handled. Tools that check for non-conforming syntax or extended character risks—like those in EmailListChecker.io—are essential. The earlier you catch these issues, the fewer delivery failures you’ll face.

Testing Inbox Placement and Deliverability Across Global Domains

Run inbox placement tests using EmailListChecker.io’s deliverability checker across major email providers like Gmail, Yahoo, and Outlook, plus regional services such as Mail.ru and Naver. Test UTF-8 emails (e.g., नमस्ते@example.com) to ensure proper routing and delivery. Monitor bounce patterns, rejection codes, and spam folder placement to identify server or list hygiene issues early.

Verify Global Deliverability with Real-World Testing

Most SMTP servers default to ASCII encoding, but global brands must support UTF-8 to reach international audiences. Sending emails with non-Latin characters—like those in Hindi, Arabic, or Japanese—requires proper SMTPUTF8 compliance. Without it, messages may fail to route or be rejected outright. You can’t rely on simulated tests alone. Real inbox placement testing is essential to validate that your server handles international domains and encodings correctly.

Use EmailListChecker.io’s inbox placement testing to simulate deliveries to actual user inboxes across different regions. This isn’t just about checking if an email arrives—it’s about confirming it lands in the primary inbox, not the spam folder. You’ll get detailed feedback on delivery performance, including rejection codes like 550 (mailbox not found) or 552 (quota exceeded), which point to misconfigurations in your SMTP server or recipient list hygiene.

Refine Configuration and Clean Your List Based on Results

Once you’ve run tests, look for patterns: Are some regions rejecting UTF-8 emails consistently? Are there high rates of temporary bounces (4xx) on certain domains? These signals often trace back to improper server configuration, lack of DMARC enforcement, or poor list hygiene. For example, many international providers (like Outlook.com or Yahoo Mail) enforce stricter rules on sender reputation and authentication than generic email services.

Clean your list by removing invalid, disposable, or role-based addresses—especially those flagged as risky by verification tools. Bulk verification helps you filter out addresses that won’t deliver, reducing spam complaints and improving deliverability over time. Also, ensure your server sends properly authenticated messages using SPF, DKIM, and DMARC, as required by RFC 6531 for UTF-8 email support.

Finally, rerun inbox placement tests after fixing configurations and cleaning your list. Use the data to optimize your sending strategy: adjust sending volume, segment by region, and monitor reputation metrics. The goal isn’t perfection—it’s consistent delivery across real global inboxes, not just internal validation.

Why You Should Not Rely Solely on Blacklist Checks for SMTPUTF8 Readiness

Blacklist status tells you nothing about a mail server’s ability to handle UTF-8 encoded messages. A domain can be clean with zero history of abuse and still fail SMTPUTF8 delivery due to outdated server software or misconfigured protocol stacks. You need to test actual server behavior, not just reputation history.

Reputation Isn’t a Proxy for Protocol Support

Being off spam blacklists like Spamhaus or MXToolbox doesn’t mean your server supports modern email standards. Many systems remain compliant with RFC 5321 and RFC 6531 but fail under real-world UTF-8 load because of legacy software limitations. You’re not checking for compliance—you’re checking for behavior.

Let’s say you're sending messages with non-Latin characters—say, Japanese, Arabic, or Cyrillic script. If your mail server hasn’t properly implemented SMTPUTF8, it will reject the message despite being on a clean domain. This isn’t a reputation issue. It's a protocol-level incompatibility.

Verification, Not Reputation, Reveals True Readiness

Only real email verification—testing how a server responds to specific UTF-8 payloads—can identify these failures. Blacklist checks only tell you if a domain has been flagged for abuse, not whether it can parse and deliver complex text. One of the most common missteps globally is assuming that “not blacklisted” means “fully functional.” It does not.

Consider SPF, DKIM, and DMARC: these are reputation and identity tools. They don’t tell you if a server accepts Unicode in the SMTP dialog. Even if your messages pass authentication, they can still be rejected during the handshake if the server doesn’t honor SMTPUTF8. That’s why the test must happen at the transport layer.

You’re not just checking if the domain is safe. You’re checking if the email infrastructure actually speaks the new language. This is where tools like bulk email verification become essential—they test real delivery behavior across hundreds of domains, pinpointing exactly where UTF-8 compatibility breaks down.

For global campaigns in 2026, assuming a well-known domain is ready for SMTPUTF8 because it's not blacklisted is a risk. The real test is in action. Your server software may be outdated. Your provider may not have applied RFC 6531 updates. Or your third-party email service may only partially implement UTF-8. These aren’t reputation issues. They’re technical gaps.

SMTPUTF8 support isn’t optional—it’s mandatory for inclusive, reliable global communication. But it’s not proven through history. It’s proven through behavior. Only live, protocol-level validation uncovers those blind spots.

Conclusion: SMTPUTF8 Is Not Optional—It’s a Deliverability Foundation for 2026 and Beyond

SMTPUTF8 compliance is no longer an experimental feature — it’s a technical necessity for sending emails globally. Without it, messages to international domains using non-ASCII characters will fail, leading to hard bounces and lost engagement.

Ignoring SMTPUTF8 harms sender reputation, triggers automatic filtering, and restricts access to markets where local language domains dominate. The cost of delay is delivery failure, wasted resources, and reduced brand reach.

Proactively validating your email list ensures only deliverable, compliant addresses remain in your send queue. Tools like EmailListChecker.io verify UTF-8 compatibility at scale and flag risky or invalid entries before they cause issues.

Sources

Keep reading

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

Frequently asked questions

Does SMTPUTF8 support non-Latin domain names like 例子.公司?

Yes, SMTPUTF8 allows domain names with non-ASCII characters including Chinese, Cyrillic, and Arabic scripts. Your server must support it to accept such addresses.

Can I test SMTPUTF8 compliance with a simple telnet session?

Yes, use telnet to connect to your mail server and issue the EHLO command. Look for the 'SMTPUTF8' extension in the response. If absent, your server does not support it.

Do all email providers support SMTPUTF8?

Major providers like Gmail, Outlook, and Yahoo support it, but older or region-specific systems may not. This makes verification critical before sending.

How does EmailListChecker.io detect UTF-8 compatibility?

It checks syntax, domain MX records, and real SMTP behavior—testing whether a UTF-8 address can be delivered successfully, not just whether it passes parsing.

What happens if my server sends to a UTF-8 address without SMTPUTF8 support?

The server may reject the connection, the message may be dropped, or it could be silently rejected—leading to delivery failure and reputation damage.

Are there any free tools to check SMTPUTF8 support?

Some public tools like MxToolbox or Mail-Tester check basic DNS and reputation but do not simulate full SMTPUTF8 delivery. True validation requires live testing.

Does SPF or DKIM affect SMTPUTF8 compliance?

No, these are email authentication protocols. SMTPUTF8 is a transport-level feature. Both must be correctly configured for reliable delivery.

How often should I verify lists for UTF-8 compatibility?

At least monthly for active lists, and before every major send. Email lists change daily—verification ensures ongoing compliance with modern SMTP standards.

What’s the accuracy of EmailListChecker.io for detecting SMTPUTF8 issues?

Its 98.9% accuracy rate includes real-world testing across global domains, capturing syntax, delivery behavior, and protocol compatibility.

Can I use EmailListChecker.io’s API to validate UTF-8 addresses in real time?

Yes, the real-time API supports bulk and individual checks, including non-ASCII addresses, and integrates with SendGrid, Mailchimp, and HubSpot.