rupipe.com - dns.ninja
rupipe.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.nameself.com ⭐ | ||||||
| A | 2a00:15f8:c001:3::144🇷🇺 MASTERHOST-AS2a00:15f8::/32 .masterhost | ||||||
| A | 87.242.73.100🇷🇺 MASTERHOST-AS87.242.73.0/24 | ||||||
| A | 88.212.207.45🇷🇺 UNITEDNET88.212.206.0/23 EXEPTO SERVERS PLANT | ||||||
| NS | ns2.nameself.com | ||||||
| A | 2a02:2100:e001:4::203🇷🇺 UNITEDNET2a02:2100::/32 United Network LLC | ||||||
| A | 88.212.208.183🇷🇺 UNITEDNET88.212.208.0/22 EXEPTO SERVERS PLANT | ||||||
| A | 95.213.146.179🇷🇺 SELECTEL95.213.146.0/24 -NET | ||||||
| MX | mx.yandex.net ⭐ | ||||||
| A | 2a02:6b8::311🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| A | 77.88.21.249🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| TXT | v=spf1 redirect=_spf.yandex.ru | ||||||
| SOA | ns1.nameself.comsupport@regtime.net serial=1779348124 | ||||||
com
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1786347929 | ||||||
Subdomains
1c.rupipe.com |
Same first word
rupipe.com |
Similar names
DNS History
17 records (3 active, 14 former)
○NSns1.activeby.net2015-08-20 → 2017-01-15 · 4 obs
● 2017-01-15 16:13:00
○ 2026-02-16 23:19:42
○ 2026-08-10 08:09:28
●NSns1.nameself.com2026-05-15 → 2026-08-10 · 3 obs
● 2026-05-15 05:08:34
● 2026-08-10 08:09:28
○NSns1.timeweb.ru2026-02-16 → 2026-05-12 · 5 obs
● 2026-02-16 23:19:42
● 2026-05-12 05:36:56
○ 2026-05-15 05:08:34
○ 2026-08-10 08:09:28
○NSns2.activeby.net2015-08-20 → 2017-01-15 · 4 obs
● 2017-01-15 16:13:00
○ 2026-02-16 23:19:42
○ 2026-08-10 08:09:28
●NSns2.nameself.com2026-05-15 → 2026-08-10 · 3 obs
● 2026-05-15 05:08:34
● 2026-08-10 08:09:28
○NSns2.timeweb.ru2026-02-16 → 2026-05-12 · 5 obs
● 2026-02-16 23:19:42
● 2026-05-12 05:36:56
○ 2026-05-15 05:08:34
○ 2026-08-10 08:09:28
○NSns3.activeby.net2015-08-20 → 2017-01-15 · 4 obs
● 2017-01-15 16:13:00
○ 2026-02-16 23:19:42
○ 2026-08-10 08:09:28
○NSns3.timeweb.org2026-02-16 → 2026-05-12 · 5 obs
● 2026-02-16 23:19:42
● 2026-05-12 05:36:56
○ 2026-05-15 05:08:34
○ 2026-08-10 08:09:28
○NSns4.timeweb.org2026-02-16 → 2026-05-12 · 5 obs
● 2026-02-16 23:19:42
● 2026-05-12 05:36:56
○ 2026-05-15 05:08:34
○ 2026-08-10 08:09:28
●MXmx.yandex.net2026-02-16 → 2026-08-10 · 7 obs
● 2026-02-16 23:19:42
● 2026-04-26 10:27:30
○ 2026-04-29 04:29:16
○ 2026-05-12 05:36:56
● 2026-05-15 05:08:34
● 2026-08-10 08:09:28
○MXmx.yandex.ru2015-08-20 → 2017-01-15 · 4 obs
● 2017-01-15 16:13:00
○ 2026-02-16 23:19:42
○ 2026-08-10 08:09:28
○MXmx1.timeweb.ru2026-05-04 → 2026-05-12 · 5 obs
● 2026-05-04 06:14:30
● 2026-05-12 05:36:56
○ 2026-05-15 05:08:34
○ 2026-08-10 08:09:28
○MXmx2.timeweb.ru2026-05-04 → 2026-05-12 · 5 obs
● 2026-05-04 06:14:30
● 2026-05-12 05:36:56
○ 2026-05-15 05:08:34
○ 2026-08-10 08:09:28
○A178.159.250.1702015-08-20 → 2017-01-15 · 4 obs
● 2017-01-15 16:13:00
○ 2026-02-16 23:19:42
○ 2026-08-10 08:09:28
○A2a03:6f00:5:1::59df:78d12026-02-16 → 2026-04-26 · 5 obs
● 2026-02-16 23:19:42
● 2026-04-26 10:27:30
○ 2026-04-29 04:29:16
○ 2026-08-10 08:09:28
○A89.124.92.752026-05-06 → 2026-05-12 · 5 obs
● 2026-05-06 21:40:36
● 2026-05-12 05:36:56
○ 2026-05-15 05:08:34
○ 2026-08-10 08:09:28
○A89.223.120.2092026-02-16 → 2026-04-26 · 5 obs
● 2026-02-16 23:19:42
● 2026-04-26 10:27:30
○ 2026-04-29 04:29:16
○ 2026-08-10 08:09:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | c.gtld-servers.net, d.gtld-servers.net, m.gtld-servers.net, f.gtld-servers.net... | - |
| rupipe.com | ns1.nameself.com, ns2.nameself.com | 6 records |
✅ Authoritative Response
Server:87.242.73.100
NS records: ns1.nameself.com, ns2.nameself.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for rupipe.com (unsigned zone)
⏱️ Timing
Total: 408ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns1.nameself.com, ns2.nameself.com |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 1 | v=spf1 redirect=_spf.yandex.ru |
| SOA | 1 | ns1.nameself.com support.regtime.net |
📌 Glue Records Collected
Total: 6
Out-of-bailiwick: 6 (ns1.nameself.com, ns1.nameself.com, ns1.nameself.com...)
Analysis
Hierarchy
rupipe.com is a parent domain of 1c.rupipe.com.
Name Servers
rupipe.com has two authoritative name servers — ns1.nameself.com and ns2.nameself.com.
rupipe.com shares its NS records with other domains, for example hotelcocos.com, dotrus.domains, pbti.ru and two others.
ns1.nameself.com and ns2.nameself.com each resolve to three IP addresses. ns1.nameself.com resolves to 87.242.73.100, 88.212.207.45 and 2a00:15f8:c001:3::144. ns2.nameself.com resolves to 88.212.208.183, 95.213.146.179 and 2a02:2100:e001:4::203.
Mail Servers
The sole mail server for rupipe.com is mx.yandex.net.
Among the domains sharing a mail server setup with rupipe.com are revskin.co, xn--80aqgbemaiuff.xn--p1ai, tsteam.ru and two others.
The mail servers of rupipe.com overlap at least partially with those of other domains, including aletex.ru, nepeshkom.ru and japanexpert.ru.
mx.yandex.net points to two IP addresses: 77.88.21.249 and 2a02:6b8::311.