Dataweaz

mts.ru

Summary

Registrar
RU-CENTER-RU
Status
REGISTERED
Created on
November 19, 1997
Expires on
November 30, 2026
Name servers
ns1.mts-ws.net, ns3.mts.ru, ns2.mts.ru, ns4.mts-ws.net
Mail servers
mx5.mts.ru, mx6.mts.ru, cm-ural01.ural.mts.ru, cm-ural02.ural.mts.ru
DMARC
Reject

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

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

Policy
Reject
Subdomain policy
Monitoring
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Strict
Aggregate reports
[email protected]
Failure reports
[email protected]

Record

v=DMARC1;p=reject;aspf=s;adkim=r;rua=mailto:[email protected];ruf=mailto:[email protected];fo=1;rf=afrf;ri=86400;sp=none

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

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

RuleValueResult
ip446.243.168.39Allowed
ip4217.66.145.1/30Allowed
ip4213.87.72.33Allowed
ip4213.87.75.66Allowed
ip4213.87.44.124Allowed
ip481.176.66.43Allowed
ip4217.74.241.47Allowed
ip4213.87.44.5/30Allowed
ip4217.8.235.120/30Allowed
ip4195.50.76.237Allowed
mx—Allowed
includesendsay.ruAllowed
all—Rejected

Top-level DNS lookups: 2 of 10 allowed

Record

v=spf1 ip4:46.243.168.39 ip4:217.66.145.1/30 ip4:213.87.72.33 ip4:213.87.75.66 ip4:213.87.44.124 ip4:81.176.66.43 ip4:217.74.241.47 ip4:213.87.44.5/30 ip4:217.8.235.120/30 ip4:195.50.76.237 mx include:sendsay.ru -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
mailjetMailjetRSA 1024 bits · shortActive
mail—RSA 1024 bits · shortActive

RSA keys shorter than 2048 bits, called short keys, are discouraged: they are easier to break.

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 mts.ru arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from mts.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 @mts.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

mts.ru  MX  10 mx1.mts.ru.
mts.ru  MX  20 mx2.mts.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.mts.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

mts.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.mts.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.mts.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.mts.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.mts.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 mts.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
A178.248.238.27

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.mts-ws.net213.87.16.43
ns3.mts.ru213.87.75.192
ns2.mts.ru213.87.50.254
ns4.mts-ws.net217.8.236.228

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @mts.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
10mx5.mts.ru213.87.44.21
10mx6.mts.ru213.87.44.22
20cm-ural01.ural.mts.ru213.87.75.67
20cm-ural02.ural.mts.ru213.87.72.41

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.mts.ru.

NameContent
mts.ruGjbdkiellFfbhYgfFDSv
mts.ruba91dd02-e7d8-47f3-9676-76de8112a26e
mts.rugoogle-site-verification=fWOKY_9px_LZjgDxdVYZ_OXUsYgCpj1J6XzMnAelZqo
mts.ruKLJDfjklsfl34jtlkdfjgg45klj
mts.rumkpZ5xq2sThSEM3upOh/6Pr0r1R2/nSabTrvYH8+0R5fUhTIderS4ivZppomtAeGdye6eENs9+ypdxyCjrOqrg==
mts.ruwebinar-verification=79c878b62c9cb28855402c398be30b0d
mts.ruZOOM_verify_Wlojpe0tSSq0n29T6GgMpQ
mts.ru202104292142190u67tdyeduc3u003l7x95xsntb0bv83aeshgmekpgnc8lb14ld
mts.ruDbnmfHjhgcFLoGdsryuwQ
mts.ruMS=ms43467869
mts.rumIbh9UPZodWUnptlLnqfVFneBoAoGHGv8fzyHDYnI8U=
mts.ru6ead9346-e2e7-4fa4-98da-6c5d73e0f5eb
mts.ru_globalsign-domain-verification=SI52vlj5wpVibNvjW9xD_0VgqgRm_l9AzrMiFPFEjS
mts.rumailru-verification: c44aa65391fa682f
mts.ruv=spf1 ip4:46.243.168.39 ip4:217.66.145.1/30 ip4:213.87.72.33 ip4:213.87.75.66 ip4:213.87.44.124 ip4:81.176.66.43 ip4:217.74.241.47 ip4:213.87.44.5/30 ip4:217.8.235.120/30 ip4:195.50.76.237 mx include:sendsay.ru -all
mts.ruund32L3KhcRJKvGjLK0gL9SU0BPKxGOdXxtJ1x3z8Ak=
mts.rumailru-verification: 7fb6738987ee0e7a
mts.ruMS=C7D0A543E03A08D26EBF537A6E27FE820F7AB9AE
mts.rufacebook-domain-verification=sem5svog8e5zddr0j5e1uw0hinma1i
mts.ruwebinar-verification=0e53f0798639e0d405c9ce1b6bcecd13
mts.ruzsdfkj4jhSDGJKw4t
mts.rumailru-verification: d526dfcb0a0af6a7
mts.ru6165a00d-4dff-4df5-b2ca-738e8ac60c2c
mts.ru_globalsign-domain-verification=dR34BgbhRHgO0Sk-TScY7bVwJq47NMFcbd0CXYHBqy
mts.rugoogle-site-verification=wEwPVAaqeUptq4dvW-FF5DXZri8gR2VCtxfVLax-tdY=
mts.ru_globalsign-domain-verification=afE6J6Ymg5Ho8Sas5xkRwFqwPVyjCpoqdz9DOoGQib
mts.rucisco-ci-domain-verification=4aa9e8cafe1a46c1794f5d07aa7db0b06327276ea015bf0c86877b19d2ac24eb
mts.ruxdgkjreKJDLKJVrhskdjfs3rwrshGS
mts.rudkl4KASDFk32kdsg43fserggaFSdg
mts.ruyandex-verification=5cbea4d997a7df1b
_dmarc.mts.ruv=DMARC1;p=reject;aspf=s;adkim=r;rua=mailto:[email protected];ruf=mailto:[email protected];fo=1;rf=afrf;ri=86400;sp=none
mailjet._domainkey.mts.ruk=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC/0Z/mWsPMo5KnXLtjlScPeleUllz4gKvC1oUWmlwahCiCjWEBZbVPbJ36Ck6ZZDVdL5QPpaMmMGqPTQPnUPmgIh86Rbr1huz4UFF8IdUqQjyazROxwwiklIuKsPqwLOL0AkGd+wvKiUalgCDk6a4o8Bf+ts7UsF4gAz+o7Pw4UwIDAQAB
mail._domainkey.mts.ruv=DKIM1; g=*; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC/ucNs/u2NfGIvku5A7aPeLXvr+NPMcwStkwO0EK7eiDoe99PTMkGEy9qKdjRMrL698RzCx7n/xv8vLxFek9/bLK90D9RijnsMIdEABT/ujn01fiXXJiS6bGZ48OLh68A5tZp1IuHRp70voVs/iZJCNw9PHpC4g1klEbk6bADMKwIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
178.248.238.27Website178.248.238.0/24
213.87.16.43Name server ns1.mts-ws.net213.87.16.0/24
213.87.75.192Name server ns3.mts.ru213.87.75.0/24
213.87.50.254Name server ns2.mts.ru213.87.50.0/24
217.8.236.228Name server ns4.mts-ws.net217.8.236.0/24
213.87.44.21Mail server mx5.mts.ru213.87.44.0/24
213.87.44.22Mail server mx6.mts.ru213.87.44.0/24
213.87.75.67Mail server cm-ural01.ural.mts.ru213.87.75.0/24
213.87.72.41Mail server cm-ural02.ural.mts.ru213.87.72.0/24
46.243.168.39Authorized by SPF46.243.168.0/24
213.87.72.33Authorized by SPF213.87.72.0/24
213.87.75.66Authorized by SPF213.87.75.0/24
213.87.44.124Authorized by SPF213.87.44.0/24
81.176.66.43Authorized by SPF81.176.66.0/24
217.74.241.47Authorized by SPF217.74.241.0/24
195.50.76.237Authorized by SPF195.50.76.0/24

WHOIS of the domain mts.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:        MTS.RU
nserver:       ns1.mts-ws.net.
nserver:       ns2.mts.ru. 213.87.50.254
nserver:       ns3.mts.ru. 213.87.75.192
nserver:       ns4.mts-ws.net.
state:         REGISTERED, DELEGATED, VERIFIED
org:           
taxpayer-id:   
registrar:     RU-CENTER-RU
admin-contact: https://www.nic.ru/whois
created:       1997-11-19T12:02:34Z
paid-till:     2026-11-30T21:00:00Z
free-date:     2027-01-01
source:        TCI

Last updated on 2026-10-02T23:43:02Z

% Query time: 432 msec
% WHEN: Fri Oct 02 23:45:57 UTC 2026