← Look up another domain · Domain statistics hub

Email infrastructure of meitetsu.co.jp

According to Live Direct Marketing's daily DNS scan (July 25, 2026), meitetsu.co.jp (Tranco rank #98,406) receives mail via Unknown / Other and sends through Salesforce. Its observed DMARC policy is p=none (monitoring). Policy alone does not establish inbox or spam placement.

Last updated: .

Mailbox provider (MX)Unknown / Other
ESPs in SPFSalesforce
SaaS senders in SPFnone detected
DMARC policyp=none
DMARC recordv=DMARC1; p=none; rua=mailto:zashi@meitetsucom.co.jp
Tranco rank#98,406
Snapshot2026-07-25 (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 meitetsu.co.jp and does not prove that a particular message reaches the inbox or spam folder.

Frequently asked questions

What email provider does meitetsu.co.jp use?

meitetsu.co.jp uses Unknown / Other for inbound mail (detected from its primary MX record) as of July 25, 2026, per Live Direct Marketing's daily Tranco top-1M scan.

What ESP does meitetsu.co.jp use?

meitetsu.co.jp authorises Salesforce in its SPF record as of July 25, 2026.

Does meitetsu.co.jp enforce DMARC?

No — meitetsu.co.jp publishes p=none, which only monitors and does not block spoofing (as of July 25, 2026).

How meitetsu.co.jp 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 Unknown / Other

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.

2DNS lookups — 8 left before the limit of 10
~allsoft fail — the common conservative default
93 Brecord length · mixed mechanisms

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.

0.00%publish MTA-STS
0.00%publish TLS-RPT
0.00%publish BIMI

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.

Where meitetsu.co.jp stands

The same snapshot cut by zone, by list position and by how alive the published policies are.

Context of .jp

Most used sending platforms among 5,396 SPF-publishing domains in Japan: Amazon SES 25.3% · Salesforce 8.7% · Zendesk 5.7% · SendGrid (Twilio) 5.7%. meitetsu.co.jp runs a stack that is typical for this zone.

Related domain statistics

Nearby domains in the Tranco ranking: coherent.com · hearthdisplay.com · localmemphis.com · hotala.com

Browse provider data · Compare historical periods · Run an inbox placement test

Your message may perform differently. Run a controlled inbox placement test to evaluate your own message, sender and creative.
Test My Email