← Look up another domain · Domain statistics hub
According to Live Direct Marketing's daily DNS scan (July 26, 2026), redshelf.com (Tranco rank #136,781) receives mail via Google Workspace and sends through SendGrid (Twilio), Amazon SES, Mailchimp. 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 | SendGrid (Twilio), Amazon SES, Mailchimp |
| SaaS senders in SPF | none detected |
| DMARC policy | p=none |
| DMARC record | v=DMARC1; p=none; pct=5; rua=mailto:dmarc@redshelf.com |
| Tranco rank | #136,781 |
| Snapshot | 2026-07-26 (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 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 redshelf.com and does not prove that a particular message reaches the inbox or spam folder.
redshelf.com uses Google Workspace for inbound mail (detected from its primary MX record) as of July 26, 2026, per Live Direct Marketing's daily Tranco top-1M scan.
redshelf.com authorises SendGrid (Twilio), Amazon SES, Mailchimp in its SPF record as of July 26, 2026.
No — redshelf.com publishes p=none, which only monitors and does not block spoofing (as of July 26, 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.
aspmx.l.google.com has a PTR pointing to ra-in-f26.1e100.net, outside its own zone — normal for cloud providers, a warning sign for a self-run server.142.250.27.26 also hosts 8 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.
Nearby domains in the Tranco ranking: rnid.org.uk · netoxygen.ch · portbase.com · agendapro.com
Browse provider data · Compare historical periods · Run an inbox placement test