← Look up another domain · Domain statistics hub

Email infrastructure of fedbar.org

According to Live Direct Marketing's daily DNS scan (July 28, 2026), fedbar.org (Tranco rank #242,556) receives mail via Microsoft 365 and sends through Constant Contact, Informz (Higher Logic). 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)Microsoft 365
ESPs in SPFConstant Contact, Informz (Higher Logic)
SaaS senders in SPFnone detected
DMARC policyp=quarantine
DMARC recordv=DMARC1; p=quarantine; pct=100; rua=mailto:fed.admin@fedbar.org,mailto:dmarc_agg@vali.email; ruf=mailto:fed.admin@fedbar.org; fo=1;
Tranco rank#242,556
Snapshot2026-07-28 (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 fedbar.org and does not prove that a particular message reaches the inbox or spam folder.

Frequently asked questions

What email provider does fedbar.org use?

fedbar.org uses Microsoft 365 for inbound mail (detected from its primary MX record) as of July 28, 2026, per Live Direct Marketing's daily Tranco top-1M scan.

What ESP does fedbar.org use?

fedbar.org authorises Constant Contact, Informz (Higher Logic) in its SPF record as of July 28, 2026.

Does fedbar.org enforce DMARC?

Partially — fedbar.org publishes p=quarantine (as of July 28, 2026).

How fedbar.org 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 Microsoft 365

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.

6DNS lookups — 4 left before the limit of 10
-allhard fail — anything not listed is rejected
217 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 fedbar.org stands

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

Related domain statistics

Nearby domains in the Tranco ranking: asav.org.br · cna.id · kona-ice.com · sonardata.io

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