← Look up another domain · Domain statistics hub
According to Live Direct Marketing's daily DNS scan (July 25, 2026), teleproxy.ru (Tranco rank #81,655) receives mail via Yandex 360 and sends through SMTP.BZ. The dataset currently contains no DMARC record for this snapshot. That is an authentication observation, not an inbox-placement result.
Last updated: .
| Mailbox provider (MX) | Yandex 360 |
|---|---|
| ESPs in SPF | SMTP.BZ |
| SaaS senders in SPF | none detected |
| DMARC policy | no record |
| Tranco rank | #81,655 |
| Snapshot | 2026-07-25 (updated daily) |
MX identifies the observed inbound mailbox or gateway. SPF includes identify services authorised to send for the domain. DMARC shows the published authentication policy. The dataset currently contains 2 populated signal groups for this page.
Observed deliverability context: based on the available observations, this page describes DNS configuration only. It does not represent a complete audit of teleproxy.ru and does not prove that a particular message reaches the inbox or spam folder.
teleproxy.ru uses Yandex 360 for inbound mail (detected from its primary MX record) as of July 25, 2026, per Live Direct Marketing's daily Tranco top-1M scan.
teleproxy.ru authorises SMTP.BZ in its SPF record as of July 25, 2026.
No — teleproxy.ru publishes no DMARC record at all (as of July 25, 2026).
Same daily dataset, three views: how its mailbox provider is trending, how strict DMARC is at its position in the list, and where its own policy sits among all DMARC publishers in the dataset.
The two ways an SPF record silently stops working. Counted from the published record; include chains are resolved one level deep, so the lookup count is a lower bound.
Adoption of the records that go beyond SPF and DMARC. Shown for the whole snapshot — per-domain detail lives on the security posture report.
The MX hostname resolved to its addresses, and those addresses resolved back. Missing or mismatched reverse DNS is one of the few DNS-visible causes of outright rejection.
mx.yandex.net has a PTR record matching its own zone.2a02:6b8::311 also hosts 1 other mail hosts — a shared server, so reputation is shared too.The same snapshot cut by zone, by list position and by how alive the published policies are.
Most used sending platforms among 5,316 SPF-publishing domains in Russia: Unisender (RU) 48.0% · SendPulse 12.0% · Mailgun 5.2% · Amazon SES 4.5%. teleproxy.ru runs a stack that is not among the most common in this zone.
Nearby domains in the Tranco ranking: propertypreswizard.com · celo.org · threadsdownloader.com · interfree.it
Browse provider data · Compare historical periods · Run an inbox placement test