addy.email
Detected Mail Infrastructure: Email Forwarding Service
Primary: mx00.ionos.com
Enforces domain sender policy
MailVeri Intelligence Assessment for addy.email
Verify an email address at addy.email
Test if a specific recipient mailbox exists and can receive messages without sending any actual email.
Need to clean email lists containing @addy.email?
DNS checks confirm mail server availability, but cannot detect full inboxes, deleted mailboxes, or stealth spam traps. MailVeri verifies recipient mailbox deliverability in real time with 99% accuracy and non-intrusive SMTP handshakes.
Mail Exchanger (MX) Records
Active inbound mail routes resolved from authoritative DNS:
SPF & DMARC Authentication
Sender Policy Framework (SPF):
Domain-based Message Authentication (DMARC):
Frequently Asked Questions about addy.email
Q Is addy.email a disposable email domain?
No. addy.email is a standard forwarding email domain powered by Email Forwarding Service. It is not an ephemeral or disposable burner service.
Q What mail servers (MX records) handle email for addy.email?
Emails addressed to @addy.email are processed by 2 authoritative mail exchanger(s), including mx00.ionos.com (priority 10), mx01.ionos.com (priority 10). The mail routing is handled by Email Forwarding Service.
Q Does addy.email have SPF and DMARC email security configured?
Yes. addy.email has published email authentication records. An SPF record is active (v=spf1 include:_spf-us.ionos.com ~all) and a DMARC policy is in place (v=DMARC1; p=none;), protecting the domain against sender address spoofing.
Q Should signups using @addy.email be allowed or blocked?
Signups from @addy.email originate from a privacy email forwarding service. While authentic, delivery success depends on the forwarding destination. Accept with standard deliverability checks.
Q How do I verify if an email address on addy.email exists without sending?
You can verify recipient mailboxes on addy.email in real time using the MailVeri API. It checks domain deliverability, mailbox existence via low-latency SMTP handshakes (<500ms), and catch-all status without sending actual emails.