How to Test Email Deliverability to Free Mail Providers Using Corporate Gateway Strategies
Test email deliverability to free mail providers with corporate gateway strategies. Use real inbox placement tests to verify inbox delivery and avoid spam.
Why Free Mail Providers Are a Hidden Challenge for Corporate Email Campaigns
You send a campaign to your customer base. Deliveries show up as "delivered" in your ESP dashboard. But open rates stay low — and you have no idea why. The message isn’t landing in inboxes. It’s sitting in spam, or worse, vanishing without a trace.
That’s not a broken campaign. It’s a blind spot in your delivery pipeline. Free email providers like Gmail, Yahoo, and Outlook use complex filtering systems that can block even legitimate corporate messages — not because they’re spam, but because of content patterns, sender reputation, or infrastructure signals that corporate gateways don’t see.
Testing email deliverability to free mail providers isn’t optional. It’s essential. Without direct, real-world testing, you can’t know if your message is blocked by spam filters, misrouted by DNS, or blacklisted due to reputation signals your gateway can’t detect.
Key takeaways
- Free email providers like Gmail and Yahoo apply aggressive spam filtering that can reject legitimate messages even when sending from a corporate gateway.
- Corporate email gateways often show success at the SMTP level but don’t reveal how messages land in consumer inboxes — creating blind spots in delivery performance.
- Without testing, you can’t distinguish whether low inbox placement stems from content, reputation, or technical misconfiguration — making troubleshooting ineffective.
How to Test Email Deliverability to Free Mail Providers Using Corporate Gateway Strategies
You can test email deliverability to free providers like Gmail, Yahoo, and Outlook by sending messages through your actual corporate SMTP stack to real inboxes, then tracking outcomes across multiple runs. This mirrors how your production system behaves, revealing whether filters, reputation, or sending patterns are causing issues. Use inbox placement tools that simulate realistic sending conditions, not just syntax checks.
- Set up a test environment that mirrors your corporate gateway. Use your actual outbound SMTP connection, including your sending domain, SPF, DKIM, and DMARC configuration. Sending from a real corporate setup ensures you catch delivery issues caused by infrastructure, reputation, or authentication mismatches that aren’t visible in test tools.
- Send test messages through your SMTP stack to curated real inboxes. Target known free email domains—Gmail, Yahoo, Outlook—using verified, non-disposable addresses. This gives you real-world data on whether your emails land in the inbox, are filtered to spam, or bounce. Avoid test-only email services; they don’t reflect actual filter behavior.
- Measure delivery outcomes over multiple test runs. Track results per message: delivered, filtered, bounced, or blocked. Run tests at different times, with varying content types (plain text, HTML, with attachments), and across different sender reputations. Repeat at least 3–5 times to spot patterns, not anomalies.
- Analyze results by domain, content, and sending time. Compare how Gmail handles a promotional HTML message sent at 9 AM versus 7 PM. Look at differences in filtering rates between Yahoo and Outlook. Isolate triggers—such as high image-to-text ratios, suspicious links, or sudden volume increases—that correlate with spam placement.
Why Real Inboxes Matter
Testing with simulated or disposable addresses gives false confidence. Filters at major providers rely on behavioral data—how recipients interact with messages, whether they open or mark as spam. Real inboxes provide meaningful signals. According to research by Spamhaus, over 90% of email delivery issues at free providers stem from sender behavior, not content alone. Your corporate gateway’s reputation and consistency are critical.
Use Tools That Reflect Real Conditions
Platforms like MailTester’s inbox placement tester allow you to send from your actual infrastructure while monitoring results across real inboxes. You gain insight into how your brand is perceived by Gmail and Yahoo’s systems, not just whether addresses are syntactically valid. This level of realism isn’t available with basic syntax checks. For teams using tools like SendGrid, Klaviyo, or HubSpot, MailTester’s integrations enable direct validation before sending at scale.
The Core Problem: Corporate Gateways Don’t Reflect Consumer Inbox Realities
When you send emails through your corporate SMTP gateway, you're using a private, reputation-built network that’s designed for internal reliability, not consumer inbox delivery. Public email providers like Gmail, Outlook, and Yahoo see your messages through a vastly different lens—based on IP history, sender reputation, and behavioral signals that your corporate stack doesn't replicate. The result? A valid email address can still end up in spam or blocked, even if the address itself is technically correct.
Why Corporate SMTP Isn't Enough for Consumer Deliverability
You might assume that if an email is syntactically valid and the domain responds, it should reach the inbox. But public email providers don’t just validate syntax—they evaluate the full context of the message. Your corporate gateway likely uses a shared IP range with no sender history, or one that’s never sent directly to Gmail or Outlook. These services rely on time-tested signals like consistent sending patterns, low complaint rates, and established domain reputation. A sudden burst of messages from an unfamiliar IP—even with valid addresses—triggers defensive filters.
For example, Gmail uses a blend of reputation scoring, behavioral analytics, and machine learning to assess incoming messages. A sudden spike in volume from a new or unused IP, even when the email is not spam, can trigger temporary quarantines or bounces. This is why a high-volume email sent through a corporate gateway might hit a 30% bounce rate despite all addresses being real.
Even with correct SPF, DKIM, and DMARC alignment, your corporate stack may lack the reputation signals that consumer providers trust. Public providers have no visibility into your internal network practices, and they can’t verify that your sender identity is stable or consistent. That disconnect lies at the heart of why test emails sent via corporate infrastructure can appear suspicious or fail delivery entirely.
Think of it this way: a corporate gateway is like a secure office door—strong, private, and functional within its context. But the public email inbox is a busy city street where every email must pass visual, behavioral, and historical checks. Sending through a gate that looks the same on the outside but operates under a different rulebook results in deliverability failures you can't see without real-world testing.
RFC 5321 defines SMTP as a flexible protocol, but it doesn’t mandate how receivers handle messages—each inbox provider applies its own rules. That’s why testing with tools that simulate real consumer senders is essential.
Use MailTester’s inbox placement tester to see how your messages are received by major email providers in real conditions. It reveals what happens when a message hits a Gmail or Outlook filter—not just whether the address is valid, but whether it’s welcome.
What You Can Measure: Real Deliverability Signals from Free Providers
You can measure whether your email lands in the primary inbox or gets filtered to spam, understand if bounces are temporary or permanent, detect if content triggers filters, and identify delivery delays signaling anti-spam scrutiny. These signals—when tracked consistently—reveal the true state of your deliverability to Gmail, Yahoo, Outlook.com, and other free providers.
Core Deliverability Signals to Track
- Did the email reach the primary inbox, spam folder, or get silently dropped? Use inbox placement testing to verify where your message is routed. Real-time testing across multiple free providers gives you the clearest signal.
- Distinguish between soft bounces (temporary issues like full inboxes), hard bounces (invalid addresses), and blocks (IP or domain-level filtering). A hard bounce means the address is dead; a block may suggest reputation problems, which industry reports show can stem from sender reputation, not just content.
- Check if keywords, links, or formatting triggered automatic filtering. Free providers use complex content rules—repeated phrases, excessive links, or HTML complexity can signal spam. Test with real user content to spot what’s being flagged.
- Monitor delivery speed. Delays over 15 seconds often indicate that the provider is applying scrutiny—possibly for rate limiting, reputation checks, or behavioral analysis.
- Look for inconsistent results across providers. Gmail and Yahoo use different reputation models; a message passing in one may fail in the other. Testing across multiple platforms reveals where your message is likely to be caught.
Why Corporate Gateway Strategies Fail (and What Actually Works)
Many companies rely on internal mail servers or corporate gateways for outbound campaigns. But these approaches don’t reflect end-user experience on free providers. Gateways often lack real mailbox behavior, deliverability reporting, and integration with anti-spam systems like Spamhaus or MxToolbox.
Let’s be clear: using your corporate gateway for testing deliverability to Gmail or Yahoo is like testing a car’s performance on a racetrack without ever driving on real roads. You miss the actual conditions.
Instead, simulate real user journeys with tools that send test messages directly from validated IPs to real free email accounts. This exposes true filtering behavior—without relying on internal infrastructure or synthetic data.
For consistent, actionable results, use the MailTester Inbox Placement tool to send test emails to real Gmail, Outlook, and Yahoo accounts and see where they land. It checks bounce types, delivery speed, and filtering behavior—all in one go. No guesswork.
Use the MailTester API to run this at scale, or verify lists ahead of send through the bulk verification tool. With 98.9% accuracy and credits that never expire, you’re set for long-term verification and testing. No fluff. Just measurable signals.
Why Traditional List Verification Isn’t Enough for Inbox Placement
You can verify 100% of your email list as valid and still have messages land in spam or disappear entirely—especially on free providers like Gmail or Yahoo. These services prioritize sender reputation and behavioral signals over address syntax alone, meaning a technically correct address might never reach the inbox. That’s why inbox placement testing matters more than just validation.
Validity Doesn’t Guarantee Inbox Delivery
A valid email address doesn’t mean it’ll land in the inbox. Gmail and Yahoo use aggressive anti-abuse filters that can deprioritize or quarantine messages based on sender behavior, even if the address is real.
Even if your message reaches the mailbox, it may be flagged as spam due to poor sender reputation, high bounce rates, or inconsistent engagement—factors traditional verifiers don’t assess.
Trap Doors in Free Mail Provider Strategies
Catch-all addresses on Gmail or Yahoo can technically receive mail, but they often trigger spam detection. Just because your message is delivered doesn’t mean it’s trusted.
Disposable email addresses—often used during signup—automatically get flagged by most providers as unreliable, even if they’re technically valid. Same with role addresses like admin@ or support@, which are frequently blacklisted due to high abuse volume.
These behaviors aren’t caught by syntax-only verification. They require active testing of how your email is treated in real inboxes, not just whether the address exists.
For example, a study by Return Path found that even low-volume senders with clean lists can see inbox placement drop below 80% when signals suggest spam-like behavior. This isn’t about one bad address—it’s about the reputation stack.
Let’s say your list passes basic validation. Great. But if your sender IP is on a blocklist, your engagement rate is low, or your content triggers filters, your messages won’t land in inboxes—even at free providers that accept most mail.
That’s where real inbox placement testing comes in. It simulates real user behavior and checks how your email performs across real domains like Gmail, Outlook, and Yahoo. The only way to confirm your message is actually landing in the inbox.
You need more than a list of valid addresses. You need insight into how your message is treated by real providers.
Use tools that test delivery from known gateways. MailTester’s inbox placement checker tests your message against real email environments and gives you a true signal: delivered to inbox, spam, or blocked.
Test your email deliverability now with real-world inbox placement reports, not theoretical validation.
How MailTester Enables Real-Time Inbox Placement Testing
You can test email deliverability to free mail providers like Gmail, Yahoo, and Outlook by sending real messages through your own corporate gateway—using MailTester’s inbox placement tests. It routes your email through actual provider networks, not simulated environments, so you see exactly how your message lands in real user inboxes, including whether it lands in spam, gets filtered, or is blocked. This reveals actual delivery behavior, not just theoretical scores.
The process: how your emails are tested in real time
- Send your message from your corporate gateway – MailTester doesn’t use mock servers. Instead, it sends your test email through your actual email infrastructure, just as a real campaign would.
- Deliver to real user inboxes across major providers – The test routes through actual Gmail, Yahoo, and Outlook networks. Each message lands in a real inbox, not a sandbox, so you see what your content looks like to actual users.
- Monitor delivery outcomes in real time – You get immediate feedback: delivered, filtered (to spam), or blocked. This includes details on why—such as sender reputation, content triggers, or alignment with provider policies.
- See diagnostic metadata from the receiving end – You receive data like the exact filtering reason (e.g., “spam score threshold exceeded”), routing path, and DMARC/DKIM alignment signals. These insights directly tie to inbox placement outcomes.
- Use the results to tune your strategy – With real-world data, you revise your content, sender setup, or list hygiene—before sending to larger audiences. This reduces the chance of being flagged by spam filters.
Why this matters
Many tools rely on historical data or black-box scoring. MailTester uses actual delivery infrastructure—just like the email providers themselves do. For example, Spamhaus tracks real-time spam patterns across mail providers; MailTester leverages that same principle by testing with live systems, not proxies.
You’re not testing a model. You’re testing what happens when your email hits the real inbox. This includes signals like SPF, DKIM, and DMARC alignment—critical for reputation. If your domain isn’t properly authenticated, even a well-written message gets dropped.
The results also expose how content affects delivery. A high spam score, for example, often triggers filtering even in legitimate domains. MailTester captures these triggers, so you can adjust subject lines, links, or HTML structure before it hurts deliverability.
The service is built for teams using corporate gateways—the kind that route email through internal infrastructure. If your domain sends from a shared IP pool or has mixed sender behavior, these tests show where your reputation breaks down.
Try real-time inbox placement testing now with MailTester’s inbox tester, built for teams that need transparency and accuracy—not guesswork.
Using the MailTester API to Automate Delivery Checks Across Free Providers
You can test email deliverability to free mail providers—like Gmail, Yahoo, and Outlook—by integrating MailTester’s real-time API into your workflow. This lets you validate addresses, check inbox placement, and catch delivery risks before sending to large lists, especially across corporate gateways where free domain delivery patterns often differ. Automate verification during list hygiene and post-send checks to reduce bounces and maintain sender reputation.
Build Deliverability Checks into Your Workflow
- Use the MailTester API to validate every email address in your list before deployment—especially critical for free providers where catch-all configurations and greylisting are common.
- Integrate the API into your list hygiene process to flag risky domains or disposable email addresses that often fail delivery to Gmail or Yahoo due to high spam correlation.
- Enable automated post-send checks for high-value campaigns, using the API to test inbox placement in real email clients and confirm delivery to free provider inboxes.
- Link the API with Mailchimp, HubSpot, Klaviyo, or SendGrid via webhooks or scheduled jobs to enforce delivery validation before each campaign dispatch.
- Use the inbox placement tester to simulate sending from your domain and see if emails land in primary inbox, spam, or are blocked entirely—specifically for Gmail, Outlook, and Yahoo.
- Filter out addresses that return as “catch-all” or “risky” to avoid wasting sends and to prevent sender reputation damage on high-volume domains.
What This Protects Against
Free email providers enforce stricter delivery standards. A single misconfigured DNS record or bad sender reputation can result in entire batches being quarantined. The MailTester API detects these issues early—before you waste sends or risk being blacklisted. Spamhaus and MxToolbox both track sender reputation patterns and blocklist behavior tied to such failures.
By embedding delivery checks into your automation stack, you ensure that every email sent through a corporate gateway has the highest chance of reaching the intended inbox—especially across the most sensitive free providers. The system doesn’t guess. It runs actual SMTP verification and reports true results. With 98.9% accuracy and credits that never expire, it’s built for scale and precision.
How to Use MailTester’s In-App AI Assistant for Deliverability Diagnostics
Ask the in-app AI assistant to analyze a failed delivery report, then request tailored fixes based on your domain and email content. It cross-references real delivery data, known filtering patterns, and sender reputation trends—from Gmail’s spam thresholds to Outlook’s content heuristics—without guesswork. You don’t need to interpret headers or logs; just describe the issue in plain English.
Analyze Delivery Failures with Natural Language
- Describe the failure in plain English. Type a query like “Why was my message filtered by Gmail?” or “My emails to Yahoo don’t land in inbox.” The AI parses the delivery outcome and scans for common triggers—suspicious sender reputation, unauthenticated domains, or content flagged as promotional.
- Request root-cause analysis. Ask the AI to evaluate a specific bounce or rejection. For example: “Show me all likely reasons my Mailchimp campaign failed for free email accounts.” It will list likely causes—like missing DMARC alignment or high spam-score content—ranked by probability based on historical data.
- Get recommendations tied to your domain and content. Query: “What should I change in my email content to improve Gmail inbox placement?” The AI references patterns from verified domains, identifies red flags (e.g., excessive links, all-caps subject lines), and suggests safer alternatives.
- Verify solutions before sending. Use the response to refine your email, then test again using Inbox Placement Testing—which simulates real inboxes across Gmail, Outlook, and Yahoo—to confirm the fix. No guesswork. Just real-time results.
- Track changes over time. Save past diagnostics to compare improvements. Over time, you’ll see reduced filtering and higher deliverability, even with bulk campaigns.
How the AI Works Behind the Scenes
The assistant uses more than just static rules—it learns from verified delivery outcomes across millions of emails. It checks sender reputation via public blocklists and internal data, evaluates authentication alignment (SPF, DKIM, DMARC), and weighs how content patterns correlate with inbox placement. This includes known filters: Gmail’s 100+ spam indicators, Outlook’s behavior-based scoring, and dynamic thresholds for disposable domains.
For instance, if you're sending to free email providers and your messages consistently land in spam, the AI may flag a mismatch in sender domain alignment or poor engagement history. It doesn’t just say “your domain is bad”—it explains why, with context, and suggests specific fixes. The output is transparent: you see not just the fix, but the data driving it.
For teams running large lists, this reduces hours of debugging. You can bulk verify emails first, then test deliverability, and finally use the AI to troubleshoot the small subset that fails—no need to analyze every header manually.
The Trade-Off: Testing Real Inboxes Requires Real Infrastructure
You can’t reliably test email deliverability to free mail providers like Gmail, Yahoo, or Outlook using basic tools or your own corporate gateway. These tools lack access to the actual provider networks and mailbox behaviors that determine inbox placement. Without real inbox testing, you’re guessing about how your emails will land—whether in the primary inbox, spam, or silently filtered out.
Why Free Tools Fall Short
Most email verification tools simulate delivery by checking syntax, domain existence, or mailbox responsiveness. But they don’t connect to actual consumer email infrastructure. As a result, they can’t detect how algorithms like Gmail’s spam scoring actually treat your message.
Even if your email passes syntax checks, it might still be rejected by the recipient provider’s filters. This isn’t visible through simple SMTP checks or validation tools. That’s why inbox placement testing is essential: it simulates how your email lands in real consumer mailboxes across real domains.
Corporate Gateways Have Limits
Testing via your corporate gateway gives you a partial view: you can confirm the email is routed and accepted by the provider's initial SMTP server. But that’s where the insight ends.
It doesn’t show what happens next—the spam filter, the client-side UI behavior, or how the user actually sees (or ignores) the email. A message can pass the gate and still be flagged or hidden in a low-visibility folder.
Provider-agnostic inbox testing tools access real consumer inboxes across the major free providers. They track the full delivery lifecycle: from SMTP handoff, through filtering and ranking, to actual inbox placement. Only this kind of testing reveals whether your email truly lands in the user’s view.
As noted in RFC 5321 (the core SMTP standard), delivery acceptance doesn’t equate to inbox placement. That distinction matters—especially at scale, where even a 5% drop in inbox delivery can impact engagement and conversion. Tools that mimic only the initial SMTP handshake miss the real endpoint behavior that drives deliverability.
For accurate results, use a service designed to test across actual mailbox environments. MailTester’s inbox placement tester sends real messages to live accounts at Gmail, Yahoo, and Outlook—giving you measurable data on how your campaigns perform in the actual environment where users receive mail.
Accurate, Actionable Results: How MailTester Delivers 98.9% Verification Accuracy
You don’t just validate email addresses—you test how they’ll behave in real inboxes. MailTester’s 98.9% accuracy combines address validity with inferred delivery outcomes across 60+ providers, including major free and corporate gateways. It’s not guesswork: you get clear verdicts like “delivered,” “blocked,” or “risky” based on actual behavior under real delivery conditions. This lets you act before sending, not after.
What Makes the Accuracy Real
- MailTester doesn’t rely on passive validation alone—it simulates real delivery attempts across domains like Gmail, Outlook, Yahoo, and corporate gateways (e.g., Microsoft 365, Google Workspace) using live infrastructure.
- Each email is tested against the actual SMTP, MX, and spam filtering behavior of the provider. This includes checking for catch-all responses, greylisting delays, and role account traps.
- Verdicts aren’t just “valid” or “invalid.” You see if an address will be delivered to the inbox, filtered to spam, blocked entirely, or flagged as risky due to past sending behavior or known abuse patterns.
- Results are updated in real time—no waiting for batch processing. You can test individual addresses or verify entire lists right before campaign launch.
- The system applies industry-standard checks: it verifies SPF, DKIM, and DMARC alignment, monitors sender reputation via blacklists (like Spamhaus Spamhaus), and flags disposable domains with known limitations in deliverability.
How This Changes Your Sending Strategy
- Instead of sending to 10,000 emails and hoping for a 70% inbox placement, you exclude addresses that will be blocked or sent to spam before the campaign starts.
- For free email providers like Gmail or Yahoo, MailTester identifies subtle delivery traps—like high bounce rates from new accounts or aggressive filtering on role addresses (e.g., admin@, sales@).
- Corporate gateways often enforce strict inbound policies. MailTester checks for common corporate blocking behaviors, such as rejected messages due to sender reputation, lack of authentication, or domain policy violations.
- With granular insights, you adjust your sending strategy: prioritize verified inboxes, re-evaluate warm-up patterns, or avoid high-risk providers altogether.
- Results are tied directly to real-world deliverability. You’re not optimizing for a theoretical score—you’re building campaigns based on actual inbox behavior.
“Testing deliverability before sending isn’t optional. It’s the only way to avoid damaging sender reputation and ensure your message reaches the right person.”
See how it works in practice: test your list with bulk verification, automate checks with the real-time API, or validate inbox placement with the inbox tester. All without committing to a long-term plan—just start with 100 free verifications at our pricing page.
Start Testing Today: 100 Free Verifications to Validate Your Gateway Strategy
Test how your corporate gateway delivers to Gmail, Yahoo, and Outlook with 100 free verifications. No risk, no commitment—just real-time feedback on deliverability performance.
Validate and Optimize Before You Scale
Use the results to adjust sender reputation, warm domains, or refine email content before launching larger campaigns. Persistent testing builds reliability with inbox providers.
Automate Deliverability Checks in Your Workflow
Integrate MailTester with Mailchimp, HubSpot, Klaviyo, or SendGrid to validate deliverability automatically before every send. Your inbox placement improves with every verification.
No credits expire—your purchased verifications stay active indefinitely. Every test strengthens your strategy.
Sources
- Benchmark testing of 15 major email service providers found about 10.5% of legitimate emails land in the spam folder and a further 6.4% go undelivered. — EmailTooltester deliverability benchmark (via WarmForge) (2026)
- Gmail delivered 87.2% of commercial email to the inbox in 2024 while sending 6.8% to spam — the best inbox rate of the four major mailbox providers. — Validity 2025 Email Deliverability Benchmark Report (2025)
Keep reading
- How to test email deliverability, spam score and rendering (complete guide)
- How Stale Is a Seed Account After 7 Days in Email Deliverability Testing?
- How Many Test Emails Are Needed to Measure Deliverability Performance
- How to Ensure Accurate Email Deliverability Testing Without Out of Office Noise
- How Does the ALL_TRUSTED Rule Affect Local Spam Test Scores?
Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.
Frequently asked questions
Can I test email deliverability to free providers without sending real emails?
No. Free providers require real messages sent through active gateways to assess inbox placement. Mock tests cannot replicate actual filtering behavior.
Why does my valid email address get filtered by Gmail even when I’m authenticating correctly?
Gmail filters based on sender reputation, content patterns, and delivery volume—not just technical authentication. A valid address may still be routed to spam.
How often should I test deliverability to free mail providers?
Test after domain setup, before major campaigns, and periodically during list warming to ensure consistent inbox placement.
Does MailTester simulate all major free email providers?
Yes. MailTester tests deliverability across Gmail, Yahoo, Outlook, and other top-tier free services using real infrastructure.
Can I test multiple domains at once with MailTester?
Yes. Use the bulk verification feature to test deliverability for dozens or hundreds of domains and recipient types simultaneously.
What’s the difference between address validation and inbox placement testing?
Address validation checks if an email exists. Inbox placement testing checks whether it lands in the inbox—crucial for free providers where delivery isn’t guaranteed.
How does MailTester detect if a message was filtered by Gmail?
It sends the message through your gateway, monitors real delivery status, and correlates it with known Gmail filtering signals.
Is inbox placement testing compatible with SendGrid or Mailchimp?
Yes. MailTester integrates with SendGrid, Mailchimp, HubSpot, and Klaviyo to test deliverability before sending through these platforms.
Can I use MailTester to test emails sent from a shared IP?
Yes. MailTester evaluates deliverability regardless of IP type—shared or dedicated—using real inbox feedback loops.
What happens if a free provider blocks my test message?
MailTester reports the block and analyzes the likely cause—sender reputation, content, volume, or blacklisting.
How accurate is MailTester’s inbox placement testing?
MailTester has a 98.9% accuracy rate across address validity and inbox placement prediction, validated through real delivery feedback.
Do I need to set up SPF or DKIM to test deliverability?
Yes. Proper authentication is required. Tests simulate real-world conditions where unauthenticated messages are more likely to be filtered.