Why Your Chinese Domain Looks Suspicious to Gmail (And What to Do About It)

Picture this: your team has spent months preparing for a European launch. The product works, the English copy has been reviewed by three native speakers, and the prospect list has been assembled with the kind of care usually reserved for a tax audit. You set up Google Workspace, checked every deliverability checklist you could find, and watched SPF, DKIM, and DMARC turn reassuringly green in your DNS console.

Then you send the first real campaign. Within 48 hours, something feels wrong. You are not on a blacklist — you checked. The messages are not hard-bouncing either — technically, they are being delivered. Yet password-reset emails are turning up in spam, sales follow-ups are being filed under Promotions, and order confirmations arrive hours late, if they arrive at all. The email has completed its journey, but apparently took the scenic route.

You check Google Postmaster Tools. Domain reputation: Medium. Spam rate: low. Nothing is flashing red. And yet your delivery results are different from last week. This is the frustrating middle ground: the dashboards look calm while the inbox placement quietly tells another story.

This is the situation many 出海 teams eventually face, and it is the situation this post is written for. Nothing is obviously broken. Your authentication may be correct, your domain may be clean, and your messages may still be treated cautiously. Gmail is not necessarily punishing you. It simply has not gathered enough evidence to treat a new sender as familiar.

Why Gmail Treats a New Domain Differently From a US One

The first thing to understand is that Gmail does not decide trust from one magic checkbox or one permanent score. It evaluates reputation over time. A domain with little or no sending history is not treated as “bad” by definition, but it is still unknown. Until Gmail sees a consistent pattern of legitimate sending and recipient engagement, caution is the reasonable default.

Consider a US SaaS company sending from a .com domain that has quietly delivered transactional email for two years. “Unknown” is not its starting point. Gmail has already seen its traffic patterns, its recipients, and the way people engage with its messages.

A 出海 team sending from a domain registered three months ago, with no meaningful history at Western mailbox providers, starts from a very different baseline. The important point is not that Gmail automatically distrusts Chinese companies or .cn domains. It is that a new domain, unfamiliar infrastructure, sending-pattern changes, and low recipient engagement can combine into a signal that anti-abuse systems handle cautiously. Geography may be part of the surrounding context, but it is not a verdict by itself.

This is less a judgment than a practical reality: reputation does not automatically transfer across borders, providers, or infrastructure. A clean domestic sending history is not the same thing as an established relationship with Gmail recipients in Europe or North America. Your new reputation starts when you begin sending there, and it grows at the pace of recipient behavior.

The Five Things That Actually Matter

There is no shortage of deliverability advice online. Much of it is technically correct, but not especially helpful in a real launch because it explains what SPF, DKIM, and DMARC are without explaining what each one changes in Gmail’s evaluation. Let’s separate authentication from trust, because they are related but very much not the same thing.

1. SPF — the guest list, not the reputation

SPF tells the receiving server which IP addresses are allowed to send email on behalf of your domain. If a message claims to come from yourcompany.com and it wasn't sent from one of the IPs listed in your SPF record, the receiving server can mark it as suspect.

Correct SPF is table stakes, but it is not a reputation upgrade. SPF answers an authorization question: “Is this sending source allowed to use the domain?” It does not answer the trust question: “Do recipients want these messages?” A valid record helps Gmail avoid treating you as an obvious spoofing risk; it does not make a new sender familiar overnight.

A correct SPF record for a team using Google Workspace and a transactional provider looks something like this:

v=spf1 include:_spf.google.com include:YOUR_ESP_INCLUDE -all

Note: replace the include statements with those of your actual email providers. Each provider publishes its own SPF include directive in their documentation.

The final mechanism matters. -all says that sources not covered by the record are not authorized, while ~all is a softer “probably not authorized” signal. Use -all only after you have inventoried every legitimate sender; otherwise, a well-intentioned cleanup can block your own receipts, support messages, or password resets.

A common failure mode for teams operating across China and overseas is exceeding SPF’s 10-DNS-lookup limit. It is surprisingly easy when one record includes a domestic provider, a Western ESP, and a separate transactional service. Each include can trigger additional lookups, and going over the limit can cause SPF evaluation to fail. Test the complete lookup chain before sending; checking only the first line of the record is not enough.

2. DKIM — the signature, not the reputation

DKIM is a cryptographic signature added to each outgoing email. When Gmail receives your message, it looks up the public key in your DNS records and verifies that the signature matches. If it does, Gmail knows the message really came from your domain and hasn't been altered in transit.

Like SPF, DKIM is primarily about authentication and message integrity, not reputation. It helps show that the message was authorized and was not altered in transit. Those are important signals, but they do not replace a history of wanted mail, replies, and low complaints. A signed message can still be an unwanted message; cryptography has limits.

If DKIM verification is inconsistent across recipients in different regions, check DNS propagation before blaming the mail client. Some DNS providers resolve more slowly or less reliably from certain networks. If that becomes a recurring problem, a globally distributed DNS provider can be worth considering even when the rest of your infrastructure remains regional.

3. DMARC — where reputation actually starts

DMARC connects SPF and DKIM through domain alignment and tells receiving providers how to handle messages that fail that alignment. It also lets you request reports about systems sending mail on behalf of your domain. That visibility is valuable because many teams discover forgotten senders only after they start reading the reports.

DMARC has three policy levels:

• p=none — Gmail should deliver your messages even if they fail alignment. Useful as a monitoring mode, but it does nothing for reputation.
• p=quarantine — Gmail should quarantine messages that fail alignment (send them to spam). This is where reputation starts building.
• p=reject — Gmail should refuse messages that fail alignment outright. Strong, but risky if you have any hidden senders.

For most 出海 teams, the sensible path is gradual: start with p=none and a valid reporting address, review the reports for at least two weeks, and fix unexpected senders. Then consider p=quarantine. Move to p=reject only when you are confident that every legitimate sender is aligned. DMARC enforcement improves authentication hygiene; it does not, by itself, create sender reputation.

Moving directly from p=none to p=reject is a reliable way to discover that some forgotten billing system, support tool, or legacy script still sends mail. Fix the inventory first. There is no prize for breaking password resets ahead of schedule.

4. Reverse DNS — the record most people never set

Reverse DNS (rDNS, also called PTR) maps an IP address back to a hostname. Gmail's filters use rDNS as a sanity check: when a server at IP 1.2.3.4 claims to be sending from mail.yourcompany.com, does a reverse lookup of 1.2.3.4 agree?

If you send through a reputable ESP, it normally manages rDNS for the sending infrastructure. If you send from your own server, ask the hosting provider to configure a matching PTR record and ensure the forward and reverse names make sense together. Without that consistency, Gmail has one more reason to treat the server cautiously.

5. Domain age and history — the clock you can't skip, but can accelerate

This is the part nobody can optimize away completely: history matters. A domain that has sent consistent, wanted email for two years has accumulated signals that a three-month-old domain simply cannot reproduce on day one. You can build trust efficiently, but you cannot manufacture years of recipient history with a clever DNS record.

What you can control is the quality of the first few weeks. Gmail’s systems observe recipient behavior, including replies, complaints, and other engagement signals. A first batch sent to people who recognize you and expect the message is far more useful than 10,000 messages sent to a scraped list on day one. A warm-up is not a ceremony; it is the first chapter of your reputation.

That brings us to the practical part: a 30-day warm-up plan with a deliberately boring pace. Boring is good here. Your domain does not need an exciting launch; it needs a predictable one.

The 30-Day Warm-Up Checklist

This is the plan I would give a 出海 team preparing its first cold-outreach campaign. It assumes SPF, DKIM, and DMARC are already configured correctly, and that the domain has been receiving normal mail for at least a few weeks without attempting a sudden jump to bulk sending.

Days 1–3: warm sends only

Send 5–10 emails per day, only to people who know you. That can include your own team, trusted contacts at other companies, or customers who already expect to hear from you. The goal is not prospecting yet. It is to establish a small, ordinary sending pattern with recipients who are unlikely to complain.

Watch: engagement from your warm recipients. Open rate can be a useful directional signal, although it is not perfectly reliable because privacy features and mail clients can distort it. If people who know you consistently ignore the messages, check the sender name and content before assuming the DNS is at fault.

Days 4–7: expand to lukewarm

Increase to 20–50 emails per day and add people who have opted in to some form of communication: newsletter subscribers, past customers, or conference contacts who agreed to stay in touch. They may not all open, but the audience is still warmer and more relevant than a purchased or scraped list.

Watch: spam complaint rate. Gmail Postmaster Tools reports this as a key indicator. Treat anything above 0.1% as a warning, and anything above 0.3% as a reason to stop, inspect the audience and content, and diagnose before continuing.

Week 2: 100–200 per day

Keep the curve gradual. Add a small cold segment, perhaps 20% of the day’s volume, and watch how recipients respond. If complaints remain below 0.1% and engagement does not collapse, you have evidence that the audience and message are at least moving in the right direction.

Watch: bounce rate. This is where email validation earns its keep. Removing invalid and high-risk addresses before sending helps keep the list below the 2% range used as a practical safety target during warm-up. The exact result depends on list quality and provider behavior, but avoid treating validation as optional housekeeping.

Week 3: 500 per day, first real cold segment

At this point, you can begin adding cold prospects, but keep the relevance bar high. “We sell B2B software and they are a B2B company” is not a reason; it is merely a sentence containing two facts. Send only when you can explain why this recipient, at this company, might care now. During warm-up, the difference between a targeted list and a generic one compounds quickly.

Watch: Gmail Postmaster Tools regularly. If domain reputation drops from Medium to Low, pause and inspect the change before sending more. “Maybe tomorrow it will fix itself” is not a monitoring strategy, even if it is a popular one.

Week 4: scale carefully

If the first three weeks have remained stable, begin scaling in steps. Double the volume, hold it for three days, and review the signals before doubling again. If reputation dips, cut the volume by half and give the system time to recover rather than trying to “send through” the problem.

A useful rule of thumb is to avoid increasing volume by more than 2× in a single day. Sudden spikes can look anomalous, especially when combined with a new audience or a new sending infrastructure. Your volume curve should look like a ramp, not a cliff.

What to monitor continuously

• Domain reputation in Postmaster Tools — should trend upward, never downward.
• Spam rate — stay under 0.1%. This is the single number Gmail cares about most.
• Bounce rate — stay under 2%. This is where validation earns its keep.
• Open rate on your warm segments — should stay above 20%. If it drops, something has changed in your sending pattern or content.

What Does Not Work (And Why People Still Try It)

This is the section many deliverability posts skip because it is more satisfying to promise a shortcut than to explain why the shortcut fails. Unfortunately, Gmail has seen most of the shortcuts already. Being useful means saying which tactics are unlikely to help, even when they sound attractive in a sales thread.

Buying an aged domain

This is a popular tactic among 出海 teams hoping to skip warm-up: buy a domain that has existed for ten years, inherit its reputation, and start sending immediately. On paper, it sounds like buying a head start. In practice, it is closer to buying a used car without checking the engine.

In practice, it rarely delivers what people hope. Gmail’s systems look at recipient behavior and sending patterns, not just the date the domain was registered. A ten-year-old domain that changes hands and suddenly sends cold email to a completely new audience has no meaningful engagement history with those recipients. The reputation that matters is the one you build with the people you actually email, not the one printed on the domain’s birth certificate.

There is a second risk: if the previous owner generated complaints, poor engagement, or blacklist history, some of that baggage may follow the domain. Before buying an aged domain, you need to investigate its history. Often the cheaper and safer option is to build a clean reputation on a domain you actually control.

Bulk IP rotation

Another tempting idea is bulk IP rotation: if one IP gets filtered, send through many others so no single IP accumulates enough history to be classified. It sounds clever right up until the filters notice the pattern.

In practice, this can make the situation worse. A domain whose messages suddenly arrive from many unrelated IPs, without a consistent sending identity, looks like low-quality or evasive behavior. A stable, properly configured sending path is usually easier for providers to understand than a parade of fresh IP addresses.

Sending through multiple ESPs to spread the load

This one is subtler. Sending half your mail through one ESP and half through another may look like sensible risk diversification. But if both providers are not configured to authenticate and align with your domain, DMARC can expose the split. Messages from reputable providers can still look suspicious when the alignment is wrong.

Start with one ESP and configure DKIM alignment properly. Diversify only when you have a clear operational reason and have verified the authentication path for every provider.

The "just add SPF/DKIM/DMARC" fix

This is the most common advice, and also the one most likely to disappoint. SPF, DKIM, and DMARC solve authentication and alignment. They help establish that your mail is authorized; they do not prove that recipients want it. Once the records are correct, your domain is allowed to send. It is not automatically trusted to send. Those are different problems, and the second one takes time.

Where Email Validation Actually Helps

It is worth being direct here, because email validation is easy to oversell: it does not repair a damaged domain reputation. If your reputation is poor, validation will not rescue it. If your reputation is unknown, validation will not create trust out of thin air.

What validation can do during warm-up is still important:

First, it helps prevent avoidable damage. Bounces are especially unhelpful while a new sending pattern is still being evaluated. Cleaning the list before sending helps keep bounce rate below the practical 2% target and shows that you are making a reasonable effort to send to valid recipients.

Second, it helps you decide where to scale first. Confidence scoring lets you prioritize safer addresses and hold back on ambiguous ones. A 90% confidence address may be reasonable for a week-two segment; a 45% confidence catch-all address is better left out until your sending history is stronger. Validation does not create trust, but it can help you avoid spending your limited early trust on questionable addresses.

If you're curious about how this works in practice, our email validation API docs show the full response schema, including confidence scoring and per-phase timing. For the specific question of how to choose a validation API when your reputation is starting from zero, our cross-border buyer's guide covers the eight things that matter.

Frequently Asked Questions

How long does it take for Gmail to trust a new domain?

For most teams, 4 to 8 weeks of consistent, low-complaint sending is enough to move from Low to Medium in Gmail's reputation system. Moving from Medium to High takes longer — often three to six months of steady engagement. The clock starts the moment you begin sending with a correct SPF, DKIM, and DMARC setup, and it resets if you trigger a spike in complaints or bounces.

Do I need a dedicated IP to send cold email from China?

Usually no. If you are sending fewer than 100,000 emails per month, a shared IP from a reputable transactional email provider will perform better than a dedicated IP you have not warmed up. Dedicated IPs are a real advantage above that volume, but they come with a serious warm-up obligation — sending thousands of emails on day one from a fresh dedicated IP will get you filtered even faster than sending from a shared pool that already has reputation.

Can I use my Chinese company email (163, QQ Mail) to send to Gmail?

Technically yes, practically it is usually a bad idea. Gmail evaluates the sending infrastructure as well as the domain. A message routed through a QQ Mail or 163 Mail outbound server carries that provider's reputation with it, which was built for domestic consumer mail, not for cold B2B outreach. For customer-facing transactional email and any form of outreach, sending through a reputable ESP with a custom domain gives Gmail a cleaner signal to evaluate.

Does buying an aged domain really speed things up?

Rarely helps. Gmail's filters key primarily on recipient engagement — opens, replies, and low complaint rates — rather than the age of the domain alone. A ten-year-old domain that changes hands and starts sending cold email to an entirely new audience has no engagement history with those recipients, and its previous reputation is either neutral or a liability if the prior owner ever landed on a blacklist. The reputation that matters is the one you build, not the one you inherit.

Will email validation alone fix my Gmail deliverability?

No. Validation and reputation are two different problems. Validation removes bad addresses before you send, which prevents the bounce-driven reputation damage that would otherwise make things worse. It cannot create reputation where none exists. The most useful thing validation does during a warm-up period is tell you which addresses are safe enough to send to while you are still building trust — confidence scoring lets you scale more aggressively on safe addresses and hold back on risky ones.

One Last Thing

If you are a 出海 team and your first campaign has landed in spam — or you are worried it might — feel free to reach out. I read every email. After seeing this situation a few times, I can usually tell which problems are quick fixes and which ones need a few weeks of consistent behavior, no matter how enthusiastically we ask Gmail to hurry up.

Sometimes the answer is “there is a typo in your SPF record.” Sometimes it is “the domain is fine; the audience is simply too cold for week one.” Either way, it is cheaper to investigate before the campaign goes out than to rebuild reputation after it drops.

📧 info@parheliaweb.com

Andy
Founder, ParheliaWeb