Email infrastructure of chikiriki.ru

According to Live Direct Marketing's daily DNS scan (September 7, 2026), chikiriki.ru (Tranco rank #73,204) points its inbound MX to Self-Hosted and authorizes UniSender in SPF. Its observed DMARC policy is p=reject. Across this dataset, 47% of DMARC publishers use an enforcing policy; this does not show where a specific message landed.

Last updated: .

Mailbox provider (MX)Self-Hosted
ESPs in SPFUniSender
SaaS senders in SPFnone detected
DMARC policyp=reject
DMARC recordv=DMARC1; p=reject; sp=reject
Tranco rank#73,204
Snapshot2026-09-07 (updated daily)

Keep an eye on chikiriki.ru

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 chikiriki.ru 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 Self-Hosted

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.

chikiriki.ru · 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:24:57Z.

Response code: 0.

  • chikiriki.ru · A · TTL 3600 s · 2026-09-07T00:24:57Z · AD=0
    5.188.42.51
chikiriki.ru · AAAA — Unknown: no conclusive answer in this capture

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

chikiriki.ru · NS — Answer records observed

Name servers listed for the DNS zone.

Query observed at: 2026-09-07T00:24:58Z.

Response code: 0.

  • chikiriki.ru · NS · TTL 3600 s · 2026-09-07T00:24:58Z · AD=0
    a.ns.selectel.ru.
  • chikiriki.ru · NS · TTL 3600 s · 2026-09-07T00:24:58Z · AD=0
    b.ns.selectel.ru.
  • chikiriki.ru · NS · TTL 3600 s · 2026-09-07T00:24:58Z · AD=0
    c.ns.selectel.ru.
  • chikiriki.ru · NS · TTL 3600 s · 2026-09-07T00:24:58Z · AD=0
    d.ns.selectel.ru.
chikiriki.ru · MX — Answer records observed

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

Query observed at: 2026-09-07T00:24:58Z.

Response code: 0.

  • chikiriki.ru · MX · TTL 3600 s · 2026-09-07T00:24:58Z · AD=0
    10 mail.chikiriki.ru.
chikiriki.ru · 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:24:57Z.

Response code: 0.

  • chikiriki.ru · SOA · TTL 3600 s · 2026-09-07T00:24:57Z · AD=0
    expire=604800; minimum=60; mname=a.ns.selectel.ru.; refresh=10800; retry=3600; rname=support.selectel.ru.; serial=2026052707
chikiriki.ru · CAA — Unknown: no conclusive answer in this capture

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

chikiriki.ru · TXT — Answer records observed

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

Query observed at: 2026-09-07T00:24:58Z.

Response code: 0.

  • Other TXT data; its purpose is not established by this measurement.

    Raw TXT valuechikiriki.ru · TXT · TTL 3600 s · 2026-09-07T00:24:58Z · AD=0
    "8dbf8a29-53ae-431b-8679-6f4877443e4a"
  • Domain-control verification for Google; not proof of active SaaS or mail use.

    Raw TXT valuechikiriki.ru · TXT · TTL 3600 s · 2026-09-07T00:24:58Z · AD=0
    "google-site-verification=paYY6SW6Jfipupvlay4r_fqQ8StSlCXGBBlL_BdfDkI"
  • Other TXT data; its purpose is not established by this measurement.

    Raw TXT valuechikiriki.ru · TXT · TTL 3600 s · 2026-09-07T00:24:58Z · AD=0
    "unione-validate-hash=e8c8e35b7d8febce40068d467b80be92"
  • SPF: authorized mail senders; not proof that mail was sent.

    Raw TXT valuechikiriki.ru · TXT · TTL 3600 s · 2026-09-07T00:24:58Z · AD=0
    "v=spf1 ip4:178.132.205.162 ip4:193.22.242.87 include:_spf.google.com include:spf.unisender.ru include:spf.mail.selcloud.ru ~all"
chikiriki.ru · DNSKEY — Unknown: no conclusive answer in this capture

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

chikiriki.ru · DS — Unknown: no conclusive answer in this capture

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

chikiriki.ru · CDS — Unknown: no conclusive answer in this capture

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

chikiriki.ru · CDNSKEY — Unknown: no conclusive answer in this capture

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

www.chikiriki.ru · 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:24:58Z.

Response code: 0.

  • www.chikiriki.ru · A · TTL 3600 s · 2026-09-07T00:24:58Z · AD=0
    5.188.42.51
www.chikiriki.ru · AAAA — Unknown: no conclusive answer in this capture

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

_dmarc.chikiriki.ru · TXT — Answer records observed

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

Query observed at: 2026-09-07T00:24:58Z.

Response code: 0.

  • DMARC: published handling and reporting policy for authentication failures.

    Raw TXT value_dmarc.chikiriki.ru · TXT · TTL 3600 s · 2026-09-07T00:24:58Z · AD=0
    "v=DMARC1; p=reject; sp=reject"

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.

_dmarc.chikiriki.ru · TXT

2026-09-07 — Answer records observed

  • DMARC: published handling and reporting policy for authentication failures.

    Raw TXT value_dmarc.chikiriki.ru · TXT
    "v=DMARC1; p=reject; sp=reject"

chikiriki.ru · A

2026-09-07 — Answer records observed

  • chikiriki.ru · A
    5.188.42.51

chikiriki.ru · MX

2026-09-07 — Answer records observed

  • chikiriki.ru · MX
    10 mail.chikiriki.ru

chikiriki.ru · NS

2026-09-07 — Answer records observed

  • chikiriki.ru · NS
    a.ns.selectel.ru
  • chikiriki.ru · NS
    b.ns.selectel.ru
  • chikiriki.ru · NS
    c.ns.selectel.ru
  • chikiriki.ru · NS
    d.ns.selectel.ru

chikiriki.ru · SOA

2026-09-07 — Answer records observed

  • chikiriki.ru · SOA
    expire=604800; minimum=60; mname=a.ns.selectel.ru; refresh=10800; retry=3600; rname=support.selectel.ru; serial=2026052707

chikiriki.ru · TXT

2026-09-07 — Answer records observed

  • Other TXT data; its purpose is not established by this measurement.

    Raw TXT valuechikiriki.ru · TXT
    "8dbf8a29-53ae-431b-8679-6f4877443e4a"
  • Domain-control verification for Google; not proof of active SaaS or mail use.

    Raw TXT valuechikiriki.ru · TXT
    "google-site-verification=paYY6SW6Jfipupvlay4r_fqQ8StSlCXGBBlL_BdfDkI"
  • Other TXT data; its purpose is not established by this measurement.

    Raw TXT valuechikiriki.ru · TXT
    "unione-validate-hash=e8c8e35b7d8febce40068d467b80be92"
  • SPF: authorized mail senders; not proof that mail was sent.

    Raw TXT valuechikiriki.ru · TXT
    "v=spf1 ip4:178.132.205.162 ip4:193.22.242.87 include:_spf.google.com include:spf.unisender.ru include:spf.mail.selcloud.ru ~all"

www.chikiriki.ru · A

2026-09-07 — Answer records observed

  • www.chikiriki.ru · A
    5.188.42.51

Changes to chikiriki.ru

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.

3DNS-dependent terms — nested dependencies are not checked; headroom is not confirmed
~allsoft fail — the common conservative default
127 Brecord length · mixed 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.

mail.chikiriki.ru

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

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

Observed IPObserved PTR namesDNS observation
178.132.205.162mail.chikiriki.ruPTR observed

Observed PTR names belong to this domain or its subdomains. Name relationships are not a forward-confirmed reverse DNS test.

Where chikiriki.ru stands

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

Context of .ru

Most used sending platforms among 5,269 SPF-publishing domains in Russia: Unisender (RU) 47.9% · Mailgun 5.1% · Amazon SES 4.4% · Mailchimp 2.9%. chikiriki.ru runs a stack that is not among the most common in this zone.

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

Frequently asked questions

What email provider does chikiriki.ru use?

chikiriki.ru uses Self-Hosted 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 chikiriki.ru use?

chikiriki.ru authorises UniSender in its SPF record as of September 7, 2026.

Does chikiriki.ru enforce DMARC?

Yes — chikiriki.ru publishes p=reject, the strictest DMARC policy (as of September 7, 2026).

Related domain statistics

Nearby domains in the Tranco ranking: wahooligan.com · utbm.fr · ping-t.com · netoxygen.ch

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.