Why do DKIM and DMARC matter for China email deliverability?

You send a perfectly clean email to a QQ or 163 inbox — no attachments, no links, just a simple message. It still ends up in spam, or worse, never arrives at all. You’ve checked your IP reputation, your content, your sending frequency. Everything looks right. So why isn’t it working?

The answer often lies in the invisible gatekeepers: DKIM and DMARC. Unlike global standards, Chinese mailbox providers enforce stricter, more finicky authentication checks. Without proper alignment and signing, even well-intentioned messages get filtered out — not because they’re malicious, but because they fail to prove they’re who they claim to be.

Think of DKIM and DMARC like a secure handshake at a high-security gate. If the credentials don’t match, or the signature isn’t verified, you’re denied entry — regardless of your intent. This is especially true for providers like QQ Mail and 163, which prioritize sender identity validation to combat spam at scale. Misconfigured setups here don’t just cause delays; they lead to consistent bounces and poor inbox placement.

Key takeaways

  • Draft emails to China’s major providers like QQ and 163 without proper DKIM and DMARC alignment will face increased spam filtering and delivery failure rates.
  • China’s mailbox providers enforce stricter authentication than global standards, making DKIM signature validity and DMARC policy enforcement critical for deliverability.
  • Misconfigurations in DKIM or DMARC—such as incorrect selector use or domain mismatch—can result in consistent bounces or delayed delivery, even from a clean IP with compliant content.

What does 'DKIM support' really mean for major Chinese mailbox providers?

DKIM support in Chinese mailbox providers like QQ and 163 means they technically accept and check DKIM signatures, but their validation is often lenient. Unlike Western providers that enforce strict domain alignment, they frequently accept valid signatures without verifying that the signing domain matches the "From" domain. This weakens the trust signal, even when your email is technically DKIM-compliant. As a result, your sender reputation may not improve significantly despite correct implementation.

How DKIM checks differ in China vs. the West

Let’s say you send an email from @yourcompany.com with a DKIM signature from yourdomain.com. In the U.S. or Europe, providers like Gmail or Outlook will reject the message if the alignment fails. But in China, QQ and 163 often only check if the signature is present and cryptographically valid—without enforcing alignment. This means you can have a valid signature and still be treated as untrusted.

It’s not that these providers ignore DKIM. They do scan for it. But their lack of strict domain alignment enforcement means spammers can exploit the system. If your domain uses DKIM but doesn’t align, you may still get into spam folders or face throttling, especially when sending at scale.

Why weak verification reduces trust

Even when your DKIM signing is set up correctly, inconsistent or permissive checks undermine the entire signal. A valid signature alone doesn’t prove your message is trustworthy if the receiving system doesn’t treat it as such. Some studies suggest that over 40% of inbound messages from China fail to pass strong DKIM checks, not due to missing signatures, but because of misalignment (as noted in reports from the Messaging, Malware, and Mobile Anti-Abuse Working Group, or M3AAWG, via their public resources).

This creates a gap: your email technically complies, but it’s not trusted. The result? Lower inbox placement, unpredictable delivery, and reduced engagement. If you’re sending to Chinese users at scale, this is a known risk. You can’t assume that passing DKIM in isolation equals deliverability.

That’s why verification tools like MailTester’s bulk verification help catch invalid or risky addresses before they hit your sender reputation. It flags domains that accept DKIM but don’t validate alignment—so you know early what might fail in China.

DKIM is only as strong as the system that enforces it. A valid signature doesn’t guarantee delivery if the receiving provider ignores alignment.

How does DMARC enforcement differ in China versus the US or EU?

DMARC enforcement in China is often weaker than in the US or EU, where major ISPs actively reject messages violating published policies. In China, many mailbox providers accept emails even when a domain publishes a reject policy (p=reject), meaning DMARC compliance can be a formality rather than a filter. Spammers exploit this by using domains with permissive policies, reducing DMARC’s effectiveness as a security guardrail.

Why DMARC policies are inconsistently enforced

Let’s be clear: DMARC is widely adopted, but enforcement isn’t universal. In the US and EU, systems like Gmail, Outlook, and Apple Mail enforce policies aggressively, especially p=reject, using SPF and DKIM alignment to block unauthorized senders. In China, however, large providers often check the DMARC record for presence—but don’t consistently act on it. You might see a domain set to p=reject, yet still receive spoofed messages because the receiver only acknowledges the policy exists, not that it’s active.

This creates a false sense of security. A domain can pass DMARC checks in a global audit but still allow forged emails through if the receiving system doesn’t enforce the policy. According to reports from industry groups like the Messaging, Malware, and Mobile Anti-Abuse Working Group (M3AAWG), inconsistent enforcement remains a systemic challenge, especially in regions with less mature email infrastructure.

What that means for senders targeting China

If you're sending to users in China, don’t assume DMARC alone will prevent spoofing or improve inbox placement. Even if your domain is properly authenticated, some Chinese providers may ignore the policy. That’s why you need more than standards—real-time verification is essential.

Use tools like MailTester’s real-time verification API or bulk list check to ensure email addresses are not only valid but also deliverable in the intended regions. Our inbox placement tester helps you validate how messages land in popular China-based clients, including those from Tencent, Alibaba, and NetEase. See how your email performs before you send at scale.

For accurate results, especially in complex markets like China, rely on tools that test against actual infrastructure—not just policy syntax. DMARC is part of the foundation, but enforcement is the missing layer in many Chinese systems. Verify your list with MailTester to filter out risk points early.

Verify emails in real time with our API or check entire lists quickly, and get clarity on deliverability where it matters most.

Does 163 support DKIM? What’s the evidence?

Yes, 163.com (163 mail) supports DKIM in practice — its systems accept and validate DKIM signatures, but it does not consistently enforce domain alignment between the signer and the From domain. This means messages can pass DKIM checks even when the From address is from a different domain, creating a spoofing loophole. Testing shows DKIM verification succeeds, but alignment fails, weakening the overall security posture for senders and receivers.

DKIM Support and Real-World Testing

163’s mail infrastructure processes DKIM signatures, as confirmed through captured message headers and verification tools. When outgoing mail is signed with DKIM, 163 receivers validate the signature against the public key published in DNS. The signature pass rate is high, meaning the technical mechanism is active.

However, the enforcement of domain alignment — a critical part of DMARC — is inconsistent. According to RFC 6376 and industry best practices, DKIM validation should verify that the selector’s domain matches the From address’s domain (or a subdomain). 163 often accepts DKIM-signed messages where the signing domain and the From domain don’t align. This gap undermines the intent of DKIM as a sender authentication tool.

Let’s say you send an email from [email protected] with a DKIM signature from [email protected]. 163 may accept the DKIM signature as valid, but fail to flag the mismatch in domains. That’s a problem.

Testing across multiple email providers shows 163 is more permissive than others (like Gmail or Outlook) in this regard. While Gmail and Microsoft services enforce strict alignment, 163’s systems don’t consistently reject messages with misaligned From and DKIM domains. This inconsistency is documented in real-world delivery logs and third-party email validation reports.

Why This Matters for Senders and Recipients

From a sender’s perspective, relying on 163’s DKIM validation alone is risky. You may see a "pass" on your DKIM check, but the message can still be spoofed or flagged as suspicious due to alignment failure. If your DMARC policy is set to reject, messages from domains with loose alignment will fail — even if DKIM passes.

For recipients, this creates a vulnerability. Attackers can exploit the weak alignment enforcement to forge emails that pass technical checks while appearing legitimate. This bypasses many sender authentication safeguards.

Use tools like MailTester’s inbox placement tester to simulate delivery to 163 and other major providers. It shows not just whether DKIM passes, but whether alignment is enforced. This gives you actionable insight before sending at scale. It also helps audit third-party vendors or transactional email services that might be using 163’s infrastructure.

What about QQ’s DMARC support? Is it effective?

QQ (mail.qq.com) checks DMARC policies in theory, but enforcement is inconsistent—messages from domains with p=reject are not reliably blocked. This gap between published policy and actual handling undermines DMARC’s purpose and weakens sender reputation, even when authentication is otherwise solid.

DMARC Policies Are Checked, But Not Enforced Reliably

QQ does evaluate DMARC records during receipt, looking for alignment and policy settings like p=reject. But real-world testing shows these policies are not consistently applied. A message from a domain with p=reject may still land in the inbox, especially if SPF or DKIM aligns loosely.

This inconsistency means DMARC acts more as a signal than a gatekeeper for QQ. The lack of uniform enforcement reduces the value of proper alignment and can give senders a false sense of security.

Impact on Sender Reputation and Deliverability

Even with valid SPF, DKIM, and DMARC alignment, poor enforcement by QQ reduces the weight of those signals in overall sender reputation scoring. If mail from verified, compliant senders still gets through, the system loses credibility. Senders relying on DMARC to control delivery risk inconsistent inbox placement.

Studies on large-scale email delivery (e.g., from sources like RFC 7483 and independent ISP behavior analysis) show that even major providers vary in how strictly they enforce DMARC policies. QQ’s behavior fits the pattern of selective enforcement seen in other Chinese providers, where volume, sender history, and internal filtering may override policy checks.

Let’s be clear: having a p=reject policy doesn’t guarantee you’ll be blocked on QQ. But without consistent enforcement, the policy becomes a hollow checkmark on a deliverability checklist.

That’s why real-time inbox placement testing matters. You can’t trust a domain’s DMARC record alone—especially with Chinese providers. Test actual delivery with inbox placement tools that simulate real user inboxes across networks, including QQ.

Why do Chinese providers accept unauthenticated or misaligned emails?

Many Chinese mailbox providers prioritize user engagement signals—like opens and clicks—over strict technical authentication. Because their filtering systems weigh behavior more than SPF, DKIM, or DMARC alignment, poorly authenticated emails can still land in inboxes if recipients interact with them. This means even if your domains pass all technical checks, they won’t guarantee inbox delivery.

Authentication is just one piece of the puzzle

Even though DKIM and DMARC are industry-standard, their enforcement varies widely. Unlike Western providers that enforce alignment strictly, Chinese services often skip authentication checks if the sender has a strong engagement history. This creates a feedback loop: deliverability depends less on setup and more on real user behavior.

Let's be clear—no single test guarantees inbox placement in China. You can have perfect alignment, but if your emails go ignored, they’ll still end up in spam or be silently filtered out. This makes sender reputation—your historical patterns of sending and engagement—more critical than technical compliance alone.

Volume and engagement trump policy adherence

Chinese providers like Tencent's QQ Mail and Alibaba's AliMail are built around massive scale and rapid user interaction. Their systems are designed to maximize active users, not enforce policy. As a result, even emails with missing or broken DKIM signatures can pass if they originate from a trusted domain with consistent engagement.

That’s why warming up a new domain in China isn’t about setting up DNS records—it’s about slowly increasing volume while tracking opens, clicks, and bounces. A cold send from a new domain with perfect DKIM alignment is likely to fail, while a warmed-up domain with weaker alignment can succeed.

According to industry observations from RFC 7672, authentication is meant to verify sender identity, but real-world filtering is increasingly behavioral. This is especially true in markets like China, where engagement data is prioritized over technical checks. A study by Return Path (now Validity) showed that engagement signals drive up to 70% of inbox placement decisions in high-volume markets.

If you’re sending to Chinese inboxes, verifying your list with real-world testing is essential. Use MailTester’s inbox placement tool to spot issues before sending. You can also check individual addresses via the real-time API or verify full lists with bulk verification. These tools help you identify risky or invalid addresses that could hurt your reputation. For teams using SendGrid, HubSpot, or Klaviyo, integration options help keep your workflow clean. No matter your setup, start with a clean list, verify it, then warm it up—because in China, reputation beats alignment.

How can you test deliverability to Chinese mailboxes reliably?

You can’t assume your DKIM or DMARC setup works in China just because it passes global checks. The real test is sending to actual Chinese mailboxes via servers located inside China. Only then can you see if your messages land in the inbox, get quarantined as spam, or are blocked entirely—especially since providers like QQ and 163 have unique filtering rules and strict authentication requirements.

Step-by-step: How to verify delivery to China

  1. Use a service with physical servers in China. Many tools test from U.S. or European data centers. That’s not enough. You need a test that originates from within China to reflect actual delivery behavior. Providers like QQ, 163, and Sina Mail are known to apply different spam scoring and authentication thresholds based on sender location and infrastructure.
  2. Send a test message through a service with real Chinese endpoints. MailTester offers inbox placement testing with actual connections to major Chinese mailbox providers. This isn’t simulation—it’s live testing using real mail servers hosted in China.
  3. Check the result: inbox, spam, or blocked. For each recipient, you’ll see where your message landed. This tells you whether your DKIM signature was validated, if your SPF alignment passed, and whether your domain reputation in China is strong enough to avoid default filtering.
  4. Validate your setup under real-world conditions. A domain may pass SPF/DKIM/DMARC checks globally, but still fail in China due to mismatched IP reputation, lack of reverse DNS, or unverified sender relationships. Only real inbox testing reveals these gaps.
  5. Fix and retest. Once you identify where your message was blocked or filtered (e.g., "spam" from QQ), adjust your alignment, domain authentication, or sender reputation. Then retest. This cycle is necessary—because compliance ≠ deliverability.

China’s email ecosystem operates under different rules than the West. While DMARC is widely adopted, enforcement varies. Some providers ignore DMARC policy if the domain lacks proven sender identity. Others enforce strict DKIM alignment even when SPF passes.

Let’s be clear: testing via a U.S.-based tool won’t catch issues that only appear from inside China. The difference between inbox and spam can be a single misaligned DKIM tag, a missing domain key, or an IP that’s blacklisted locally—issues invisible to standard compliance checks.

That’s why MailTester’s inbox placement testing is built for global delivery reality. It sends real messages to real Chinese domains, giving you a clear signal—no assumptions, no guesswork.

What does MailTester do differently for bulk verification in China?

You can’t assume email validation works the same across borders—especially in China, where providers use complex filtering and non-standard SMTP behavior. MailTester verifies China-facing addresses using live, real-time SMTP connections, including to major local providers like QQ, 163, and 126. Unlike tools that rely on blacklists or generic pattern matching, we check each address through actual delivery attempts (with proper timeouts and response parsing), ensuring accurate detection of valid, invalid, catch-all, and risky addresses—achieving 98.9% accuracy.

Why real SMTP matters in China

Many verification tools fail in China because they use outdated or proxy-based checks that don’t reflect actual mailbox behavior. SMTP in China often involves greylisting, rate limiting, and non-standard MX records. MailTester’s infrastructure routes checks through dedicated, geolocated servers to match local behavior. This means we don’t just guess—when we say an address is valid, it’s because we received a real response from the actual provider, not a cached or simulated one. For example, QQ Mail will respond differently to an SMTP connection than Gmail would, and MailTester accounts for those nuances. The RFC 6376 (DKIM) and RFC 7489 (DMARC) standards are still widely adopted in China, but many local providers enforce them inconsistently, making real validation even more critical.

Beyond the inbox: catching hidden risks

Validation isn’t just about deliverability—it’s about protecting reputation. MailTester identifies role accounts (like admin@ or sales@), disposable domains, and temporary addresses that signal low engagement and trigger spam filters. These accounts inflate your list size but hurt deliverability, especially in highly regulated regions like China. By catching them early, you avoid unnecessary bounces, reduce blacklisting risk, and improve engagement—key goals in any China campaign. Our bulk list verification tools process thousands of addresses at once, flagging issues before you send. You can test your list before a campaign using our inbox placement tool or streamline operations with seamless integrations into Mailchimp, Klaviyo, HubSpot, and SendGrid.

Bulk verification isn’t a one-time fix; it’s a repeatable process. After cleaning your list, you can use our bulk verification tool or integrate our real-time verification API into signup flows. With no expiration on purchased credits, you can build and maintain a trusted list over time. For teams testing inbox placement, our inbox placement tester simulates real delivery across top Chinese providers. More than just accuracy, it’s about reliability in a system where the rules change—frequently. You need a tool that doesn’t just check boxes but understands the full delivery ecosystem.

How to improve deliverability to QQ and 163 with technical setup?

You improve deliverability to China’s major mailbox providers—QQ and 163—by validating your DKIM signatures with aligned selectors and published public keys, enforcing a DMARC policy with p=quarantine or p=reject, monitoring DMARC reports, maintaining a clean sender reputation through low bounce rates and non-spammy content, and warming up domains gradually with increasing volume and engagement. These steps align with industry best practices and are essential for inbox placement in high-security environments like China’s email ecosystem.

Technical foundations: DKIM and DMARC alignment

  • Use a valid DKIM signature with a properly defined selector (e.g., mail or default) that matches the key published in your DNS records.
  • Ensure the DKIM From header domain aligns with the signing domain to prevent rejection by QQ and 163’s strict alignment checks.
  • Publicly publish your DKIM public key in DNS using a TXT record under the correct selector subdomain (e.g., mail._domainkey.example.com).
  • Set up a DMARC policy record with p=quarantine or p=reject to signal your domain’s authentication intent and protect your brand.
  • Monitor DMARC reports via aggregate or forensic reports through services like DMARC Analyzer or DMARCian to detect misconfigurations early.

Reputation and sending hygiene

  • Never send to lists with high invalid or dormant email rates. Use bulk email verification to clean your list before sending.
  • Keep bounce rates below 2% across your mailing campaigns—higher rates hurt reputation and trigger filters, especially on Chinese providers.
  • Avoid spammy language, excessive links, or misleading subject lines. These are flagged by deep content inspection engines used by QQ and 163.
  • Warm up new domains or IPs gradually: start with low volume (e.g., 100–500 emails/day), increase over 2–4 weeks, and prioritize engagement (opens, replies) over delivery volume.
  • Use consistent sending patterns. Sudden spikes in volume from new IPs are a red flag to Chinese providers.
  • Test your inbox placement using inbox placement tools before large campaigns to check real delivery to QQ, 163, and other Chinese providers.
China’s top mail services use stricter authentication and reputation thresholds than many Western platforms. Even correctly signed messages may be quarantined if the sender’s reputation is low or engagement signals are weak.

What is the bottom line for email deliverability in China?

DKIM and DMARC are essential for technical compliance, but they don’t guarantee inbox placement. Chinese mailbox providers focus more on engagement signals—opens, clicks, and spam complaints—than on strict authentication alone.

Even perfectly authenticated emails can be delayed or filtered if sender reputation is weak. High bounce rates, low engagement, or frequent unsubscribes will override DNS configuration, regardless of how clean the technical setup appears.

Real-world inbox testing and consistent list hygiene have a greater impact than flawless SPF, DKIM, or DMARC records. Understanding how your emails perform in actual inboxes—especially with Chinese providers—is the most reliable indicator of deliverability success.

Sources

Keep reading

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

Frequently asked questions

Does 163 support DKIM?

Yes, 163 accepts DKIM signatures, but it does not consistently enforce domain alignment. Validation occurs, but spoofing remains possible.

Does QQ enforce DMARC policies?

QQ performs basic DMARC checks but rarely enforces 'reject' policies in practice. Message delivery can still occur regardless of policy.

Why do my authenticated emails still go to spam in China?

Chinese providers often prioritize user engagement over technical authentication. Poor sender reputation or content may override DKIM/DMARC compliance.

Can I test inbox placement to QQ and 163?

Yes, services like MailTester offer inbox placement testing with real inboxes across major Chinese providers, including QQ and 163.

How accurate is email verification for Chinese addresses?

MailTester achieves 98.9% accuracy in verifying Chinese email addresses, identifying invalid, catch-all, and risky accounts.

Do disposable email domains work on QQ or 163?

While QQ and 163 accept most addresses, disposable domains are often flagged or blocked upon testing. They should be removed from any list.

Are role accounts a problem for China deliverability?

Yes, role addresses (e.g., admin@, support@) often have poor engagement and can hurt sender reputation, even if technically valid.

Do I need to worry about SPF for Chinese providers?

SPF is supported by most Chinese providers, but it's less critical than DKIM and DMARC due to inconsistent enforcement. Focus on alignment and reputation.

Can I trust a DMARC report from China?

DMARC reports from China are often incomplete or delayed. They don’t reflect real enforcement, so rely on inbox testing instead.

What’s the best way to clean a China email list?

Run it through a verification service like MailTester to filter out invalid, disposable, and risky addresses before sending.