← Look up another domain · Domain statistics hub
Email infrastructure of openl.io
According to Live Direct Marketing's daily DNS scan (August 31, 2026), openl.io (Tranco rank #133,513) receives mail via Migadu. Its observed DMARC policy is p=reject. 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) | Migadu |
|---|---|
| ESPs in SPF | none detected |
| SaaS senders in SPF | none detected |
| DMARC policy | p=reject |
| DMARC record | v=DMARC1; p=reject; sp=reject; adkim=s; aspf=s; rua=mailto:67336cc02b524f518638195b170aa861@dmarc-reports.cloudflare.net; |
| Tranco rank | #133,513 |
| Snapshot | 2026-08-31 (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 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 openl.io and does not prove that a particular message reaches the inbox or spam folder.
Frequently asked questions
What email provider does openl.io use?
openl.io uses Migadu for inbound mail (detected from its primary MX record) as of August 31, 2026, per Live Direct Marketing's daily Tranco top-1M scan.
Does openl.io enforce DMARC?
Yes — openl.io publishes p=reject, the strictest DMARC policy (as of August 31, 2026).
How openl.io 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.
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.
Historical reverse DNS observation
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.
Where openl.io 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 54.0% of domains (Google Workspace, Microsoft 365, Unknown / Other).
- Across the dataset 25.2% of DMARC records are inert — policy does nothing and no reports are collected.
Related domain statistics
Nearby domains in the Tranco ranking: cloudhosting.co.uk · molport.com · federaltimes.com · sliderrevolution.com
Browse provider data · Compare historical periods · Run an inbox placement test