← Look up another domain · Domain statistics hub
According to Live Direct Marketing's daily DNS scan (July 25, 2026), lighthouseapp.com (Tranco rank #83,253) receives mail via Unknown / Other and sends through Postmark. 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) | Unknown / Other |
|---|---|
| ESPs in SPF | Postmark |
| SaaS senders in SPF | none detected |
| DMARC policy | p=quarantine |
| DMARC record | v=DMARC1; p=quarantine; adkim=s; aspf=s; |
| Tranco rank | #83,253 |
| Snapshot | 2026-07-25 (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 lighthouseapp.com and does not prove that a particular message reaches the inbox or spam folder.
lighthouseapp.com 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.
lighthouseapp.com authorises Postmark in its SPF record as of July 25, 2026.
Partially — lighthouseapp.com publishes p=quarantine (as of July 25, 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.
astrotrain.entp.com has a PTR pointing to ec2-23-23-91-107.compute-1.amazonaws.com, outside its own zone — normal for cloud providers, a warning sign for a self-run server.The same snapshot cut by zone, by list position and by how alive the published policies are.
Nearby domains in the Tranco ranking: tmprl.cloud · mv1.in · paceap.com · footholds.net
Browse provider data · Compare historical periods · Run an inbox placement test