← Look up another domain · Domain statistics hub

Email infrastructure of intercontinentalnet.org

According to Live Direct Marketing's daily DNS scan (July 30, 2026), intercontinentalnet.org (Tranco rank #298,221) receives mail via Cloudflare Email Routing and sends through Cloudflare Email Routing. The dataset currently contains no DMARC record for this snapshot. That is an authentication observation, not an inbox-placement result.

Last updated: .

Mailbox provider (MX)Cloudflare Email Routing
ESPs in SPFCloudflare Email Routing
SaaS senders in SPFnone detected
DMARC policyno record
Tranco rank#298,221
Snapshot2026-07-30 (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 intercontinentalnet.org and does not prove that a particular message reaches the inbox or spam folder.

Frequently asked questions

What email provider does intercontinentalnet.org use?

intercontinentalnet.org uses Cloudflare Email Routing for inbound mail (detected from its primary MX record) as of July 30, 2026, per Live Direct Marketing's daily Tranco top-1M scan.

What ESP does intercontinentalnet.org use?

intercontinentalnet.org authorises Cloudflare Email Routing in its SPF record as of July 30, 2026.

Does intercontinentalnet.org enforce DMARC?

No — intercontinentalnet.org publishes no DMARC record at all (as of July 30, 2026).

How intercontinentalnet.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 Cloudflare Email Routing

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.

1DNS lookups — 9 left before the limit of 10
~allsoft fail — the common conservative default
42 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

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.

Current PTR coverage · Measurement methodology

Where intercontinentalnet.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: hnuu.edu.cn · dynedge.com · swcorp.org · mhlnews.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