Dataweaz

step.ru

Summary

Registrar
RU-CENTER-RU
Status
REGISTERED
Created on
September 1, 1997
Expires on
September 30, 2027
Name servers
ns1.step.ru, ns2.step.ru, ns4.step.ru, ns3.step.ru
Mail servers
mx2.step.ru, mx.step.ru
SPF
Soft

Spoofing protection (DMARC)

Quarantine

E-mails spoofing this domain are sent to spam.

DMARC tells mail servers what to do with an e-mail that claims to come from step.ru but fails SPF and DKIM checks.

Policy
Quarantine
Subdomain policy
Quarantine
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Aggregate reports
[email protected]
Failure reports
—

Record

v=DMARC1; p=quarantine; sp=quarantine; fo=1; rua=mailto:[email protected]

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

SPF lists the servers allowed to send e-mails for step.ru.

RuleValueResult
mx—Allowed
afrontend.step.ruAllowed
afrontend2.step.ruAllowed
amx.step.ruAllowed
amx2.step.ruAllowed
ip4195.144.1.6Allowed
ip4194.190.79.6Allowed
ip4195.144.1.28Allowed
ip4194.190.79.28Allowed
includespf.unisender.comAllowed
all—Suspicious

Top-level DNS lookups: 6 of 10 allowed

Record

v=spf1 mx a:frontend.step.ru a:frontend2.step.ru a:mx.step.ru a:mx2.step.ru ip4:195.144.1.6  ip4:194.190.79.6 ip4:195.144.1.28 ip4:194.190.79.28 include:spf.unisender.com ~all

E-mail signing (DKIM)

DKIM keys published by step.ru under the most common selectors. Other keys may exist under selectors specific to each sending service.

SelectorLikely serviceKeyStatus
mail—RSAActive

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to step.ru arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from step.ru was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @step.ru address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

step.ru  MX  10 mx1.step.ru.
step.ru  MX  20 mx2.step.ru.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.step.ru.
Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .
An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

step.ru  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1
Identifies the record as an SPF policy. It must come first.
ip4, ip6
Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx
Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include
Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all
Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.step.ru, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.step.ru  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1
Protocol version. Optional but recommended, in which case it must come first.
k
Key algorithm: rsa, the most common, or ed25519.
p
Public key, base64-encoded. An empty value means the key has been revoked.
t
Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.step.ru, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.step.ru  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1
Identifies the record as a DMARC policy. It must come first.
p
Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp
Subdomain policy. Without it, subdomains follow the domain's policy.
rua
Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf
Address that receives detailed failure reports, message by message. Few providers still send them.
pct
Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf
DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of step.ru

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

TypeIP address
A62.109.31.114

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

ServerIP address
ns1.step.ru46.243.174.83
ns2.step.ru45.129.77.42
ns4.step.ru91.217.20.1
ns3.step.ru91.217.21.1

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @step.ru addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

PriorityServerIP address
10mx2.step.ru194.190.79.28
10mx.step.ru195.144.1.28

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.step.ru.

NameContent
step.ruglobalsign-domain-verification=byswFgREI88MIh0xsw2fAYqehA3-OrumswLD6YXhAm
step.ruMS=ms95031567
step.ruwebinar-verification=b286f8ffc95061e567b3fc0f2b38295a
step.ruwebinar-verification=db63256e980f5099f84a835de1af5115
step.ruMS=10AA5DE11546F11448ADDB29C1DAAFCE1EAA1766
step.ruv=spf1 mx a:frontend.step.ru a:frontend2.step.ru a:mx.step.ru a:mx2.step.ru ip4:195.144.1.6 ip4:194.190.79.6 ip4:195.144.1.28 ip4:194.190.79.28 include:spf.unisender.com ~all
step.rucisco-ci-domain-verification=5c88066a4ebb8c0f41b41a7967e3ba138ff9413ba9f7b764e7c5740da652e796
step.ruglobalsign-domain-verification=p-1GYHU9nTop6RjtNjCgxC0z8_LrsgaWQPdb5YvJfr
step.ruglobalsign-domain-verification=wOB4_fXDaSBdsshDiysUb8sG21vq0pL9K8ocIpg53i
step.rumailru-verification: 8c4d6da5910b5139
step.ru0F8zJbIH4bCpF/6H2+BxzJlY3Edvf2KdDUIGqWcOO3T8ayMvs/yvCIlZHpbD/TFRdpf6qmfHlW5ge9TJFKFT+A==
_dmarc.step.ruv=DMARC1; p=quarantine; sp=quarantine; fo=1; rua=mailto:[email protected]
mail._domainkey.step.ruv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArFt3fP9W7dCB+h86FvqNN4zjxO+kaZO9poTfbJEUTBBv88hFpH3G/NoXA9+8SsOQ0AQ4ugDZPGV9xsBd34yGcuszAWa+

Related IP addresses

IPv4 addresses used by step.ru: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
62.109.31.114Website62.109.31.0/24
46.243.174.83Name server ns1.step.ru46.243.174.0/24
45.129.77.42Name server ns2.step.ru45.129.77.0/24
91.217.20.1Name server ns4.step.ru91.217.20.0/24
91.217.21.1Name server ns3.step.ru91.217.21.0/24
194.190.79.28Mail server mx2.step.ru, Authorized by SPF194.190.79.0/24
195.144.1.28Mail server mx.step.ru, Authorized by SPF195.144.1.0/24
195.144.1.6Authorized by SPF195.144.1.0/24
194.190.79.6Authorized by SPF194.190.79.0/24

WHOIS of the domain step.ru

% TCI Whois Service. Terms of use:
% https://tcinet.ru/documents/whois_ru_rf.pdf (in Russian)
% https://tcinet.ru/documents/whois_su.pdf (in Russian)

domain:        STEP.RU
nserver:       ns1.step.ru. 46.243.174.83
nserver:       ns2.step.ru. 45.129.77.42
nserver:       ns3.step.ru. 91.217.21.1
nserver:       ns4.step.ru. 91.217.20.1
state:         REGISTERED, DELEGATED, VERIFIED
org:           
taxpayer-id:   
registrar:     RU-CENTER-RU
admin-contact: https://www.nic.ru/whois
created:       1997-09-01T17:20:30Z
paid-till:     2027-09-30T21:00:00Z
free-date:     2027-11-01
source:        TCI

Last updated on 2026-10-02T12:33:01Z

% Query time: 286 msec
% WHEN: Fri Oct 02 12:37:54 UTC 2026