IONOS Mail Email Verification
IONOS, formerly 1&1, is a large European hosting company and registrar with a very heavy presence in Germany, Austria, Spain, France and the United Kingdom. Like most registrars it bundles mailboxes with hosting and domain packages, so a huge number of European small businesses and tradespeople run their company email on IONOS without ever having made a deliberate choice of email platform. IONOS runs its own mail infrastructure rather than reselling a hyperscaler, and its hosted domains publish IONOS MX records. Because it is a shared hosting platform, catch-all and forwarding configurations are common on IONOS domains, and that has direct consequences for what verification can and cannot prove.
How IONOS Mail Handles Verification
What the MX records tell you
IONOS hosted domains publish MX records pointing at IONOS infrastructure, typically a redundant pair such as mx00.ionos.com and mx01.ionos.com. Because IONOS operates across several European markets and has been through a rebrand from 1&1, you may still encounter older hostname families on long lived domains. Mailthentic matches the IONOS MX signature and identifies the domain as IONOS regardless of which country the customer is in. As always, the MX record is the source of truth: a domain registered at IONOS but pointed at a different mail platform is handled as that platform, not as IONOS.
How IONOS answers an SMTP probe
Verification opens an SMTP session to the IONOS host, sends EHLO, sets a null sender, issues RCPT TO for the address under test, and closes the connection without ever sending DATA. No message is transmitted and nothing appears in anyone's mailbox.
On an IONOS domain configured to reject unknown recipients, a nonexistent mailbox is refused with a 550, and Mailthentic reports that address as invalid. That verdict is dependable. The complication is that IONOS, like every shared hosting platform, makes catch-all and blanket forwarding easy to configure, and a large share of IONOS customer domains have one or the other switched on. On those domains the server returns 250 for any local part you present, whether it belongs to a real mailbox or to nobody at all.
Why catch-all removes certainty
A catch-all domain has instructed its mail server to accept everything rather than reject unknown recipients. Real mail reaches real mailboxes, and everything else lands in a bin or gets forwarded somewhere. From the outside, the server's 250 is identical in both cases, so acceptance carries no information about the specific address you asked about.
Mailthentic tests for this explicitly. Alongside the probe for the address you care about, it sends a probe for a randomly generated local part that could not plausibly exist. If the server accepts that, the domain is catch-all, and the result for your real address is reported as accept-all or ambiguous rather than valid. Mailthentic will not manufacture a confirmation it does not have. No SMTP based verification tool can confirm an individual mailbox on a catch-all domain, and any vendor claiming otherwise is guessing behind a confident label.
Rate limiting and greylisting
IONOS serves an enormous number of domains from shared infrastructure and defends it accordingly. Probing many IONOS domains in quick succession will draw temporary responses in the 421, 450 and 451 range, and some IONOS configurations greylist unfamiliar sources on first contact. These are deferrals, not rejections. Reading them as invalid addresses would silently destroy good contacts, so Mailthentic treats them strictly as temporary, backs off, and retries. Throttling is keyed to the MX host cluster rather than the email domain, which means a list containing hundreds of separate IONOS customer domains is paced as a single target against the shared IONOS servers instead of being fired at them in parallel.
What a result here genuinely means
An invalid verdict on an IONOS domain means the server rejected the recipient and the mailbox does not exist. A valid verdict on an IONOS domain that is not catch-all is real evidence. An accept-all verdict means the domain accepts everything and the address is unproven, which is not a shortcoming of the check but an accurate description of what the server is willing to disclose.
Quick Facts
MX Pattern
mx00.ionos.com
Catch-All Behavior
Accepts all addresses
Typical SMTP Response
250 OK
Provider Type
business
Common Domains
customer domains on IONOS
Best Practices for IONOS Mail
Do not bulk delete accept-all IONOS addresses
A large proportion of IONOS domains belong to legitimate European small businesses whose mailboxes are perfectly real. An accept-all verdict tells you the server would not confirm the mailbox, not that the mailbox is absent. Deleting the whole segment discards good customers. Sending to it blind risks bounces and reputation damage. Segment it, rank it, and treat it as its own risk tier.
Rank the unproven addresses
- Engagement first. Any contact with a recent open, click or reply is worth mailing regardless of the SMTP verdict.
- Source quality. Addresses from your own opt-in forms are far safer than imported, bought or scraped lists.
- Plausible local parts. A person's name on a small company domain is credible. Machine generated looking strings are not.
- Role addresses. On small business domains, generic prefixes such as info or kontakt are extremely common and usually real, but they are shared inboxes that hurt engagement metrics and raise complaint risk in cold campaigns.
Send in controlled stages
Never drop an untested accept-all segment into a full campaign. Send a small batch, then measure that segment's bounce rate and open rate on their own rather than blended into your overall numbers. On a catch-all domain the dead addresses may not bounce at all, because the server quietly absorbs them, so a segment showing few bounces but almost no opens is a segment whose mail is landing in a catch-all bin rather than in front of a person.
Protect deliverability
- Get SPF, DKIM and DMARC in place before mailing shared hosting platforms. Unauthenticated mail is filtered hard.
- Warm new sending IPs and domains gradually. Sudden volume from an unknown source into IONOS infrastructure invites throttling.
- Honour deferrals. A
421or451is an instruction to slow down, and retrying aggressively will hurt your sending reputation. - Remember the audience is largely European. Consent obligations under GDPR are strict, so only mail people who genuinely opted in, and make the unsubscribe immediate and obvious.
Suppress what you can prove
Remove every address Mailthentic marks invalid on an IONOS domain, since those were hard rejected at the server. Suppress anything that bounces on a live send, and re-verify accept-all segments periodically, because small businesses close and their domains stop resolving long before anyone updates your CRM.
Other Email Providers
Verify IONOS Mail email addresses
Our 9-point verification engine handles IONOS Mail's specific behavior automatically. Start free.