← Look up another domain · Domain statistics hub
Email infrastructure of kosmosapp.ru
According to Live Direct Marketing's daily DNS scan (August 21, 2026), kosmosapp.ru (Tranco rank #45,102) receives mail via Timeweb (RU) and sends through SMTP.BZ. Its observed DMARC policy is p=reject. Across this dataset, 47% of DMARC publishers use an enforcing policy; this does not show where a specific message landed.
Last updated: .
| Mailbox provider (MX) | Timeweb (RU) |
|---|---|
| ESPs in SPF | SMTP.BZ |
| SaaS senders in SPF | none detected |
| DMARC policy | p=reject |
| DMARC record | v=DMARC1; p=reject |
| Tranco rank | #45,102 |
| Snapshot | 2026-08-21 (updated daily) |
How to interpret these observations
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 3 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 kosmosapp.ru and does not prove that a particular message reaches the inbox or spam folder.
Frequently asked questions
What email provider does kosmosapp.ru use?
kosmosapp.ru uses Timeweb (RU) for inbound mail (detected from its primary MX record) as of August 21, 2026, per Live Direct Marketing's daily Tranco top-1M scan.
What ESP does kosmosapp.ru use?
kosmosapp.ru authorises SMTP.BZ in its SPF record as of August 21, 2026.
Does kosmosapp.ru enforce DMARC?
Yes — kosmosapp.ru publishes p=reject, the strictest DMARC policy (as of August 21, 2026).
How kosmosapp.ru compares
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.
Market share of Timeweb (RU)
DMARC enforced by list position
Policy maturity of all DMARC publishers
SPF diagnostics
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.
Modern mail security across the dataset
Adoption of the records that go beyond SPF and DMARC. Shown for the whole snapshot — per-domain detail lives on the security posture report.
Reverse DNS of the mail host
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.
mx1.timeweb.ruhas a PTR record matching its own zone.- Resolves to 2a03:6f00:3::5c35:742f, 92.53.116.47.
Where kosmosapp.ru stands
The same snapshot cut by zone, by list position and by how alive the published policies are.
- At this list position the top three mailbox providers hold 60.7% of domains (Google Workspace, Microsoft 365, Unknown / Other).
- Across the dataset 25.0% of DMARC records are inert — policy does nothing and no reports are collected.
Context of .ru
Most used sending platforms among 5,415 SPF-publishing domains in Russia: Unisender (RU) 48.1% · Mailgun 5.0% · Amazon SES 4.3% · Mailchimp 3.0%. kosmosapp.ru runs a stack that is not among the most common in this zone.
Related domain statistics
Nearby domains in the Tranco ranking: pathe.nl · nps.edu · stratasys.com · invoicesimple.com
Browse provider data · Compare historical periods · Run an inbox placement test