na-cat.com
Detected Mail Infrastructure: Temporary Disposable Mail Network
Primary: recv400.erinn.biz
Enforces domain sender policy
MailVeri Intelligence Assessment for na-cat.com
Verify an email address at na-cat.com
Test if a specific recipient mailbox exists and can receive messages without sending any actual email.
Need to clean email lists containing @na-cat.com?
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 na-cat.com
Q Is na-cat.com a disposable email domain?
Yes. na-cat.com is identified as an active temporary or burner email provider. Mailboxes exist for limited durations and are discarded automatically.
Q What mail servers (MX records) handle email for na-cat.com?
Emails addressed to @na-cat.com are processed by 1 authoritative mail exchanger(s), including recv400.erinn.biz (priority 10). The mail routing is handled by Temporary Disposable Mail Network.
Q Does na-cat.com have SPF and DMARC email security configured?
Yes. na-cat.com has published email authentication records. An SPF record is active (v=spf1 +ip4:160.251.104.92 +ip4:160.16.149.19 -all) and a DMARC policy is in place (v=DMARC1; p=reject; pct=100), protecting the domain against sender address spoofing.
Q Should signups using @na-cat.com be allowed or blocked?
Yes, signups using @na-cat.com should be blocked immediately. This domain is classified as an active temporary burner service. Allowing temporary accounts leads to high bounce rates, bot abuse, and spam trap contamination.
Q How do I verify if an email address on na-cat.com exists without sending?
You can verify recipient mailboxes on na-cat.com 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.