fexbox.ru
Detected Mail Infrastructure: Enterprise Mail Infrastructure
Primary: mx1.timeweb.ru
Sender spoofing protections unverified
MailVeri Intelligence Assessment for fexbox.ru
Verify an email address at fexbox.ru
Test if a specific recipient mailbox exists and can receive messages without sending any actual email.
Need to clean email lists containing @fexbox.ru?
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 fexbox.ru
Q Is fexbox.ru a disposable email domain?
No. fexbox.ru is a standard corporate email domain powered by Enterprise Mail Infrastructure. It is not an ephemeral or disposable burner service.
Q What mail servers (MX records) handle email for fexbox.ru?
Emails addressed to @fexbox.ru are processed by 2 authoritative mail exchanger(s), including mx1.timeweb.ru (priority 10), mx2.timeweb.ru (priority 10). The mail routing is handled by Enterprise Mail Infrastructure.
Q Does fexbox.ru have SPF and DMARC email security configured?
fexbox.ru has an active SPF record published (v=spf1 include:_spf.timeweb.ru ~all), but no DMARC policy was detected. Outbound messages have baseline authorization, but lack cryptographic enforcement via DMARC.
Q Should signups using @fexbox.ru be allowed or blocked?
No, signups using @fexbox.ru represent genuine corporate or enterprise mailboxes and should be accepted. Verify individual mailbox deliverability via MailVeri to prevent delivery to inactive or full mailboxes.
Q How do I verify if an email address on fexbox.ru exists without sending?
You can verify recipient mailboxes on fexbox.ru 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.