← Look up another domain · Domain statistics hub
According to Live Direct Marketing's daily DNS scan (July 30, 2026), pluym.com (Tranco rank #208,877) receives mail via MTA Routes. Its observed DMARC policy is p=none (monitoring). Policy alone does not establish inbox or spam placement.
Last updated: .
| Mailbox provider (MX) | MTA Routes |
|---|---|
| ESPs in SPF | none detected |
| SaaS senders in SPF | none detected |
| DMARC policy | p=none |
| DMARC record | v=DMARC1;p=none;pct=100; |
| Tranco rank | #208,877 |
| Snapshot | 2026-07-30 (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 pluym.com and does not prove that a particular message reaches the inbox or spam folder.
pluym.com uses MTA Routes for inbound mail (detected from its primary MX record) as of July 30, 2026, per Live Direct Marketing's daily Tranco top-1M scan.
No — pluym.com publishes p=none, which only monitors and does not block spoofing (as of July 30, 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.
No current PTR conclusion is available on this retained page. Its previous PTR summary did not preserve enough dated, per-address evidence to establish a current negative DNS answer or a complete reverse DNS check. This does not mean PTR records are absent.
The page's original snapshot date is unchanged. MX addresses receive mail and do not identify the actual sending IP. For outgoing mail, obtain that IP, query its PTR names, and resolve those names back to A/AAAA. FCrDNS and delivery were not measured here.
The same snapshot cut by zone, by list position and by how alive the published policies are.
-all SPF and a DMARC record that enforces nothing — the sending side is locked down while the policy side is not.Nearby domains in the Tranco ranking: tritius.cz · thembay.com · pub.solar · weblink.com.br
Browse provider data · Compare historical periods · Run an inbox placement test