Email infrastructure of likeboost.net
According to Live Direct Marketing's daily DNS scan (September 7, 2026), likeboost.net (Tranco rank #40,082) points its inbound MX to Cloudflare Email Routing and authorizes Cloudflare Email Routing in SPF. 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 SPF | Cloudflare Email Routing |
| SaaS senders in SPF | none detected |
| DMARC policy | no record |
| Tranco rank | #40,082 |
| Snapshot | 2026-09-07 (updated daily) |
Keep an eye on likeboost.net
Get a first health report, then meaningful changes to SPF, DMARC, MX, sampled MX PTR and blocklists. See your domain history and run a real inbox placement test from your private watchlist.
Manage existing subscriptions →How likeboost.net 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
From observation to a useful check
- What was observed
- The DNS records and classifications in this snapshot.
- What it means
- MX describes inbound mail; SPF authorizes senders.
- What is unknown
- The actual sending IP, nested SPF dependencies, inbox placement and commercial relationships. MTA-STS, TLS-RPT and BIMI adoption are not measured.
- Next check
- Verify current DNS and test a real message: run an inbox placement test.
DNS records
Source: OpenINTEL / Tranco. Capture: 2026-09-07. These are answers from the measurement vantage point, not a live DNS check. TTL is the observed cache lifetime in seconds.
likeboost.net · A — Answer records observed
IPv4 addresses for this name. They do not identify the mail server or prove a hosting migration.
Query observed at: 2026-09-07T01:10:17Z.
Response code: 0.
- likeboost.net · A · TTL 300 s · 2026-09-07T01:10:17Z · AD=0
188.114.96.0 - likeboost.net · A · TTL 300 s · 2026-09-07T01:10:17Z · AD=0
188.114.97.0
likeboost.net · AAAA — Answer records observed
IPv6 addresses for this name. An address record does not test service availability.
Query observed at: 2026-09-07T01:10:17Z.
Response code: 0.
- likeboost.net · AAAA · TTL 300 s · 2026-09-07T01:10:17Z · AD=0
2a06:98c1:3120:: - likeboost.net · AAAA · TTL 300 s · 2026-09-07T01:10:17Z · AD=0
2a06:98c1:3121::
likeboost.net · NS — Answer records observed
Name servers listed for the DNS zone.
Query observed at: 2026-09-07T01:10:17Z.
Response code: 0.
- likeboost.net · NS · TTL 86400 s · 2026-09-07T01:10:17Z · AD=0
aiden.ns.cloudflare.com. - likeboost.net · NS · TTL 86400 s · 2026-09-07T01:10:17Z · AD=0
veronica.ns.cloudflare.com.
likeboost.net · MX — Answer records observed
Servers named to receive mail. Lower preference numbers are tried first.
Query observed at: 2026-09-07T01:10:17Z.
Response code: 0.
- likeboost.net · MX · TTL 300 s · 2026-09-07T01:10:17Z · AD=0
27 route2.mx.cloudflare.net. - likeboost.net · MX · TTL 300 s · 2026-09-07T01:10:17Z · AD=0
34 route1.mx.cloudflare.net. - likeboost.net · MX · TTL 300 s · 2026-09-07T01:10:17Z · AD=0
65 route3.mx.cloudflare.net.
likeboost.net · SOA — Answer records observed
Zone administration data. The serial is a version number, not a creation date or clock.
Query observed at: 2026-09-07T01:10:17Z.
Response code: 0.
- likeboost.net · SOA · TTL 1800 s · 2026-09-07T01:10:17Z · AD=0
expire=604800; minimum=1800; mname=aiden.ns.cloudflare.com.; refresh=10000; retry=2400; rname=dns.cloudflare.com.; serial=2413458143
likeboost.net · CAA — Unknown: no conclusive answer in this capture
Rules for certificate issuance. These do not show whether an existing certificate is valid.
likeboost.net · TXT — Answer records observed
Text records can publish mail policies, domain-control challenges or other data.
Query observed at: 2026-09-07T01:10:17Z.
Response code: 0.
SPF: authorized mail senders; not proof that mail was sent.
Raw TXT value
likeboost.net · TXT · TTL 300 s · 2026-09-07T01:10:17Z · AD=0"v=spf1 include:_spf.mx.cloudflare.net ~all"
likeboost.net · DNSKEY — Unknown: no conclusive answer in this capture
DNSSEC key, signature or denial-of-existence data observed in this response.
likeboost.net · DS — Unknown: no conclusive answer in this capture
DNSSEC key, signature or denial-of-existence data observed in this response.
likeboost.net · CDS — Unknown: no conclusive answer in this capture
DNSSEC key, signature or denial-of-existence data observed in this response.
likeboost.net · CDNSKEY — Unknown: no conclusive answer in this capture
DNSSEC key, signature or denial-of-existence data observed in this response.
www.likeboost.net · A — Answer records observed
IPv4 addresses for this name. They do not identify the mail server or prove a hosting migration.
Query observed at: 2026-09-07T01:10:17Z.
Response code: 0.
- www.likeboost.net · A · TTL 300 s · 2026-09-07T01:10:17Z · AD=0
188.114.96.0 - www.likeboost.net · A · TTL 300 s · 2026-09-07T01:10:17Z · AD=0
188.114.97.0
www.likeboost.net · AAAA — Answer records observed
IPv6 addresses for this name. An address record does not test service availability.
Query observed at: 2026-09-07T01:10:17Z.
Response code: 0.
- www.likeboost.net · AAAA · TTL 300 s · 2026-09-07T01:10:17Z · AD=0
2a06:98c1:3120:: - www.likeboost.net · AAAA · TTL 300 s · 2026-09-07T01:10:17Z · AD=0
2a06:98c1:3121::
_dmarc.likeboost.net · TXT — Unknown: no conclusive answer in this capture
Text records can publish mail policies, domain-control challenges or other data.
DNSSEC records are shown only when returned. An unset AD flag is not proof that a zone is unsigned. MTA-STS, TLS-RPT, BIMI and arbitrary DKIM selectors are not measured here; their absence cannot be inferred.
Recorded DNS history
Registry presence: first seen 2026-04-28; last seen 2026-09-07. These are appearances in our domain registry, not domain registration dates or earlier DNS values.
This history starts with saved RR captures. Provider market-share charts are aggregate context, not this domain’s DNS history. Dates identify observations; no continuous validity between them is implied. Equivalent RR states are combined, ignoring response TTL and capture-time changes. Up to 30 distinct RR states and 60 dated captures are retained within a per-domain byte limit.
No earlier different RR snapshot is available for comparison.
Available saved snapshots
2026-09-07 (equivalent state also recorded on 2026-09-05)
Each query below keeps its own observation date; unknown checks may retain older values.
likeboost.net · A
2026-09-07 — Answer records observed
- likeboost.net · A
188.114.96.0 - likeboost.net · A
188.114.97.0
likeboost.net · AAAA
2026-09-07 — Answer records observed
- likeboost.net · AAAA
2a06:98c1:3120:: - likeboost.net · AAAA
2a06:98c1:3121::
likeboost.net · MX
2026-09-07 — Answer records observed
- likeboost.net · MX
27 route2.mx.cloudflare.net - likeboost.net · MX
34 route1.mx.cloudflare.net - likeboost.net · MX
65 route3.mx.cloudflare.net
likeboost.net · NS
2026-09-07 — Answer records observed
- likeboost.net · NS
aiden.ns.cloudflare.com - likeboost.net · NS
veronica.ns.cloudflare.com
likeboost.net · SOA
2026-09-07 — Answer records observed
- likeboost.net · SOA
expire=604800; minimum=1800; mname=aiden.ns.cloudflare.com; refresh=10000; retry=2400; rname=dns.cloudflare.com; serial=2413458143
likeboost.net · TXT
2026-09-07 — Answer records observed
SPF: authorized mail senders; not proof that mail was sent.
Raw TXT value
likeboost.net · TXT"v=spf1 include:_spf.mx.cloudflare.net ~all"
www.likeboost.net · A
2026-09-07 — Answer records observed
- www.likeboost.net · A
188.114.96.0 - www.likeboost.net · A
188.114.97.0
www.likeboost.net · AAAA
2026-09-07 — Answer records observed
- www.likeboost.net · AAAA
2a06:98c1:3120:: - www.likeboost.net · AAAA
2a06:98c1:3121::
Changes to likeboost.net
No entry for this domain appears in the current public change feed. The feed is a selected sample, so this does not establish that its DNS stayed unchanged.
Start monitoring to build a history from your first check, or explore observed changes across the dataset.
SPF diagnostics
Static observations from the published SPF record. No nested include or redirect dependencies were evaluated. The actual sending IP and evaluation path are needed to assess the RFC 7208 limit of 10 DNS-dependent terms.
Modern mail security across the dataset
The required DNS labels are not queried. Adoption is unknown for this domain and for the population. Apex TXT anomalies are listed separately in the security posture report.
Reverse DNS of inbound MX hosts
These are separately dated observations of inbound MX addresses. They do not identify the actual sending IP. To assess outbound mail, check current forward and reverse DNS of the actual sending IP; FCrDNS and delivery were not measured here.
route2.mx.cloudflare.net
Partial observation: some addresses were not checked or the resolver could not determine their PTR records.
DNS attempt: 2026-09-08 06:00:52 UTC. 3 of 6 addresses queried; 3 definite address results in the saved observation.
| Observed IP | Observed PTR names | DNS observation |
|---|---|---|
162.159.205.17 | route2.mx.cloudflare.net | PTR observed |
162.159.205.18 | route2.mx.cloudflare.net | PTR observed |
162.159.205.19 | route2.mx.cloudflare.net | PTR observed |
2606:4700:f5::10 | — | Not checked (query limit) |
2606:4700:f5::e | — | Not checked (query limit) |
2606:4700:f5::f | — | Not checked (query limit) |
Observed PTR names are outside this domain. Name relationships are not a forward-confirmed reverse DNS test.
The observed IP 162.159.205.17 is also associated with 1 other MX hostnames. Outbound use and reputation were not measured.
route1.mx.cloudflare.net
Partial observation: some addresses were not checked or the resolver could not determine their PTR records.
DNS attempt: 2026-09-08 06:00:52 UTC. 3 of 6 addresses queried; 3 definite address results in the saved observation.
| Observed IP | Observed PTR names | DNS observation |
|---|---|---|
162.159.205.11 | route1.mx.cloudflare.net | PTR observed |
162.159.205.12 | route1.mx.cloudflare.net | PTR observed |
162.159.205.13 | route1.mx.cloudflare.net | PTR observed |
2606:4700:f5::b | — | Not checked (query limit) |
2606:4700:f5::c | — | Not checked (query limit) |
2606:4700:f5::d | — | Not checked (query limit) |
Observed PTR names are outside this domain. Name relationships are not a forward-confirmed reverse DNS test.
The observed IP 162.159.205.11 is also associated with 1 other MX hostnames. Outbound use and reputation were not measured.
route3.mx.cloudflare.net
Partial observation: some addresses were not checked or the resolver could not determine their PTR records.
DNS attempt: 2026-09-08 06:00:52 UTC. 3 of 6 addresses queried; 3 definite address results in the saved observation.
| Observed IP | Observed PTR names | DNS observation |
|---|---|---|
162.159.205.23 | route3.mx.cloudflare.net | PTR observed |
162.159.205.24 | route3.mx.cloudflare.net | PTR observed |
162.159.205.25 | route3.mx.cloudflare.net | PTR observed |
2606:4700:f5::11 | — | Not checked (query limit) |
2606:4700:f5::12 | — | Not checked (query limit) |
2606:4700:f5::13 | — | Not checked (query limit) |
Observed PTR names are outside this domain. Name relationships are not a forward-confirmed reverse DNS test.
The observed IP 162.159.205.23 is also associated with 1 other MX hostnames. Outbound use and reputation were not measured.
Where likeboost.net 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.1% of domains (Google Workspace, Microsoft 365, Unknown / Other).
- Across the dataset 25.1% of DMARC records are inert — policy does nothing and no reports are collected.
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 likeboost.net and does not prove that a particular message reaches the inbox or spam folder.
Frequently asked questions
What email provider does likeboost.net use?
likeboost.net uses Cloudflare Email Routing for inbound mail (detected from its primary MX record) as of September 7, 2026, per Live Direct Marketing's daily Tranco top-1M scan.
What ESP does likeboost.net use?
likeboost.net authorises Cloudflare Email Routing in its SPF record as of September 7, 2026.
Does likeboost.net enforce DMARC?
No — likeboost.net publishes no DMARC record at all (as of September 7, 2026).
Related domain statistics
Nearby domains in the Tranco ranking: magix.com · uhg.com · albourne.com · classiccars.com
Browse provider data · Compare historical periods · Run an inbox placement test
Data: Email infrastructure of the Tranco top-1M, daily snapshot 2026-09-07, derived from OpenINTEL forward-DNS measurements. Cite with the date — records change daily.