← Look up another domain · Domain statistics hub
Email infrastructure of n1.ru
According to Live Direct Marketing's daily DNS scan (August 2, 2026), n1.ru (Tranco rank #45,595) receives mail via Google Workspace and sends through SendGrid (Twilio), Mindbox, Zendesk. Its observed DMARC policy is p=quarantine. 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) | Google Workspace |
|---|---|
| ESPs in SPF | SendGrid (Twilio), Mindbox, Zendesk |
| SaaS senders in SPF | none detected |
| DMARC policy | p=quarantine |
| DMARC record | v=DMARC1; p=quarantine; rua=mailto:service-dmarc@n1.ru |
| Tranco rank | #45,595 |
| Snapshot | 2026-08-02 (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 n1.ru and does not prove that a particular message reaches the inbox or spam folder.
Frequently asked questions
What email provider does n1.ru use?
n1.ru uses Google Workspace for inbound mail (detected from its primary MX record) as of August 2, 2026, per Live Direct Marketing's daily Tranco top-1M scan.
What ESP does n1.ru use?
n1.ru authorises SendGrid (Twilio), Mindbox, Zendesk in its SPF record as of August 2, 2026.
Does n1.ru enforce DMARC?
Partially — n1.ru publishes p=quarantine (as of August 2, 2026).
How n1.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 Google Workspace
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.
aspmx.l.google.comhas a PTR pointing tora-in-f26.1e100.net, outside its own zone — normal for cloud providers, a warning sign for a self-run server.- Resolves to 142.250.27.26, 2a00:1450:4025:401::1a.
- Its address
142.250.27.26also hosts 8 other mail hosts — a shared server, so reputation is shared too.
Where n1.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,364 SPF-publishing domains in Russia: Unisender (RU) 48.1% · SendPulse 11.9% · Mailgun 5.1% · Amazon SES 4.5%. n1.ru runs a stack that is not among the most common in this zone.
Related domain statistics
Nearby domains in the Tranco ranking: wfolio.com · ntop.org · tni.org · grantland.com
Browse provider data · Compare historical periods · Run an inbox placement test