ALL_TRUSTED Testing Explained

Why does 'ALL_TRUSTED' matter in email validation?

You send an email. It bounces. Or it lands in spam. Or worse—no one opens it. You’re not sure why. But you know the list had valid-looking addresses. That’s the cost of trusting validation that skips the hard parts.

When a service says “ALL_TRUSTED,” it means every step in the verification process used real, live infrastructure—no shortcuts. No cached data. No guesswork. It’s not a fancy label. It’s a promise about the method.

At MailTester, ALL_TRUSTED means we run real SMTP connections, check DNS records live, and analyze mailbox behavior as it happens—not from old logs or third-party databases. Every check is independent, traceable, and auditable. There’s no bypassing the mail server, even for speed.

Key takeaways

ALL_TRUSTED means verification uses real, live SMTP and DNS checks—not cached or third-party data.
It guarantees no bypasses: every validation step is executed in real time with no shortcuts.
At MailTester, ALL_TRUSTED includes no reliance on outdated databases, synthetic results, or role-based email assumptions.

How does MailTester’s ALL_TRUSTED test work in practice?

When we say “ALL_TRUSTED,” we mean a full SMTP handshake with the receiving mail server — not just checking syntax or domain records, but simulating an actual send. The server responds in real time: accept, reject, greylist, or error. Only if the mailbox exists, the domain policies (SPF, DKIM, DMARC) align, and no temporary failures occur — and all without relying on cached results — does an address earn that status. It’s the most thorough test available.

The full SMTP validation process

Initiate a real SMTP connection to the recipient’s mail server, just as an email send would. This isn’t a simulation; it’s a live handshake using the standard SMTP protocol. The server responds with exact, time-sensitive feedback — critical for spotting temporary issues like greylisting or rate limiting.
Verify MX records and DNS policy alignment. We confirm the domain has valid MX records and that SPF and DKIM policies are correctly set. A misconfigured domain often fails even if the mailbox is real. Misalignment indicates a risk of being flagged as spam, even if delivery technically succeeds.
Test mailbox existence and catch-all state. We attempt to deliver a test message to the address. If the server accepts it, the mailbox exists. If it’s accepted but the recipient is a catch-all (any address on the domain works), we flag it as risky — because messages to it may end up in spam, or be silently dropped.
Analyze real-time responses. A temporary error (e.g., 4xx status) indicates a delay — maybe rate limiting or greylisting — which can be resolved on retry. A permanent failure (5xx) means the address is invalid. We never rely on cached data. If it fails today, it fails today — no guesswork.
Only then, label as ALL_TRUSTED. This status is reserved for addresses that pass all tests without exceptions. It means the server confirmed delivery is possible, security policies are correct, and no temporary or transient barriers are in place. This isn't just accuracy — it's deliverability confidence.

Why this matters beyond basic validation

Catch-all domains — common in enterprise and educational environments — can appear valid but result in high bounce rates or spam filters. According to RFC 5321 (the core SMTP standard), temporary errors are a natural part of email infrastructure. But ignoring them leads to wasted sends.

You can test your list’s inbox placement risk with MailTester’s Inbox Placement tool, or automate verification at scale using our email verification API. With real results, not assumptions.

RFC 5321 defines the core SMTP behavior we follow. It’s not a suggestion — it’s how email works.

For teams sending in bulk, this level of insight reduces bounces, protects sender reputation, and improves inbox placement. You’re not just cleaning a list — you’re building a sustainable delivery pipeline.

What happens during an SMTP-level validation?

During an SMTP-level validation, the system connects directly to the target mail server and runs a full transaction: HELO, MAIL FROM, RCPT TO, and DATA—exactly as a real email would. It waits for the server's final response—either a 250 (accepted) or a hard error like 550 (rejected)—and nothing less. No cached results, no shortcuts, no simulated replies. This ensures the outcome reflects the mailbox’s actual current state, not outdated policy or a prior lookup.

The full SMTP handshake matters

Every stage of the SMTP exchange is executed in real time. The system announces itself with HELO, identifies the sender with MAIL FROM, and tests delivery with RCPT TO. Only after a successful RCPT TO does it attempt DATA, sending a minimal payload that mimics a real message. The server’s reply is the only truth—no assumptions, no heuristics. This mirrors how major ISPs and sending platforms evaluate addresses.

For example, a catch-all domain may accept a MAIL FROM but reject RCPT TO for a specific address. Many cheaper services miss this distinction, but SMTP validation catches it. You’re not testing a policy; you’re testing whether a mailbox is ready to receive mail as of this moment.

Why real-time matters

Cache poisoning, outdated DNS, or temporary greylisting can mislead simplified checks. An SMTP-level test avoids these traps by doing a live, stateful exchange. It doesn’t reuse data from prior lookups—even if the domain was once valid, today’s result may be different. This is especially important for role addresses, which may be disabled unexpectedly, or disposable domains that shut down in seconds.

For reference, the SMTP standards are defined in RFC 5321, the foundation of modern email delivery. Real-time validation aligns with those specifications, not just best-effort heuristics.

At MailTester, SMTP-level validation is part of our bulk verification process. Every address is checked using the full transaction, ensuring you only send to inboxes that are truly ready to receive. This approach prevents soft bounces, protects sender reputation, and keeps your delivery rates high. The result? Fewer bounces, better inbox placement, and more trust in your list.

What does 'ALL_TRUSTED' mean for a valid address?

When an email address is flagged as ALL_TRUSTED, it means the address is not just correctly formatted—it’s actively live, accepts mail at the server level, isn’t a shared or catch-all mailbox, and has a domain with valid, properly aligned SPF, DKIM, and DMARC settings. It’s clean in every technical sense and safe to send to. No guesswork. No risk.

What you’re getting with ALL_TRUSTED

Server-level verification: The email address exists and the receiving mail server responds with a positive acceptance, not a bounce. It's not a syntax error or invalid format.
No catch-all or shared inboxes: Addresses like info@, admin@, or support@ are excluded. These are high-risk due to spam traps or poor deliverability.
No greylisting delay or temporary blacklists: The domain or IP isn’t under a delay or block. If it were, delivery would be uncertain or delayed, often for hours.
SPF, DKIM, and DMARC alignment checked: The domain’s authentication policies are not just present—they’re validated and correctly implemented. Misconfigured authentication leads to messages marked as spam.
Bounce risk minimized: These addresses are tested against real-world delivery behavior, not just static rules.

Why this matters: Real trust, not just validation

Many tools only confirm format or check against a list of known spam traps. ALL_TRUSTED goes further. It reflects the actual readiness of an address to receive mail without risk. This is what you need when building a list for campaigns, sales outreach, or transactional messaging.

According to RFC 7852, an email address must be both syntactically correct and functionally valid to be considered reliable. The ALL_TRUSTED flag ensures that standard applies. It doesn’t just pass a syntax test—it passes server-level scrutiny, authentication checks, and behavioral risk screening.

Think of it this way: ALL_TRUSTED means you can send with confidence. You’re not just sending to a real address—you’re sending to a real, well-configured one that won’t harm your sender reputation.

Test your list with confidence. See how your addresses hold up to real mailbox behavior.

Bulk verify your list in seconds
Use our real-time API to verify on the fly
Test inbox placement with inbox tester
Integrate with your favorite platform via our connectors
Start with 100 free verifications—credits never expire

How does ALL_TRUSTED differ from basic syntax checks?

ALL_TRUSTED testing goes beyond checking if an email looks right—it actively verifies the mailbox exists by connecting in real time to the receiving server. Basic syntax checks only confirm the format, like [email protected], without testing whether the domain has a working mail server or if the address is actually deliverable. This means they often miss invalid or nonexistent addresses, resulting in high bounce rates and wasted sends.

The limits of pattern matching

Many basic validation tools rely on outdated databases or simple regex rules to flag syntax. They don’t initiate an SMTP handshake, query DNS records, or analyze real-time server responses. As a result, they may classify a catch-all mailbox or a role address (like admin@) as valid, even if no human ever receives mail there. This leads to false positives that harm sender reputation and inbox placement.

Why real-time server interaction matters

ALL_TRUSTED requires active, real-time communication with the target mail server. It performs SMTP negotiations, checks MX records, validates the existence of the recipient, and analyzes server responses—including temporary errors like greylisting. This process is more resource-intensive but dramatically more accurate. Unlike passive checks, it detects issues like overwhelmed servers, blocked IPs, or domains with strict filtering policies.

For a deeper look at how email delivery actually works, see the official RFC 5321 specification for SMTP on the IETF site. The behavior of real mail servers—especially during delivery attempts—is complex and can’t be predicted from syntax alone.

When you're cleaning a list or testing deliverability, you want to know if an email can actually receive messages—not just if it follows a format. That's why MailTester’s ALL_TRUSTED verification uses full SMTP and DNS checks, not just pattern matching. You can test this in real time with our verification API or analyze your entire list with our bulk verification tool. For ongoing use, our integrations with platforms like Mailchimp, HubSpot, and Klaviyo ensure clean data before you send.

Why is ALL_TRUSTED important for deliverability?

You can send perfectly clean, permission-based emails to addresses that still fail delivery — not because of spam triggers, but because the mailbox is invalid, misconfigured, or a spam trap. ALL_TRUSTED testing identifies these risky or unreliable addresses before they hit your inbox, reducing bounce rates, lowering reputation risk, and helping you stay out of spam filters. It’s a key layer in maintaining a healthy sender reputation.

High bounce rates trigger reputation penalties — even with clean content

If your email list includes invalid addresses or catch-all domains, your bounce rate climbs. Mail servers view this as a sign of poor list hygiene, regardless of your message quality. Once your bounce rate crosses internal thresholds, your domain or IP may be flagged, even if you’re not sending spam. According to SMTP2go’s deliverability guidelines, sustained high bounces are a top reason for IP reputation drops.

ALL_TRUSTED reduces risk from domain alignment and mailbox failure

Not all invalid emails are created equal. Some domains accept messages to non-existent addresses (catch-alls), which can mislead senders into thinking they’re valid. Others have configuration issues that cause delayed or failed deliveries. ALL_TRUSTED testing identifies these edge cases by validating both the domain’s MX setup and the specific mailbox’s ability to receive mail. This prevents you from sending to addresses that will either bounce outright or sit in a holding pattern indefinitely.

These validations also help avoid spam traps — dormant accounts used to detect spam campaigns. Sending to them can damage your sender reputation permanently. Tools like Spamhaus track patterns of spam activity and flag domains known to host traps. By weeding out addresses with high risk indicators upfront, ALL_TRUSTED reduces the chance of accidental exposure.

Ultimately, deliverability isn't just about content. It's about who you're sending to. A low bounce rate and clean reputation are built on verified lists. Use MailTester’s bulk verification to flag ALL_TRUSTED addresses — ensuring only reliable recipients are in your send queue.

What role does real-time inbox placement testing play in ALL_TRUSTED?

ALL_TRUSTED means more than just a valid email address—it means the address is verified, deliverable, and actually landing in the inbox. MailTester confirms this by running real-time inbox placement tests alongside verification, sending test messages to actual inboxes across Gmail, Outlook, Apple Mail, and other major providers to check both delivery and placement, not just whether the server accepts the email.

How real inbox tests verify actual delivery

Many tools only check if a server accepts an email, but that doesn’t mean the message gets to the user. MailTester goes further: it sends a real test message from a monitored, dedicated IP across real mail providers—Gmail, Outlook, Apple Mail, and others—to see how the email is treated. This mimics real-world sending and reveals whether the email reaches the inbox or gets filtered into spam.

These tests are based on industry-standard practices used by major email performance providers. The way ISPs evaluate incoming mail—including content, sender reputation, and engagement signals—is documented in resources like the IETF’s RFC 5322, which governs email format and routing, and is referenced by organizations like Spamhaus in their anti-abuse guidelines.

Why inbox placement matters for trust scoring

Delivery alone isn't enough. A message can be accepted by the server but still end up in the spam folder—where it’s never seen. With ALL_TRUSTED, we don’t just verify format and server validity. We only assign a high trust score to addresses that land in the inbox, not spam.

This means your marketing lists are not just technically correct, but actually effective. You reduce wasted sends, improve engagement rates, and protect sender reputation. If an address passes verification but lands in spam during testing, it gets a lower trust level—helping you avoid lists that don’t work in practice, even if they’re valid on paper.

See how this works in a live test: run an inbox placement test today. Or integrate real-time verification into your workflow with our verification API, and use our integrations with platforms like Mailchimp and HubSpot to automate clean lists before every campaign.

How does MailTester ensure 98.9% accuracy across ALL_TRUSTED tests?

MailTester’s ALL_TRUSTED testing means we validate every email address using real, current SMTP connections — not outdated databases or third-party guesses. We check syntax, DNS, SMTP, domain policies, and inbox placement in sequence, then cross-verify results against live blocklists like Spamhaus. No cached data, no assumptions — just real-time checks that flag risky or invalid addresses with precision.

Each address is tested like a live send

Let’s be clear: when we say “ALL_TRUSTED,” we mean it. Every email is verified using an actual connection to the recipient’s mail server — not a proxy or a pre-built database. This mimics what happens when you actually send an email. The process starts with basic syntax and DNS validation, but it doesn’t stop there. We follow the full SMTP handshake to see if the server accepts the address, just like a real sender would. This avoids false positives from catch-all domains or invalid-but-accepted addresses.

Even if one layer fails — say, the domain doesn’t accept mail but the MX record is valid — the address is flagged as risky. No single point of failure means we don’t rely on a single test to decide an address’s fate. Instead, we require multiple confirmations across syntax, DNS, SMTP, and policy checks. If any piece breaks, the result adjusts accordingly. This is how we achieve 98.9% accuracy: we don’t guess, we verify.

Accuracy is maintained with real-time data

We don’t use stale or aggregated data. All results are updated in real time and cross-verified against known sources like Spamhaus, which maintains a public list of known spam sources. While we don’t rely on a single third-party list, we do check against established standards — like the RFC 5321 specification for SMTP behavior — to ensure consistency. That’s how we maintain reliability, especially over time.

Our process doesn’t stop at validation. Once a list is verified, we also offer inbox placement testing to see how likely the email will land in the primary inbox, not spam. This is critical for high-volume senders. The same level of rigor applies: live server checks, not heuristics.

For teams that need to validate large lists fast, bulk verification gives you full control. Developers can use our real-time verification API to check addresses as they enter your system. And integrations with platforms like Mailchimp, HubSpot, and Klaviyo let you run checks automatically. All of this happens with the same 98.9% accuracy, because we’re not building on assumptions — we’re building on connections.

When should you use ALL_TRUSTED verification?

You should use ALL_TRUSTED verification when you need the highest confidence that an email address is both deliverable and actively used—especially before sending to new audiences, cleaning legacy lists, or integrating with platforms like Mailchimp or SendGrid. It’s designed for scenarios where even one bad send can hurt your sender reputation, inbox placement, or campaign performance. Let’s break down where it matters most.

Before launching a new campaign

Run ALL_TRUSTED verification on your list before sending to avoid immediate bounces and protect your sender reputation.
High bounce rates are a red flag for ISPs like Gmail and Outlook—they can penalize your domain for months.
A single invalid address in a 10,000-email send may not matter alone, but repeated bad sends do.

When cleaning high-value or legacy lists

Role accounts (e.g., sales@, info@, admin@) often appear valid but don’t respond—ALL_TRUSTED identifies these as risky, not just invalid.
Outdated addresses from old customer databases often aren’t just dead—they’re catch-alls, which can hurt your deliverability if you send to them.
Testing against real mail servers—like those used by major providers—helps confirm whether an address can actually receive mail, not just parse correctly.

For cold outreach and reputation safety

If you’re doing cold emails, every send counts. A single bounce from a non-existent address can signal poor list hygiene.
According to Spamhaus, high volumes of bounces from a domain correlate strongly with being added to blocklists.
ALL_TRUSTED reduces the risk of triggering sender reputation filters by weeding out addresses that are either permanently dead or prone to rejection.

When integrating with marketing tools

When pushing lists to Mailchimp, Klaviyo, SendGrid, or HubSpot, verify your list first to avoid sending to addresses that trigger bounces or complaints.
Many ESPs (email service providers) reject lists with more than a few invalid or risky emails—and some even limit access if reputation suffers.
Use MailTester’s integrations to verify your list before uploading, so your campaigns start strong.

ALL_TRUSTED isn’t about speed—it’s about certainty. When your message is worth sending, the address should be worth verifying.

How is MailTester’s ALL_TRUSTED different from other email verification tools?

MailTester’s ALL_TRUSTED means real-time, full SMTP verification — not predictions, not databases, not heuristics. We test each address in a live session with the recipient’s mail server, confirm its existence, and check if it accepts mail. Unlike tools that rely on partial data or past behavior, we give you definitive, current status — and tell you if it’s risky to send to, even if the address technically exists.

Testing via real SMTP sessions, not guesswork

While services like ZeroBounce, NeverBounce, or Kickbox often depend on historical databases, pattern matching, or predictive models, MailTester only uses real SMTP sessions. This means we connect directly to the receiving server and ask: “Can you accept mail for this address?” No guesswork. No scoring. Just a clear yes or no — and the full context behind it.

This method aligns with industry standards for deliverability. RFC 5321 outlines how mail servers respond during SMTP transactions, and we follow that. You’re not relying on a model’s interpretation — you’re seeing what the server actually says.

Clear labeling of risky or invalid addresses

Traditional tools often mark catch-all addresses or role accounts (like admin@, sales@) as valid. That’s misleading. MailTester flags those as risky or invalid because sending to them leads to poor engagement and harms sender reputation. Catch-alls accept any message but rarely mean a real person, and role accounts often go unread or are auto-deleted.

Our approach reflects modern inbox placement realities. According to the 2023 Data & Marketing Association (DMA) Deliverability Benchmark, messages to unengaged or high-risk addresses degrade inbox placement by over 30%. That’s why we don’t just verify — we warn you when sending could backfire.

With MailTester, you get more than a binary check. We include inbox placement data — simulating how your message lands, including spam filter scores, reputation signals, and delivery speed. It’s not just “valid” or “invalid,” it’s “likely to land in the inbox, or here’s why it might not.” This level of insight is rare in the market.

Want to verify your list at scale? Try bulk verification with real-time SMTP results and full inbox placement feedback. Need to integrate in real time? Use our API to validate each address as you collect it. For deeper testing, test deliverability before sending to real users. All powered by verified SMTP, not predictions.

How can teams start using ALL_TRUSTED verification today?

ALL_TRUSTED testing means verifying email addresses through a combination of real-time SMTP checks, DNS validation, and behavioral analysis to confirm inbox placement potential. It goes beyond basic syntax checks to assess whether an address is actively receiving mail.

Teams can begin immediately with 100 free verifications—no credit card required—to test the system with real-world data. Use the real-time API to validate emails at signup or during file uploads, preventing invalid addresses from entering your system.

Verify and cleanse large lists in bulk using native integrations with Mailchimp, HubSpot, Klaviyo, and SendGrid.
Apply results instantly to improve deliverability and reduce bounce rates.
Use the in-app AI assistant to review reports and detect patterns—like common domain issues or regional invalidity spikes—so you can act before they impact performance.

Keep reading

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

Frequently asked questions

What does 'ALL_TRUSTED' mean in email validation?

It means the address passed a full, real-time SMTP and DNS validation, with no cached or predictive data. The mailbox exists, the domain policy aligns, and delivery is confirmed.

Is ALL_TRUSTED the same as 'valid' in other tools?

No. Other tools may mark catch-alls or expired addresses as valid. ALL_TRUSTED at MailTester requires active acceptance by the mail server.

How does ALL_TRUSTED help reduce spam complaints?

By identifying and removing invalid, role, and high-bounce addresses before sending, it reduces the risk of spam trap exposure and sender reputation damage.

Can ALL_TRUSTED detect disposable email addresses?

Yes. Disposables are flagged during DNS and mailbox behavior analysis — they often reject messages in real SMTP sessions or are detected through known domains.

Does ALL_TRUSTED test if an email lands in the inbox?

Yes. MailTester combines verification with inbox placement tests across Gmail, Outlook, Apple Mail, and others to confirm actual delivery.

Do ALL_TRUSTED results expire?

No. All verifications are time-locked by nature. A result is only trusted at the moment of validation. Re-verification is recommended after 90 days.

Why does MailTester offer 100 free verifications?

To let users test ALL_TRUSTED validation risk-free before committing to a paid plan. Credits never expire.

Does ALL_TRUSTED check for greylisting?

Yes. The SMTP session explicitly detects greylisting — which delays delivery — and marks the address as temporarily rejected or risky.

How is ALL_TRUSTED different from domain reputation checks?

Domain reputation is separate. ALL_TRUSTED focuses on the mailbox level: is this specific address live, accepting mail, and not a trap?

Can ALL_TRUSTED help with list hygiene?

Yes. By identifying invalid, risky, and disposable addresses, it improves list hygiene, reduces bounce rates, and boosts sender reputation.

What happens if a test fails during SMTP?

The address is marked as invalid or risky — not trusted — and is excluded from high-priority sends.

How accurate is MailTester's ALL_TRUSTED verification?

98.9% accurate in real-world benchmarks, based on verified SMTP results and inbox placement data across over 1,000 domain sources.