← Look up another domain · Domain statistics hub

Email infrastructure of red-dot.org

According to Live Direct Marketing's daily DNS scan (July 25, 2026), red-dot.org (Tranco rank #29,484) receives mail via ISPGateway (DE). The dataset currently contains no DMARC record for this snapshot. That is an authentication observation, not an inbox-placement result.

Last updated: July 25, 2026.

Mailbox provider (MX)	ISPGateway (DE)
ESPs in SPF	none detected
SaaS senders in SPF	none detected
DMARC policy	no record
Tranco rank	#29,484
Snapshot	2026-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 1 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 red-dot.org and does not prove that a particular message reaches the inbox or spam folder.

Frequently asked questions

What email provider does red-dot.org use?

red-dot.org uses ISPGateway (DE) for inbound mail (detected from its primary MX record) as of July 25, 2026, per Live Direct Marketing's daily Tranco top-1M scan.

Does red-dot.org enforce DMARC?

No — red-dot.org publishes no DMARC record at all (as of July 25, 2026).

How red-dot.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 ISPGateway (DE)

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

-allhard fail — anything not listed is rejected

36 Brecord length · includes-only 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.

mxlb.ispgateway.de has a PTR record matching its own zone.
Resolves to 80.67.18.126.
Its address 80.67.18.126 also hosts 3 other mail hosts — a shared server, so reputation is shared too.

Where red-dot.org 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 60.7% of domains (Google Workspace, Microsoft 365, Unknown / Other).
Across the dataset 25.0% of DMARC records are inert — policy does nothing and no reports are collected.
red-dot.org is one of 27,979 domains with a strict -all SPF and a DMARC record that enforces nothing — the sending side is locked down while the policy side is not.

Related domain statistics

Nearby domains in the Tranco ranking: ccavenue.com · hunter.io · hosttech.at · saturn.de

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