← Look up another domain · Domain statistics hub
Email infrastructure of slant.co
According to Live Direct Marketing's daily DNS scan (August 2, 2026), slant.co (Tranco rank #94,290) receives mail via Google Workspace and sends through Customer.io. Its observed DMARC policy is p=none (monitoring). Policy alone does not establish inbox or spam placement.
Last updated: .
| Mailbox provider (MX) | Google Workspace |
|---|---|
| ESPs in SPF | Customer.io |
| SaaS senders in SPF | none detected |
| DMARC policy | p=none |
| DMARC record | v=DMARC1; p=none; |
| Tranco rank | #94,290 |
| 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 slant.co and does not prove that a particular message reaches the inbox or spam folder.
Frequently asked questions
What email provider does slant.co use?
slant.co 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 slant.co use?
slant.co authorises Customer.io in its SPF record as of August 2, 2026.
Does slant.co enforce DMARC?
No — slant.co publishes p=none, which only monitors and does not block spoofing (as of August 2, 2026).
How slant.co 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 slant.co 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 24.7% of DMARC records are inert — policy does nothing and no reports are collected.
Related domain statistics
Nearby domains in the Tranco ranking: gamblinghelponline.org.au · espublico.com · gameseal.com · ctia.org
Browse provider data · Compare historical periods · Run an inbox placement test