Why does Gmail 4.7.28 block new domains?

You just set up a new domain for your email campaigns. You send your first batch of mail. And Gmail replies with a 4.7.28 error. Not “bounced,” not blocked permanently — but delayed. You’re not alone. This error shows up regularly when new domains try to send mail through Gmail’s systems, especially during the first month.

Gmail 4.7.28 isn’t a rejection — it’s a gate. New domains don’t yet have sender reputation. They lack history. Spammers often use fresh domains to avoid detection, so Gmail applies extra scrutiny. The system uses reputation signals, authentication, and behavioral heuristics to delay or filter mail from domains that haven’t proven themselves.

Key takeaways

  • Gmail 4.7.28 is a temporary, reputation-based delay — not a permanent block — applied to new domains during their first 30 days.
  • The error often results from missing or incorrect email authentication (SPF, DKIM, DMARC), low sender reputation, or sending patterns that resemble spam.
  • Proper setup of authentication records and sending habits over time can resolve the block and improve inbox placement.

What does Gmail 4.7.28 on new domain mean?

Gmail 4.7.28 on new domain means your message was blocked from delivery due to Gmail’s rate-limiting or inspection rules. It signals that Gmail recognized your domain but treated it as new and lacking trust, typically because of low sending history, recent DNS changes, or poor sender reputation. This error can affect a single email or all emails sent from that domain within a short time window.

How Gmail’s systems evaluate new domains

Gmail uses a combination of technical checks and behavioral signals to assess new domains. When you send from a domain that has no prior sending history, Gmail applies stricter scrutiny—especially if you're sending at scale. The 4.7.28 error often appears when a new domain exceeds message volume thresholds too quickly or lacks a proper sender reputation profile.

Rate-limiting isn't just about volume—it's also about consistency. Sending a high number of emails in a short burst (e.g., 1,000+ in an hour) from a freshly set-up domain triggers defensive measures. The same applies to domains with weak or inconsistent SPF/DKIM alignment, or those using temporary or disposable IPs.

For context, the RFC 6409 defines how bounce notifications like DSNs (Delivery Status Notifications) should be structured. Gmail’s 4.7.28 is a standard DSN code indicating a policy-based rejection. It's not a technical failure, but a deliberate decision based on trust signals—something systems like Spamhaus and MXToolbox track through reputation databases.

How to recover from 4.7.28 on new domain

Recovery starts with confirming your domain isn’t flagged by any blocklist. Use tools like MXToolbox to check DNS records and reputation. Then, verify your email sending setup: ensure SPF, DKIM, and DMARC are correctly published, and avoid using catch-all or role accounts in your campaigns.

Start slow. Send a small volume of emails (50–100 per hour) and monitor feedback loops and bounces. Consistent, low-volume sending builds trust over time. If you're sending bulk emails, use a service like MailTester to clean and verify your list before sending.

For real-time checks, run inbox placement tests with MailTester’s inbox tester—it simulates real delivery conditions across Gmail, Yahoo, and Outlook. If you’re doing repeated sends, integrate the MailTester API to validate addresses before they hit your SMTP server.

Trust is earned by consistency, not declared by configuration.

Gmail 4.7.28 isn’t a permanent barrier. It’s a signal to slow down, verify, and rebuild.

How does Gmail rate new domains?

Gmail evaluates new domains through a mix of technical setup, sending volume, recipient engagement, and feedback loops. A domain with properly configured DNS, valid SPF/DKIM/DMARC records, and consistent low bounce rates signals legitimacy and passes Gmail’s initial checks much faster. Sending large volumes too quickly or to low-quality lists commonly triggers Gmail’s 4.7.28 rate threshold, especially without verified engagement signals.

Technical setup is the foundation

Your domain’s technical health determines whether Gmail even considers it trustworthy. Valid MX, SPF, DKIM, and DMARC records aren’t optional—they’re baseline requirements. Without them, Gmail treats your messages as suspicious by default. You can test this in real time using MailTester’s bulk verification or API, which checks these records and flags issues before you send.

Volume and behavior matter just as much

Gmail doesn’t just look at setup—it watches how you send. A new domain sending 10,000 emails in a day to a list with no prior engagement will likely be throttled or filtered, regardless of perfect DNS. This is where the 4.7.28 threshold comes in: it’s not a fixed rule but a signal based on behavior. Gmail uses historical feedback—including bounces, spam complaints, and inbox engagement—to adjust delivery over time.

Sending slowly, warming up your domain with real users who opt in, and ensuring high engagement reduces risk. Tools like inbox placement testing help you see how Gmail and other providers treat your messages before sending to live lists.

There’s no shortcut here. Even with flawless technical records, a domain that sends to unengaged users or uses a poor-quality list will be flagged. Think of it as a probation period: Gmail gives new domains a chance—but only if you behave like a trusted sender.

For teams managing high-volume sends, real-time verification via the MailTester API can catch invalid, disposable, or high-risk addresses before they harm your reputation. It’s not about hiding bad data—it’s about building a sender reputation that can withstand Gmail’s scrutiny.

Learn more about how domain reputation works in practice at RFC 6376 (DKIM) and RFC 7208 (SPF), which define the technical standards Gmail follows.

What’s the real fix for Gmail 4.7.28 on new domains?

Gmail’s 4.7.28 system doesn’t respond to quick fixes. The real fix starts with a clean, verified email list, proper domain authentication, a gradual warm-up over 14–21 days, and inbox placement testing to confirm Gmail is accepting messages. Skipping any step increases risk of rejection or spam filtering.

Simplify the foundation

  • Start with a verified list—use tools like MailTester’s bulk verification to filter out invalid, role-based, and disposable email addresses. Over 10% of new domain sends bounce due to poor list hygiene.
  • Check your SPF, DKIM, and DMARC records using MxToolbox or RFC 7208. A single misconfiguration can trigger Gmail’s anti-spoofing filters even with valid content.
  • Ensure your domain isn’t on any blocklists. Check reputations via Spamhaus or abuse.net—especially if you’re using a shared IP or hosting provider.

Build trust through consistency

  • Warm your domain slowly—start with 50–100 emails per day, focused on engagement (open, clicks), not volume. Gradually increase over 14–21 days to avoid triggering automated abuse detection.
  • Use inbox placement testing before scaling. MailTester’s inbox tester simulates real Gmail inboxes and returns placement results in minutes, showing whether your mail lands in inbox, spam, or is blocked entirely.
  • Monitor for anomalies. If you see sudden spikes in bounces or spam complaints, pause and audit—Gmail’s systems update continuously, and new domains are scrutinized more closely.

There’s no magic bypass. The fix isn’t a setting, a code change, or a third-party bypass. It’s consistency in setup, hygiene, and behavior. Gmail 4.7.28 prioritizes sender reputation and engagement signals. If your domain behaves reliably, Gmail will follow.

How does email list hygiene prevent 4.7.28 errors?

Bad email addresses — invalid, role-based, or from disposable domains — trigger high bounce rates and feedback loops. Gmail flags these patterns as abuse signals, even if your message is harmless. Cleaning your list with a tool like MailTester reduces reputation risk and stops 4.7.28 errors before they start.

Invalid and disposable addresses hurt your sender reputation

Every bounce, especially from invalid or temporary emails, counts against your sender reputation. Gmail tracks these metrics closely. If your domain sends to a list with a 25% bounce rate, even with good content, Gmail will flag your sending behavior as suspicious.

Role accounts (like admin@ or sales@) often don’t open messages, create feedback loops, and add no real value. Sending to them artificially inflates your bounce rate and lowers deliverability. Disposable email domains (like mailinator.com) are used for testing and phishing — Gmail treats them as high-risk.

Let’s be clear: a clean list doesn’t just improve inbox placement. It keeps your domain out of spam filters and avoids the 4.7.28 error that signals a sending policy violation.

Prevention starts with real-time verification

You don’t have to wait to get rejected. Tools like MailTester catch problems before they hit Gmail’s systems. The verification API checks individual emails in real time, while bulk verification cleans entire lists in seconds.

Using MailTester’s inbox placement test shows you exactly how your message lands in real inboxes — not just a spam score. This gives you confidence your emails are trusted, not blocked. It’s not about chasing perfection. It’s about reducing abuse signals through good hygiene.

Even if you’re sending permission-based emails, a contaminated list can trigger automated blocks. That’s why hygiene matters — it’s not just about removing bad addresses. It’s about proving you’re not a spammer to Gmail’s systems.

For teams using Mailchimp, HubSpot, or SendGrid, MailTester integrates directly. You can clean lists before campaigns launch and avoid expensive or blocked sends. No credits ever expire — you can use them whenever you need to.

For a full breakdown of email verification standards, see the SMTP RFC 5321 and RFC 6591 on feedback loops. These define how receivers evaluate sender behavior.

Clean your list with MailTester’s bulk verification and stop Gmail 4.7.28 errors in their tracks — before they even start.

Use MailTester to prevent new domain delivery issues

You can avoid Gmail 4.7.28 deliverability issues on a new domain by verifying every email address before sending. Catch invalid, role-based, and disposable emails early. Identify catch-all domains that appear valid but don’t deliver. Test inbox placement with real Gmail accounts before launching campaigns. Use MailTester’s API or bulk verification to clean and validate lists at scale.

Before you send, verify what’s in your list

  • Run your entire email list through MailTester’s bulk verification to flag invalid addresses and reject bounce-prone ones before they hit the wire.
  • Use the real-time API to verify every address as it’s collected—stop role accounts like admin@, sales@, or support@ from entering your system.
  • Check for disposable domains (like @mailinator.com) that often get flagged or blocked by Gmail’s filters—even if they’re technically valid.
  • Spot catch-all domains: some domains accept all incoming emails, but not all recipients actually see them. MailTester identifies these to prevent false positives.

Test deliverability before you scale

  • Use MailTester’s inbox placement tool to send test emails to real Gmail accounts—no fake inboxes, no simulators. Confirm your content reaches the inbox without triggering filters.
  • Test different subject lines, sender names, and content formatting with real-world Gmail setups to see how your message is received.
  • Integrate MailTester with your CRM or ESP (Mailchimp, HubSpot, Klaviyo, SendGrid) via our integrations page to automate clean-up and validation across workflows.
  • Start with 100 free verifications at MailTester’s pricing page—credits never expire, so you can plan ahead without rush.

Deliverability on a new domain hinges on sender reputation, and reputation starts with list quality. A single bad address can hurt your standing with Gmail, especially under strict filters like 4.7.28. By verifying every email and testing delivery in real conditions, you reduce bounces, avoid blocklists, and improve inbox placement. This isn’t guesswork—Gmail evaluates sender behavior based on consistent, clean engagement.

“A high volume of invalid addresses can lead to temporary or permanent sender blocklists. Maintaining sender reputation begins with list hygiene.” — DMARC.org

Gmail 4.7.28: A signal, not a death knell

Gmail’s 4.7.28 error isn’t a permanent ban—it’s a warning that your domain is under evaluation. It means Gmail is scrutinizing your sending behavior, not rejecting you outright. If you fix authentication, clean your list, and warm up properly, over 90% of domains are fully accepted within 30 days.

What 4.7.28 Really Means

Let’s be clear: this isn’t a block. It’s a signal. Gmail uses 4.7.28 to flag domains that show signs of poor reputation or suspicious activity. It often follows spikes in hard bounces, spam complaints, or missing SPF/DKIM records. The message isn’t “you’re blacklisted”—it’s “we’re watching.”

Think of it like a traffic signal: red doesn’t mean you’re banned from the road. It means you need to stop, check your route, and proceed carefully. The same applies here. Fixing the root issue—poor list hygiene, broken authentication, or sudden volume spikes—typically resolves it.

Why Most Fail (And How to Avoid It)

The real problem isn’t the 4.7.28 error. It’s sending to misconfigured domains or low-quality lists. If your domain isn’t authenticated properly (SPF, DKIM, DMARC), Gmail will treat every message as suspect. A single misconfigured record can trigger evaluation.

Even if you’re technically correct, poor sender reputation—high bounce rates, unengaged recipients, or rapid volume growth—can trigger this. For example, sending 10,000 emails on a new domain in one day with no prior warming up is a common red flag. Gmail’s algorithms notice.

Fixing it isn’t magic. It’s process. Verify your sending list with tools like MailTester’s bulk verification to catch invalid, disposable, or role-based addresses before they hurt your reputation. Use MailTester’s API to validate in real time and reduce bounce rates at scale.

Once you clean your list, ensure all records are correct. Test them using MXToolbox or RFC 7628, which defines modern email authentication standards. Then, warm up your domain gradually—start with small batches, increase volume over days, and track engagement.

Over 90% of domains that follow these steps are fully accepted by Gmail within a month. The error doesn’t mean you’re dead. It means you’ve got a roadmap. Ignore it, and you’ll stay in the red. Fix the fundamentals, and you’re back in the game.

Why SPF, DKIM, and DMARC matter for new domains

Without properly configured SPF, DKIM, and DMARC, Gmail treats your new domain as high-risk—even if your content is legitimate. This triggers technical rate limits like 4.7.28, reducing inbox placement and causing bounces. These three protocols together establish trust, proving you’re authorized, your messages are unaltered, and Gmail knows how to handle failures.

SPF: Only authorized servers send from your domain

SPF (Sender Policy Framework) is a DNS record that lists which mail servers are allowed to send emails on your domain’s behalf. If Gmail receives an email claiming to be from your domain but the sending server isn’t in the SPF list, it sees that as a red flag. This is especially critical for new domains, which lack sender reputation. Without SPF, Gmail sees your domain as a potential source of spam.

DKIM: Proves messages weren’t tampered with

DKIM (DomainKeys Identified Mail) adds a digital signature to each outgoing email. When Gmail receives the message, it checks the signature against your public key in DNS. If the signature doesn’t match, the message has been altered in transit—either accidentally or maliciously. This isn’t just about content integrity; it’s a trust signal. Gmail prioritizes domains that consistently send DKIM-signed emails.

DMARC: Tells Gmail what to do when things fail

DMARC (Domain-based Message Authentication Reporting & Conformance) sits on top of SPF and DKIM. It tells Gmail whether to reject, quarantine, or monitor emails that fail authentication. If you have DMARC set to "p=none", Gmail takes no action—even if SPF or DKIM fail. That means spammers can abuse your domain with impunity. Setting a policy like "p=reject" is essential for new domains to build trust. As the RFC 7483 standard states, DMARC is the enforcement layer that makes SPF and DKIM effective.

When all three are set correctly, Gmail treats your domain as low-risk, removing the 4.7.28 rate limit. This isn't just technical—it’s about reputation. New domains start with zero signal, so the protocols become your first proof of legitimacy. You can verify your setup using tools like MailTester’s inbox placement tester or test your domain health before sending bulk campaigns. For ongoing validation across large email lists, use the bulk verification feature or integrate with your platform via the real-time API. Even small misconfigurations can trigger automated defenses—so get it right the first time.

Domain warm-up: The quiet fix for Gmail 4.7.28

You can resolve Gmail 4.7.28's skepticism by gradually warming up your new domain with low-volume, high-engagement sends. Start with 50–100 emails daily to known, active users. Increase volume only after consistent open and engagement rates. Avoid blasting unengaged addresses during the first 14 days. This builds sender reputation quietly, without triggering spam filters.

How to warm up your domain properly

  • Begin with 50–100 emails per day to recipients who have already interacted with your brand (e.g., past customers, website signups).
  • Send only to engaged users—those who’ve opened or clicked your messages before. Gmail treats unengaged sends as spam signals.
  • Increase volume by 10–20% per day only after three consecutive days of strong open and engagement rates. No spikes.
  • Avoid sending to new, unverified, or unengaged email addresses for at least the first 14 days. This includes cold leads or scraped lists.
  • Use a tool like MailTester to verify your list and isolate high-quality, engaged addresses before warming up. Not every address on your list is ready to be sent to.
  • Monitor hard bounces and spam complaints. Any spike in either kills warm-up progress.

Why this works

Gmail uses a range of signals to assess sender credibility. New domains start with a zero reputation. Without engagement data, Gmail defaults to caution—often marking sends as spam or rejecting them silently. Warm-up gives Gmail a clear record of consistent, meaningful delivery.

This process aligns with industry standards. The Spamhaus Project notes that sender reputation is heavily influenced by user engagement over time, not just volume. Similarly, RFC 5321 details how SMTP servers evaluate sender behavior during initial connection. A slow, steady build-up satisfies both technical and behavioral thresholds.

Let’s be clear: you can’t rush this. Trying to send 10,000 emails on day one will trigger rate limits and spam filtering. The 4.7.28 algorithm detects sudden volume spikes—even if the content is clean. Warm-up isn’t optional. It’s the foundation of inbox placement.

Use MailTester’s bulk verification to remove invalid, catch-all, or disposable addresses. Filter out inactive users. Run an inbox placement check after 7–10 days to test how Gmail is treating your messages. If the test shows high deliverability, you’re on track.

Only scale after you’ve proven consistent engagement. Your domain reputation isn’t built in a day. It’s built in 28 days of smart, focused sends.

How MailTester helps you avoid new domain issues

You can prevent Gmail 4.7.28 errors and other new domain deliverability problems by verifying email addresses before sending. MailTester identifies invalid, catch-all, and risky addresses with 98.9% accuracy, so you don’t waste sends on addresses that will bounce or trigger spam filters. It integrates directly with Mailchimp, HubSpot, Klaviyo, and SendGrid to clean your list before every campaign, reducing bounce rates and protecting sender reputation.

How it works in practice

  • Use the bulk verification tool to scan your entire list and flag invalid or risky addresses—no more sending to known bounces or disposable domains.
  • Check real inbox placement with the inbox tester to see how your emails land across Gmail, Outlook, and other providers, including newer versions like 4.7.28.
  • Integrate MailTester with your ESP via pre-built connectors for automatic list cleaning—no delays, no manual work.
  • Use the real-time API to verify addresses at signup, during onboarding, or in batch—ideal for high-volume workflows.
  • MailTester detects catch-all domains, where every address appears valid, which otherwise lead to misleading success rates and poor deliverability for new domains.

Why accuracy matters on new domains

New domains often face stricter scrutiny from providers like Gmail. A single misconfigured SPF record or a high ratio of invalid addresses can trigger throttling or outright rejection. According to RFC 5321, SMTP servers validate recipient addresses before accepting mail—failure early in the handshake (like with a 4.7.28 error) means your message dies before delivery.

MailTester’s 98.9% accuracy rate helps catch issues before they affect your reputation. It’s not a magic fix, but it removes the noise. You’re not just avoiding bounces—you’re preventing your domain from being flagged due to inconsistent or malformed delivery patterns.

Validating addresses before sending is an industry-standard practice for maintaining sender reputation and inbox placement, especially for new domains with no established track record.

Conclusion: 4.7.28 isn’t a bug — it’s a gateway to trust

Gmail’s 4.7.28 behavior on new domains isn’t a bug—it’s a deliberate gatekeeping mechanism. It ensures only senders with verified legitimacy gain access to inboxes, reducing spam for users.

Fixing it isn’t just about sending headers or adjusting SPF records. Success requires clean email lists, valid authentication (SPF, DKIM, DMARC), and sending volume that grows gradually over time.

Detecting invalid or risky addresses before sending prevents deliverability issues. Inbox placement testing and email verification help confirm your domain is accepted without penalty, even during early setup.

Sources

Keep reading

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

Frequently asked questions

What causes Gmail 4.7.28 on new domains?

It’s triggered when Gmail detects a new domain with poor sending history, weak authentication, or high bounce rates. The error indicates temporary rate limiting.

Can I fix Gmail 4.7.28 without changing my domain?

Yes — fixing DNS settings, cleaning your list, and warming up your domain gradually will resolve the issue without domain changes.

How long does Gmail 4.7.28 last?

It typically lasts up to 30 days, depending on sending practices and reputation build-up. Most domains regain full access within two weeks with proper hygiene.

Does sending to role addresses cause 4.7.28?

Yes — role addresses (e.g. admin@, sales@) are often used in spam campaigns. Sending to them increases risk and can trigger Gmail’s rate limits.

Why does Gmail block new domains at all?

New domains are frequently used by spammers. Gmail applies temporary restrictions to verify legitimacy before granting full inbox access.

Can disposable emails trigger 4.7.28?

Yes — disposable domains are commonly associated with spam. Sending to them harms your reputation and increases the risk of rate limiting.

How do I test if my domain works with Gmail?

Use inbox placement testing with real Gmail accounts. Tools like MailTester can simulate delivery and confirm whether Gmail accepts your messages.

Is 98.9% email verification accuracy reliable?

Yes — MailTester achieves 98.9% accuracy by combining real-time SMTP checks, pattern recognition, and database intelligence. It reduces bounce and blocklist risks.

Can I verify emails in bulk with MailTester?

Yes — MailTester supports bulk list verification through its API and dashboard. You can verify thousands of addresses at once.

Do MailTester credits expire?

No — purchased credits never expire. You can use them anytime, even months or years later.

What’s the best way to warm up a new email domain?

Start with low-volume sends to engaged recipients. Gradually increase volume over 14–21 days while maintaining high engagement and low complaint rates.

Does MailTester integrate with SendGrid?

Yes — MailTester integrates with SendGrid and other platforms like Mailchimp, HubSpot, and Klaviyo to clean and verify lists before sending.