Email infrastructure of avtub.so

According to Live Direct Marketing's daily DNS scan (September 7, 2026), avtub.so (Tranco rank #22,185) points its inbound MX to Namecheap Email Forwarding and authorizes Namecheap Forwarding 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)Namecheap Email Forwarding
ESPs in SPFNamecheap Forwarding
SaaS senders in SPFnone detected
DMARC policyno record
Tranco rank#22,185
Snapshot2026-09-07 (updated daily)

Keep an eye on avtub.so

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 →
Monitoring starts only after you explicitly confirm by email. English reports. Stop any time.

How avtub.so 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

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.

avtub.so · 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-07T00:07:53Z.

Response code: 0.

  • avtub.so · A · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    188.114.96.0
  • avtub.so · A · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    188.114.97.0
avtub.so · AAAA — Answer records observed

IPv6 addresses for this name. An address record does not test service availability.

Query observed at: 2026-09-07T00:07:53Z.

Response code: 0.

  • avtub.so · AAAA · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    2a06:98c1:3120::
  • avtub.so · AAAA · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    2a06:98c1:3121::
avtub.so · NS — Answer records observed

Name servers listed for the DNS zone.

Query observed at: 2026-09-07T00:07:53Z.

Response code: 0.

  • avtub.so · NS · TTL 86400 s · 2026-09-07T00:07:53Z · AD=0
    carioca.ns.cloudflare.com.
  • avtub.so · NS · TTL 86400 s · 2026-09-07T00:07:53Z · AD=0
    lamar.ns.cloudflare.com.
avtub.so · MX — Answer records observed

Servers named to receive mail. Lower preference numbers are tried first.

Query observed at: 2026-09-07T00:07:53Z.

Response code: 0.

  • avtub.so · MX · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    10 eforward1.registrar-servers.com.
  • avtub.so · MX · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    10 eforward2.registrar-servers.com.
  • avtub.so · MX · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    10 eforward3.registrar-servers.com.
  • avtub.so · MX · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    15 eforward4.registrar-servers.com.
  • avtub.so · MX · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    20 eforward5.registrar-servers.com.
avtub.so · SOA — Answer records observed

Zone administration data. The serial is a version number, not a creation date or clock.

Query observed at: 2026-09-07T00:07:53Z.

Response code: 0.

  • avtub.so · SOA · TTL 1800 s · 2026-09-07T00:07:53Z · AD=0
    expire=604800; minimum=1800; mname=carioca.ns.cloudflare.com.; refresh=10000; retry=2400; rname=dns.cloudflare.com.; serial=2412010171
avtub.so · CAA — Unknown: no conclusive answer in this capture

Rules for certificate issuance. These do not show whether an existing certificate is valid.

avtub.so · TXT — Answer records observed

Text records can publish mail policies, domain-control challenges or other data.

Query observed at: 2026-09-07T00:07:53Z.

Response code: 0.

  • SPF: authorized mail senders; not proof that mail was sent.

    Raw TXT valueavtub.so · TXT · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    "v=spf1 include:spf.efwd.registrar-servers.com ~all"
avtub.so · DNSKEY — Unknown: no conclusive answer in this capture

DNSSEC key, signature or denial-of-existence data observed in this response.

avtub.so · DS — Unknown: no conclusive answer in this capture

DNSSEC key, signature or denial-of-existence data observed in this response.

avtub.so · CDS — Unknown: no conclusive answer in this capture

DNSSEC key, signature or denial-of-existence data observed in this response.

avtub.so · CDNSKEY — Unknown: no conclusive answer in this capture

DNSSEC key, signature or denial-of-existence data observed in this response.

www.avtub.so · 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-07T00:07:53Z.

Response code: 0.

  • www.avtub.so · A · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    188.114.96.0
  • www.avtub.so · A · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    188.114.97.0
www.avtub.so · AAAA — Answer records observed

IPv6 addresses for this name. An address record does not test service availability.

Query observed at: 2026-09-07T00:07:53Z.

Response code: 0.

  • www.avtub.so · AAAA · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    2a06:98c1:3120::
  • www.avtub.so · AAAA · TTL 300 s · 2026-09-07T00:07:53Z · AD=0
    2a06:98c1:3121::
_dmarc.avtub.so · 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.

avtub.so · A

2026-09-07 — Answer records observed

  • avtub.so · A
    188.114.96.0
  • avtub.so · A
    188.114.97.0

avtub.so · AAAA

2026-09-07 — Answer records observed

  • avtub.so · AAAA
    2a06:98c1:3120::
  • avtub.so · AAAA
    2a06:98c1:3121::

avtub.so · MX

2026-09-07 — Answer records observed

  • avtub.so · MX
    10 eforward1.registrar-servers.com
  • avtub.so · MX
    10 eforward2.registrar-servers.com
  • avtub.so · MX
    10 eforward3.registrar-servers.com
  • avtub.so · MX
    15 eforward4.registrar-servers.com
  • avtub.so · MX
    20 eforward5.registrar-servers.com

avtub.so · NS

2026-09-07 — Answer records observed

  • avtub.so · NS
    carioca.ns.cloudflare.com
  • avtub.so · NS
    lamar.ns.cloudflare.com

avtub.so · SOA

2026-09-07 — Answer records observed

  • avtub.so · SOA
    expire=604800; minimum=1800; mname=carioca.ns.cloudflare.com; refresh=10000; retry=2400; rname=dns.cloudflare.com; serial=2412010171

avtub.so · TXT

2026-09-07 — Answer records observed

  • SPF: authorized mail senders; not proof that mail was sent.

    Raw TXT valueavtub.so · TXT
    "v=spf1 include:spf.efwd.registrar-servers.com ~all"

www.avtub.so · A

2026-09-07 — Answer records observed

  • www.avtub.so · A
    188.114.96.0
  • www.avtub.so · A
    188.114.97.0

www.avtub.so · AAAA

2026-09-07 — Answer records observed

  • www.avtub.so · AAAA
    2a06:98c1:3120::
  • www.avtub.so · AAAA
    2a06:98c1:3121::

Changes to avtub.so

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.

1DNS-dependent terms — nested dependencies are not checked; headroom is not confirmed
~allsoft fail — the common conservative default
50 Brecord length · includes-only mechanisms

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.

MTA-STSNot measured in this dataset
TLS-RPTNot measured in this dataset
BIMINot measured in this dataset

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.

eforward1.registrar-servers.com

PTR records were observed for all returned addresses of this MX.

DNS attempt: 2026-09-07 05:30:17 UTC. 1 of 1 addresses queried; 1 definite address results in the saved observation.

Observed IPObserved PTR namesDNS observation
162.255.118.51eforward1.registrar-servers.comPTR observed

Observed PTR names are outside this domain. Name relationships are not a forward-confirmed reverse DNS test.

The observed IP 162.255.118.51 is also associated with 3 other MX hostnames. Outbound use and reputation were not measured.

eforward2.registrar-servers.com

PTR records were observed for all returned addresses of this MX.

DNS attempt: 2026-09-07 05:30:17 UTC. 1 of 1 addresses queried; 1 definite address results in the saved observation.

Observed IPObserved PTR namesDNS observation
162.255.118.52eforward2.registrar-servers.comPTR observed

Observed PTR names are outside this domain. Name relationships are not a forward-confirmed reverse DNS test.

The observed IP 162.255.118.52 is also associated with 2 other MX hostnames. Outbound use and reputation were not measured.

eforward3.registrar-servers.com

PTR records were observed for all returned addresses of this MX.

DNS attempt: 2026-09-07 05:30:17 UTC. 1 of 1 addresses queried; 1 definite address results in the saved observation.

Observed IPObserved PTR namesDNS observation
162.255.118.51eforward3.registrar-servers.comPTR observed

Observed PTR names are outside this domain. Name relationships are not a forward-confirmed reverse DNS test.

The observed IP 162.255.118.51 is also associated with 3 other MX hostnames. Outbound use and reputation were not measured.

eforward4.registrar-servers.com

PTR records were observed for all returned addresses of this MX.

DNS attempt: 2026-09-07 05:30:17 UTC. 1 of 1 addresses queried; 1 definite address results in the saved observation.

Observed IPObserved PTR namesDNS observation
162.255.118.52eforward2.registrar-servers.comPTR observed

Observed PTR names are outside this domain. Name relationships are not a forward-confirmed reverse DNS test.

The observed IP 162.255.118.52 is also associated with 2 other MX hostnames. Outbound use and reputation were not measured.

eforward5.registrar-servers.com

PTR records were observed for all returned addresses of this MX.

DNS attempt: 2026-09-07 05:30:17 UTC. 1 of 1 addresses queried; 1 definite address results in the saved observation.

Observed IPObserved PTR namesDNS observation
162.255.118.51eforward3.registrar-servers.comPTR observed

Observed PTR names are outside this domain. Name relationships are not a forward-confirmed reverse DNS test.

The observed IP 162.255.118.51 is also associated with 3 other MX hostnames. Outbound use and reputation were not measured.

Where avtub.so stands

The same snapshot cut by zone, by list position and by how alive the published policies are.

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 avtub.so and does not prove that a particular message reaches the inbox or spam folder.

Frequently asked questions

What email provider does avtub.so use?

avtub.so uses Namecheap Email Forwarding 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 avtub.so use?

avtub.so authorises Namecheap Forwarding in its SPF record as of September 7, 2026.

Does avtub.so enforce DMARC?

No — avtub.so publishes no DMARC record at all (as of September 7, 2026).

Related domain statistics

Nearby domains in the Tranco ranking: memrise.com · nai.com · kenya-airways.com · 211.ru

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

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.