fexpost.com
Detected Mail Infrastructure: Temporary Disposable Mail Network
Primary: mx.fex.plus
Sender spoofing protections unverified
MailVeri Intelligence Assessment for fexpost.com
Verify an email address at fexpost.com
Test if a specific recipient mailbox exists and can receive messages without sending any actual email.
Need to clean email lists containing @fexpost.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 fexpost.com
Q Is fexpost.com a disposable email domain?
Yes. fexpost.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 fexpost.com?
Emails addressed to @fexpost.com are processed by 1 authoritative mail exchanger(s), including mx.fex.plus (priority 1). The mail routing is handled by Temporary Disposable Mail Network.
Q Does fexpost.com have SPF and DMARC email security configured?
fexpost.com has an active SPF record published (v=spf1 a:mx.fex.plus -all), but no DMARC policy was detected. Outbound messages have baseline authorization, but lack cryptographic enforcement via DMARC.
Q Should signups using @fexpost.com be allowed or blocked?
Yes, signups using @fexpost.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 fexpost.com exists without sending?
You can verify recipient mailboxes on fexpost.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.