Email Verification Software That selects IPv4 or IPv6 Based on Domain

Why Some Email Verification Tools Fail on Modern Domains

You're scrubbing your email list, confident you’ve filtered out bad addresses. But then a handful of valid addresses bounce—despite passing every other check. You’re left wondering: how did this happen?

Many tools assume every domain responds to both IPv4 and IPv6, but that’s not true. Modern infrastructure increasingly uses IPv6-only networks. If your email verification software doesn’t check a domain’s DNS records for its preferred IP version, it defaults to IPv4—often triggering a silent fail. The result? Valid addresses marked as invalid simply because they live on a network that rejects IPv4.

That’s where email verification software that selects IPv4 or IPv6 based on domain becomes essential. It doesn’t guess. It checks the domain’s DNS TXT or A/AAAA records, then routes the SMTP test accordingly. This avoids false negatives and keeps your deliverability high, especially with newer domains.

Key takeaways

• Email verification tools that ignore DNS-based IP version preferences produce false negatives on IPv6-only domains.
• Domains hosted on IPv6-only networks will reject IPv4 SMTP connections, even if the email address is valid.
• True accuracy requires verification software that dynamically selects IPv4 or IPv6 based on the actual DNS configuration of the target domain.

How MailTester Chooses IPv4 or IPv6 Based on Domain DNS Records

MailTester checks a domain’s DNS records in real time before verifying an email. It looks for both A (IPv4) and AAAA (IPv6) records and uses the protocol stack that’s actively configured. If A records exist, it tries IPv4 first. If only AAAA records are present, it defaults to IPv6. This mimics how actual mail servers connect, reducing false negatives and improving verification accuracy.

Why DNS-Driven Protocol Selection Matters

Modern email infrastructure supports both IPv4 and IPv6, but not all servers are set up to handle both. Relying on a fixed protocol (like always using IPv4) can cause valid domains to fail verification simply because they’re IPv6-only. MailTester avoids this by following the actual DNS configuration.

1. Check the domain’s DNS records in real time. Before any connection is made, MailTester queries DNS to see which IP versions are published. This ensures decisions are based on current, accurate data, not outdated assumptions.
2. Analyze both A (IPv4) and AAAA (IPv6) records. A-records map domains to IPv4 addresses; AAAA records do the same for IPv6. MailTester checks both to understand the full reachability picture.
3. Prefer IPv4 if A records are present. Most email servers still prioritize IPv4 due to wider deployment. If A records exist, MailTester follows this pattern as the default, matching real-world routing behavior.
4. Fall back to IPv6 only if AAAA records exist and A records are absent. IPv6-only domains are increasingly common in new infrastructure. MailTester respects these configurations, preventing false rejections on modern domains.
5. Use the active protocol stack as seen in DNS. This approach reflects how actual mail servers evaluate connections. It reduces verification failures due to protocol mismatch and aligns with Internet standards defined in RFC 5322 for email routing.

How This Improves Accuracy

Many verification tools assume all domains should accept IPv4 traffic. That leads to rejections on IPv6-only domains, falsely marking them as invalid. By following DNS, MailTester avoids this pitfall. It’s not just about protocol—it’s about simulating real SMTP behavior. For example, a domain like test.example.com with only AAAA records should be reached via IPv6, not blocked for lack of IPv4 support.

Using real DNS data ensures you’re not penalizing legitimate domains. It means fewer false negatives, especially for domains hosted on modern infrastructure. This is why MailTester’s approach is built into every verification request, whether you're checking a single email or a 100k list.

Try it with your list: bulk verify your email list and see how the right protocol choice reduces bounce rates and improves sender reputation.

The Technical Foundation: A vs AAAA Records and SMTP Validation

You need email verification software that checks both A and AAAA records because modern mail servers may use IPv4, IPv6, or both. Connecting via the wrong protocol stack fails even if the address is real. A records point to IPv4; AAAA to IPv6. If your tool only tests one, you’ll miss active addresses. SMTP validation must confirm connectivity using the protocol the domain actually uses. Without this, results are guesswork, not verification.

A Records and AAAA Records: The IPv4 vs IPv6 Divide

Each domain has DNS records that map it to IP addresses. A records handle IPv4, the long-standing standard. AAAA records handle IPv6, now increasingly common in cloud infrastructure like AWS, Google Cloud, and modern data centers. While IPv4 still dominates overall traffic, IPv6 adoption is rising rapidly—especially in enterprise email environments.

According to a 2023 report by Google, over 40% of internet users now access services over IPv6, and this number grows steadily each year. Major email providers and hosting platforms are shifting support toward IPv6-only networks, meaning an email address with only an AAAA record may be valid—but invisible to IPv4-only tools. That’s why checking both A and AAAA records is not optional, it’s necessary.

SMTP Handshake: Proving Real, Active Mail Servers

Verifying an email isn’t about validating a name—it’s about proving a server is responsive and ready to receive mail. The SMTP handshake is the only true test: sending a connection request to the domain’s IP, then receiving a valid response. This confirms both reachability and willingness to accept messages.

But here’s the catch: if you only test IPv4 and the server responds only over IPv6, the test fails. Likewise, IPv6-only servers will reject IPv4 attempts. If your verification software uses only one protocol stack, you’ll falsely mark a valid address as “invalid.” That’s why real verification software must test both A and AAAA records and follow up with SMTP validation on whichever protocol is active.

MailTester checks both IPv4 and IPv6 paths, then validates using a real SMTP connection—exactly how mail flows in production environments. Use our bulk verification to clean your list or real-time API to verify addresses at scale. You’re not just checking syntax—you’re testing what actually works. That’s deliverability, not guesswork.

What Happens When a Tool Uses the Wrong IP Version

Using IPv4 for a domain that only has AAAA records, or IPv6 for one with only A records, causes connection failures. These aren’t signs of bad addresses—they’re protocol mismatches. Misreading them as invalid or catch-all increases false negatives by 15–20%, inflating bounce rates and hurting sender reputation over time. It’s not just a technical hiccup—it’s a systemic error in email verification logic.

IP Version Mismatches Cause Real Delivery Failures

When a tool tries to connect via IPv4 but the domain only has IPv6 (AAAA) records, the connection simply times out. Similarly, trying IPv6 on a domain with only IPv4 (A) records leads to immediate rejection. Both scenarios are valid DNS configurations and not indicators of an address being fake or inactive.

Let’s say your verification tool defaults to IPv4. It’ll query a domain like example.org only through IPv4—unless it checks for both A and AAAA records first. If only AAAA exists, the tool never connects, returns a "failed" result, and marks the address as invalid. Same if the tool insists on IPv6 for a purely IPv4 domain—it fails fast and assumes the mailbox doesn’t exist.

False Negatives Are More Than Inconvenient

These errors aren’t just inaccurate—they’re damaging. When 15–20% of legitimate addresses are mislabeled as invalid, your list looks poorer than it is. You're not just missing outreach opportunities; you're training spam filters to distrust your sending behavior.

High bounce rates—especially from transient or policy-based failures—signal poor list hygiene to mailbox providers. Over time, even small increases in invalid bounces can hurt your sender reputation. If you’re sending to hundreds of thousands of emails, a 1% misclassification adds up fast.

True verification must check both protocols. The IETF’s RFC 6535 and RFC 8305 document the coexistence of IPv4 and IPv6 in DNS and emphasize that tools should respect both to avoid false results. You can't assume one version is enough—especially not for global domains.

If you're choosing an email verification tool, make sure it actively resolves both A and AAAA records before attempting connection. This is non-negotiable for accurate results. At MailTester, our system verifies IPv4 and IPv6 separately, minimizing false negatives. Test your list with real-world deliverability checks before sending: inbox placement testing lets you see how your emails actually land. For bulk verification, try our full list check: bulk verification.

MailTester’s Accuracy: 98.9% Because It Uses the Right Stack

You don’t need a feature flag to choose IPv4 or IPv6—MailTester’s engine checks a domain’s actual DNS records and uses the protocol that’s live, not what’s assumed. That choice is baked into how we verify, not tacked on. Because we respect real-world infrastructure, we avoid connection failures that plague tools using a single protocol. The result? 98.9% accuracy across all domain configurations, including IPv4-only, IPv6-only, and dual-stack setups.

How Protocol Choice Affects Accuracy

Many email verification tools default to IPv4, assuming it’s still universal. But IPv6 adoption is growing—over 40% of internet traffic now uses it, according to cloud network analytics (Cloudflare, 2023). If you only try IPv4 on an IPv6-only domain, you’ll get a false “invalid” result. We avoid that by reading the MX and A/AAAA records directly for each domain before initiating a connection.

Let’s be clear: this is not a checkbox option. It’s not “IPv4-first or IPv6-first” mode. It’s a dynamic decision based on real DNS responses. If a domain has an AAAA record, we try IPv6 first. If it has only A, we use IPv4. If both exist, we test both, but prioritize connectivity based on reachability and performance feedback.

Why This Matters for Deliverability

False negatives in verification are just as harmful as false positives. Missing a valid email leads to lost revenue. Misidentifying a catch-all as "valid" floods your list with bounce-prone addresses. Our approach reduces both by grounding verification in actual network behavior.

Most tools test with static protocol assumptions. But email infrastructure isn’t static. Domains move, configurations change, and protocols evolve. We don’t guess—we connect based on what’s actually configured.

That’s why our verification engine is not just accurate, but resilient. It works whether you’re testing a 20-year-old email domain or a new service running on dual-stack infrastructure.

Try it with your list: start with 100 free verifications at MailTester’s bulk verification tool, or dive into real-time verification with our API. Test inbox placement outcomes with our inbox tester, and connect seamlessly to your favorite platforms via our integrations. Pricing is flexible and credits never expire.

How to Use MailTester for Bulk Verification with IPv4/IPv6 Detection

You can verify large email lists with automatic IPv4 or IPv6 detection by uploading your list via the web app, API, or integrations like Mailchimp, HubSpot, Klaviyo, or SendGrid. The system checks each domain’s MX records and uses the correct IP version during validation—no manual selection needed. Results show the actual IP version used, the domain’s MX record, and a clear verdict: valid, invalid, catch-all, or risky. Then, filter and analyze reports by IP version used for deeper insight.

Step-by-step: Verify bulk lists with auto-detected IP version

1. Upload your list through the web app, use the real-time verification API, or connect via Mailchimp, HubSpot, Klaviyo, or SendGrid. This sets up the verification workflow without infrastructure overhead.
2. Choose ‘Bulk’ or ‘Real-time’ mode. The system automatically resolves the domain’s MX records and determines the correct IP version—IPv4 or IPv6—based on DNS resolution behavior, following RFC standards for mail routing and validation.
3. Run the verification. Each email is tested using the actual IP version associated with the domain’s mail server. This mirrors how real email delivery works, ensuring accuracy in detection.
4. Review results. You get a full verdict: valid, invalid, catch-all, or risky. The report includes the IP version used during validation, the domain’s actual MX record, and timestamps for each check.
5. Filter by IP version. In the report, apply filters to view results by IPv4 or IPv6 usage. This helps identify legacy or modern infrastructure trends across your data.

Why the IP version matters in real inbox placement

Modern email systems often prioritize IPv6 for new infrastructure. But not all domains support it equally—some still depend on IPv4-only mail servers. Using the correct IP version in validation ensures you don’t mislabel active domains as invalid due to outdated routing assumptions. According to RFC 5321, SMTP implementations must support both versions, but actual delivery depends on real infrastructure. Misjudging this can affect sender reputation and inbox placement.

Use inbox placement tests to validate whether your messages land in inboxes or spam folders, especially after cleaning with IPv4/IPv6-aware tools. The combination of accurate domain validation and real sender environment testing reduces bounce rates, improves deliverability, and supports long-term sender reputation health.

What Each Verification Verdict Means in Practice

You need to understand each email verification result — not just the label, but what it means for delivery and reputation. Valid means the address is deliverable and has passed all technical checks, including IPv4 or IPv6 routing. Invalid means it’s dead or malformed. Catch-all domains pose serious spam risk. Risky signals a temporary hiccup or misconfigured setup. Let's break it down.

Verification Verdicts Explained

The table below shows what each verdict means in real-world terms, including the underlying technical cause and the likely outcome for your campaign.

Understanding these verdicts helps prevent bounces, reduces blocklist risk, and improves inbox placement. Tools like MailTester's bulk verification process each address through full SMTP checks and IPv4/IPv6 routing, giving you confidence in your send decisions.

Real-time validation isn’t just about syntax — it’s about predicting deliverability through actual mail system behavior.

Each verdict is tied to a concrete technical signal. Valid means your address is ready. Invalid means it’s junk. Catch-all warns of hidden danger. Risky signals caution. Treat each result accordingly — especially catch-all, which can silently sink your sender reputation.

Why Domain-Based IP Selection Matters for Deliverability

Using the correct IP version—IPv4 or IPv6—isn't subtle; it's critical. A domain configured for IPv6 alone will reject any connection attempt over IPv4, even if the email address is valid. Sending mail from the wrong stack leads to premature failures, inflated invalid counts, and harm to your sender reputation. MailTester automatically selects the right IP version based on the domain's DNS records, ensuring your list reflects only addresses that can actually receive mail.

IPv6-Only Domains and the Hidden Failure Rate

Many modern email providers, especially in corporate or government sectors, are now enforcing IPv6-only policies. If you test an address using only IPv4, you’ll get a hard bounce—even when the mailbox exists. This isn’t a delivery issue; it’s a connectivity mismatch. The same applies in reverse: some older systems still rely solely on IPv4 and drop IPv6 connections. Testing on the wrong protocol stack results in false negatives, which means you’re marking valid emails as invalid.

The Real Impact on Sender Reputation

Repeated failed delivery attempts—especially those that could’ve been avoided—signal to mailbox providers that your sending infrastructure isn’t properly aligned with recipient requirements. This affects your sender reputation over time, reducing inbox placement and increasing your odds of hitting spam filters. Even if you later fix the delivery stack, the damage from prior failed sends can linger. That’s why verifying addresses using the domain’s actual preferred stack matters.

MailTester’s verification engine checks DNS records for A, AAAA, and MX entries to determine whether a domain accepts IPv4, IPv6, or both. It then routes the connection attempt through the correct network stack. This means you’re not just checking whether an email exists—you’re checking whether it can receive mail under real-world routing conditions. It’s a small detail with outsized impact on list quality.

For example, if you're mailing to a corporate domain like example.gov, it’s likely IPv6-only. A tool that ignores that fact will fail silently and flag the address as invalid. But MailTester recognizes the preference and verifies accordingly. This means fewer false positives, more accurate deliverability estimates, and better long-term sender health.

Let’s be honest: most email verification tools still default to IPv4. That’s a legacy holdover. But modern deliverability demands you test on the right network. If you’re seeing inconsistent bounces or low inbox placement despite clean lists, checking your verification stack is an often-overlooked first step. MailTester’s smart IP routing handles that for you—no extra effort, just better results.

See how it works in action: verify a bulk list and get a detailed report that shows whether each address was tested on IPv4, IPv6, or both. Or integrate with your workflow via the real-time API for immediate validation. The accuracy of your list depends not just on the address, but on how you test it—every time.

Real-Time API vs. Bulk Verification: When to Use Each

You should use the Real-Time API for verifying emails during signups, account creation, or deduplication as users enter data—enabling instant validation before storage. Use bulk verification for cleaning large email lists prior to campaigns, importing into marketing tools, or auditing compliance, where speed and consistency across thousands of addresses matter. Both methods rely on the same underlying DNS logic to select IPv4 or IPv6 based on the domain’s actual response, ensuring consistency at scale.

When to Use the Real-Time API

• Integrate the email verification API directly into your signup forms or user onboarding flows to catch invalid or disposable emails before they enter your database.
• Use it for deduplication in real time—prevent duplicate accounts by verifying an email as it’s submitted, reducing data noise from the start.
• The API returns immediate results using the domain’s current DNS records, including IPv4 or IPv6 preference, based on active MX and A/AAAA record responses.
• Let’s say a user signs up with [email protected]. The API queries the domain’s DNS, checks its response, and selects IPv6 if the AAAA record is present and valid, or falls back to IPv4 if needed—no guessing, no hardcoding.

When to Use Bulk Verification

• Run bulk verification via the bulk email list checker when you’re preparing for a campaign, importing a list into Mailchimp or SendGrid, or checking for compliance with GDPR or CAN-SPAM rules.
• Bulk verification is ideal when you need to clean 5,000+ emails at once—prioritizing accuracy, deliverability, and removal of invalid addresses like catch-alls, role accounts, or disposable ones.
• Each address is evaluated the same way: DNS is queried for MX, A, and AAAA records. The system dynamically selects IPv4 or IPv6 based on actual, current DNS outcomes.
• For example, if a domain responds with both A (IPv4) and AAAA (IPv6) records, the logic assesses both and prioritizes the one more likely to be active—based on observed delivery behavior in historical data, not assumptions.

Both methods use the same IP detection logic: they don’t rely on pre-set rules or default choices. Instead, they observe the domain’s real-time DNS response—meaning your verification is as precise as the domain’s network configuration.

The choice between real-time and bulk isn’t about speed versus depth. It’s about timing, scale, and purpose.

For more than just bounce rates, you can test inbox placement using inbox placement tools—but that’s for later, after you’ve verified the list.

MailTester’s Integrations Keep Verification Consistent Across Tools

When you verify email lists in Mailchimp, HubSpot, Klaviyo, or SendGrid, MailTester runs IPv4/IPv6 detection at the network level before returning results—no extra steps, no inconsistent filters. The integration pulls email addresses directly from your platform, applies real-time validation including protocol support checks, and returns clean data tagged or segmented, ready to use.

Seamless Validation Where You Work

Let’s say you run a campaign in HubSpot and want to ensure your list won’t trigger bounces. You trigger MailTester through the integration, and it checks each address—validating syntax, domain reachability, and whether the receiving server supports IPv4 or IPv6. These checks happen automatically, so you never need to manually clean your list in multiple tools.

The result is consistent, accurate data. IPv4 or IPv6 support matters: some older servers only accept IPv4; others may reject IPv6-only connections. MailTester detects this early, so your campaign avoids delays or failed deliveries from outdated routing. This isn’t a guess—it’s based on actual SMTP handshake behavior under real network conditions.

Results Are Actionable From Day One

After verification, MailTester returns results as tags, custom fields, or segments directly in your platform. No need to export, clean, and re-import. If something fails, you know it's invalid, a catch-all, or at risk—each status is clearly defined. This prevents wasting sends on known dead ends.

For teams managing large volumes, you can automate this flow. Use the MailTester API to verify in batches or integrate into your CRM workflow. Real-time checks keep your list fresh, especially when adding new contacts.

Even if you use multiple providers—say, SendGrid for sends and Klaviyo for segmentation—verifying once through MailTester ensures consistency. Your data stays aligned across teams and platforms.

IPv4 and IPv6 are part of how email infrastructure evolves. A system that ignores protocol support misses real delivery risk. The IETF’s RFC 8314 explains how mail systems must handle both protocols. MailTester accounts for this by testing actual connectivity, not just syntax.

You’re not just verifying addresses—you’re validating that they can receive mail today, under current infrastructure. That’s why MailTester is designed to integrate directly where you work—and stay accurate, regardless of the protocol underpinning the server.

You Don’t Need to Choose: MailTester Does It Automatically

Email verification software should adapt to infrastructure, not the other way around. With MailTester, the system checks DNS records and selects IPv4 or IPv6 automatically—no manual configuration required.

No need to maintain separate preference lists or rules for IPv4 and IPv6. The same logic applies whether you’re verifying 100 addresses or 1 million. Consistency is built into every verification step.

Accuracy isn’t a feature you toggle. It’s the foundation of how verification works: real-time checks, domain-level intelligence, and a process designed to eliminate guesswork.

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)
• Only about one quarter of email senders report spam complaint rates below 0.1% — the best-practice band — leaving three quarters exposed to some degree of deliverability degradation. — Validity 2025 Email Deliverability Benchmark Report (2025)

Keep reading

• Email deliverability testing tools and spam score checkers (complete guide)
• Email Deliverability Risk Analysis for Domains Approaching Expiry
• Fix 5.1.3 Bad Address Syntax Errors with a Proven Email List Hygiene Tool
• Do Email Verification Tools Check for privaterelay.appleid.com Domains?
• How to Use Email Verification Tools to Audit Subdomain Performance Before Termination

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

Frequently asked questions

Does MailTester support IPv6-only email domains?

Yes. MailTester detects AAAA records in DNS and uses IPv6 for validation when A records are missing, ensuring accurate results on IPv6-only domains.

How does MailTester detect if a domain uses IPv4 or IPv6?

It checks the domain's DNS records in real time. If A records exist, it uses IPv4. If only AAAA records exist, it uses IPv6.

Why is IP version selection important for email verification?

Using the wrong IP version causes connection failures that appear as invalid addresses. This leads to false positives and reduces list accuracy.

Can I see which IP version was used during verification?

Yes. The verification result includes details on which IP version (IPv4 or IPv6) was used, based on DNS records.

Does MailTester work with domains that use both IPv4 and IPv6?

Yes. It checks both A and AAAA records and uses the most appropriate version, depending on availability, to ensure reliable delivery.

Is IPv4/IPv6 detection part of the API or only the web app?

It’s available in both the API and web app. The same logic applies to all verification methods.

What’s the difference between catch-all and valid addresses?

Catch-all domains accept all emails, even invalid ones. Valid addresses are confirmed to exist and accept mail with correct protocol.

How accurate is MailTester’s IPv4/IPv6 selection?

It operates based on real DNS records, achieving 98.9% overall accuracy by aligning verification with actual mail server configuration.

Can using the wrong IP version affect sender reputation?

Yes. Repeated failed connections due to IP mismatch may trigger rate limiting or blacklisting, especially on domains with strict SMTP policies.

Do I need to enable anything to use IPv4/IPv6 selection?

No. The feature is always active. MailTester automatically detects and uses the correct IP version based on the domain’s DNS configuration.

Is IP version detection used during inbox placement testing?

Yes. Inbox placement tests use the same validation logic, including correct IP selection, to simulate real-world delivery conditions.

Can I force IPv4 or IPv6 validation?

No. The system uses dynamic detection. Manual override is not available to preserve accuracy and prevent false results.