← Look up another domain · Domain statistics hub

Email infrastructure of jellyfish.systems

According to Live Direct Marketing's daily DNS scan (July 25, 2026), jellyfish.systems (Tranco rank #70,489) receives mail via Namecheap Email Forwarding. Its observed DMARC policy is p=none (monitoring). Policy alone does not establish inbox or spam placement.

Last updated: .

Mailbox provider (MX)Namecheap Email Forwarding
ESPs in SPFnone detected
SaaS senders in SPFnone detected
DMARC policyp=none
DMARC recordv=DMARC1; p=none; rua=mailto:ab25c7607b89337@rep.dmarcanalyzer.com; ruf=mailto:ab25c7607b89337@for.dmarcanalyzer.com; fo=1;
Tranco rank#70,489
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 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 jellyfish.systems and does not prove that a particular message reaches the inbox or spam folder.

Frequently asked questions

What email provider does jellyfish.systems use?

jellyfish.systems uses Namecheap Email Forwarding 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 jellyfish.systems enforce DMARC?

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

How jellyfish.systems 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 Namecheap Email Forwarding

DMARC enforced by list position

Policy maturity of all DMARC publishers

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 jellyfish.systems 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: hongkongairlines.com · kap.org.tr · medievalists.net · prepsportswear.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