riocom.ru checked at 2025-03-26T02:12:27.617Z 141ms 123/123/123 100% R:12
DNS.NINJA - riocom.ru
Search for IP or hostnames
riocom.ru
MX | mx.yandex.net | ||||||
A | 2a02:6b8::311 🇷🇺 Yandex | ||||||
PTR | mxfront.stable.qloud-b.yandex.net | ||||||
A | 77.88.21.249🇷🇺 Teletech | ||||||
PTR | mxfront.stable.qloud-b.yandex.net | ||||||
NS | ns1.reg.ru | ||||||
A | 2a00:f940:4::47 🇷🇺 AS-REGRU | ||||||
PTR | ns11.reg.ru | ||||||
A | 176.99.13.11🇷🇺 AS-REGRU | ||||||
PTR | ns1.reg.ru | ||||||
A | 176.99.13.13🇷🇺 AS-REGRU | ||||||
PTR | ns1.reg.ru | ||||||
A | 176.99.13.15🇷🇺 AS-REGRU | ||||||
PTR | ns1.reg.ru | ||||||
A | 176.99.13.17🇷🇺 AS-REGRU | ||||||
PTR | ns1.reg.ru | ||||||
A | 194.58.117.11🇷🇺 AS-REGRU | ||||||
PTR | ns1.reg.ru | ||||||
A | 194.58.117.13🇷🇺 AS-REGRU | ||||||
PTR | ns1.reg.ru | ||||||
A | 194.58.117.15🇷🇺 AS-REGRU | ||||||
PTR | ns1.reg.ru | ||||||
A | 194.58.117.17🇷🇺 AS-REGRU | ||||||
PTR | ns1.reg.ru | ||||||
NS | ns2.reg.ru | ||||||
A | 2a00:f940:5::190 🇷🇺 AS-REGRU | ||||||
PTR | ns8.reg.ru | ||||||
A | 176.99.13.12🇷🇺 AS-REGRU | ||||||
PTR | ns2.reg.ru | ||||||
A | 176.99.13.14🇷🇺 AS-REGRU | ||||||
PTR | ns2.reg.ru | ||||||
A | 176.99.13.16🇷🇺 AS-REGRU | ||||||
PTR | ns2.reg.ru | ||||||
A | 176.99.13.18🇷🇺 AS-REGRU | ||||||
PTR | ns2.reg.ru | ||||||
A | 194.58.117.12🇷🇺 AS-REGRU | ||||||
PTR | ns2.reg.ru | ||||||
A | 194.58.117.14🇷🇺 AS-REGRU | ||||||
PTR | ns2.reg.ru | ||||||
A | 194.58.117.16🇷🇺 AS-REGRU | ||||||
PTR | ns2.reg.ru | ||||||
A | 194.58.117.18🇷🇺 AS-REGRU | ||||||
PTR | ns2.reg.ru |
ru
NS | a.dns.ripn.net | ||||||
NS | b.dns.ripn.net | ||||||
NS | d.dns.ripn.net | ||||||
NS | e.dns.ripn.net | ||||||
NS | f.dns.ripn.net |
0 | ||||
0 | ||||
0 | ||||
0 | ||||
0 | ||||
5 | ||||
(lm) | riocom.ru | |||
(lm) | riocom.at | |||
(lm) | riocom.com.br | |||
(lm) | riocom.com | |||
(lm) | riocom.net | |||
50 | ||||
(le) | oricom.de | |||
(le) | roomic.com | |||
(le) | cormio.com | |||
(le) | oricom.tv | |||
(le) | icroom.com | |||
(le) | cormio.com.au | |||
(le) | riocom.ru | |||
(le) | oricom.us | |||
(le) | riocom.at | |||
(le) | morico.ru | |||
(le) | ricmoo.com | |||
(le) | oromic.com | |||
(le) | riocom.com.br | |||
(le) | morico.org | |||
(le) | comori.net | |||
(le) | icorom.com | |||
(le) | omicro.net | |||
(le) | oricom.at | |||
(le) | ricomo.de | |||
(le) | miroco.de | |||
(le) | irmoco.com | |||
(le) | oricom.co.nz | |||
(le) | comori.com | |||
(le) | comoir.com.br | |||
(le) | oricom.co.uk | |||
(le) | riocom.com | |||
(le) | comrio.com.br | |||
(le) | oricom.co | |||
(le) | imcoro.com | |||
(le) | oricom.com.au | |||
(le) | oricom.net | |||
(le) | oricom.ca | |||
(le) | icmoro.edu.it | |||
(le) | oricom.com | |||
(le) | roomic.de | |||
(le) | comori.org | |||
(le) | microo.com | |||
(le) | oricom.org | |||
(le) | comoir.com | |||
(le) | riocom.net | |||
(le) | miroco.eu | |||
(le) | coromi.com | |||
(le) | omicro.it | |||
(le) | ocomir.com | |||
(le) | coriom.com | |||
(le) | comior.com | |||
(le) | mooric.com | |||
(le) | cormio.no | |||
(le) | cromio.com | |||
(le) | oricom.mobi |
AI analysis
Two name servers, ns1.reg.ru and ns2.reg.ru, are the delegation for riocom.ru.
The name server setup of riocom.ru is shared with other domains such as medicalsolutions.ru, biolum.ru, rctservice.ru, mirazh-event.ru, and electromafia.ru.
ns1.reg.ru and ns2.reg.ru both point to nine IP numbers each. For ns1.reg.ru, these are: 2a00:f940:4::47, 176.99.13.11, 176.99.13.13, 176.99.13.15, 176.99.13.17, 194.58.117.11, 194.58.117.13, 194.58.117.15, and 194.58.117.17, while for ns2.reg.ru, they are: 2a00:f940:5::190, 176.99.13.12, 176.99.13.14, 176.99.13.16, 176.99.13.18, 194.58.117.12, 194.58.117.14, 194.58.117.16, and 194.58.117.18.
The mail server, mx.yandex.net, manages riocom.ru.
Just like other domains such as formulacity.ru, samtes.ru, zhukovanatallia.ru, viprp.ru, and gatetokorea.ru, riocom.ru also has the same mail server setup.
The mail servers of riocom.ru are at least partially shared with other domains, such as asti-soft.ru, otziv-o-rabote.ru, and citycard.me.
The mail servers mx.yandex.ru are frequently utilized in conjunction.
mx.yandex.net is configured to point to two IP addresses, namely 2a02:6b8::311 and 77.88.21.249.