--- title: "Chroot Jail Explained: What It Is & How to Use It on Linux" description: A chroot jail isolates a process in a restricted directory, hardening your Linux server. Learn what it is, how it works, and how to set one up on your VPS. image: https://blog.ishosting.com/hubfs/blog/what-is-chroot-jail/chroot-jail.png --- [VPS](https://ishosting.com/en/vps) [Dedicated hosting](https://ishosting.com/en/dedicated) [VPN](https://ishosting.com/en/vpn) [Storage](https://ishosting.com/en/storage) [About us](https://ishosting.com/en/about) [Client area](https://my.ishosting.com/en/account) [is\*hosting Blog](https://blog.ishosting.com/en) - [News](https://blog.ishosting.com/en/tag/news) - [VPS](https://blog.ishosting.com/en/tag/vps) - [Hosting](https://blog.ishosting.com/en/tag/hosting) - [Technology](https://blog.ishosting.com/en/tag/technology) - [is\*ai](https://blog.ishosting.com/en/tag/isai) - Other - [Marketing](https://blog.ishosting.com/en/tag/marketing) - [Security](https://blog.ishosting.com/en/tag/security) [News](https://blog.ishosting.com/en/tag/news) Categories [Search](https://blog.ishosting.com/hs-search-results) Hosting Services [About Us](https://ishosting.com/en/about) [Client Area](https://my.ishosting.com/en/account) [News](https://blog.ishosting.com/en/tag/news) [VPS](https://blog.ishosting.com/en/tag/vps) [Hosting](https://blog.ishosting.com/en/tag/hosting) [Technology](https://blog.ishosting.com/en/tag/technology) [is\*ai](https://blog.ishosting.com/en/tag/isai) [Marketing](https://blog.ishosting.com/en/tag/marketing) [Security](https://blog.ishosting.com/en/tag/security) [VPS](https://ishosting.com/en/vps) [Dedicated hosting](https://ishosting.com/en/dedicated) [VPN](https://ishosting.com/en/vpn) [Storage](https://ishosting.com/en/storage) 1. [Blog](https://blog.ishosting.com/en) 2. [How to](https://blog.ishosting.com/en/tag/how-to) 3. Chroot Jail: How to Restrict Access to a Specific Directory How to # Chroot Jail: How to Restrict Access to a Specific Directory A chroot jail isolates a process in a restricted directory, hardening your Linux server. Learn what it is, how it works, and how to set one up on your VPS. [Natasha M.](https://blog.ishosting.com/en/author/natasha-m) 20 Mar 2024 9 min reading ![Chroot Jail: How to Restrict Access to a Specific Directory](https://blog.ishosting.com/hubfs/blog/what-is-chroot-jail/chroot-jail.png) Table of Contents - [What is Chroot Jail and What Is It Used For](https://blog.ishosting.com/en/what-is-chroot-jail#what-is-chroot-jail) - [Chroot Jail Setup](https://blog.ishosting.com/en/what-is-chroot-jail#chroot-jail-setup) - [SFTP Check with Chroot Jail](https://blog.ishosting.com/en/what-is-chroot-jail#sftp-check) - [Additional Security Techniques](https://blog.ishosting.com/en/what-is-chroot-jail#additional-security-techniques) - [Conclusion](https://blog.ishosting.com/en/what-is-chroot-jail#conclusion) When administering a computer system, you sometimes need to create a new environment, separate from the major system, where the user will see only certain files, can create a test environment for programs or scripts, restore the system, or reinstall the bootloader. Creating such an environment called a chroot jail, helps perform certain tasks outside the major system for its security. In our article today, we will learn what a chroot jail is, how and why it is created, and what additional security methods are used. ## What is Chroot Jail and What Is It Used For **Chroot** (derived from the phrase "**change root**") is a command on Unix-like systems that changes the visible root directory to the user-specified one. **Chroot Jail** is placing a user in a fake root directory (jail) intentionally created to give the user access to certain commands and permissions. What are the purposes of using a chroot prison? A chroot jail is used to create a small sandbox to start the process (e.g., testing programs or scripts, recovering the system password, etc.). This means that a process cannot maliciously modify information outside the prescribed directory tree to avoid crashing the entire system. Keep in mind that a chroot jail is neither a replacement for virtual machines nor a full security boundary. chroot only changes the visible root directory of a process: it does not isolate processes, the network, or resource usage, and a process with root privileges inside the jail can break out of it. That is why users in a chroot jail should never get root access. For real isolation, use containers (namespaces and cgroups) or virtual machines. ## Chroot Jail Setup ![Chroot Jail Setup](https://blog.ishosting.com/hs-fs/hubfs/blog/what-is-chroot-jail/setting.png?width=1536&height=440&name=setting.png) There are certain conditions for chroot jail setup: - A system running a Linux or Unix OS. - A user’s account with sudo level privileges. - Terminal/command line access. All commands are run as the **root** user**.** If you are logged into the server as a regular user, use the **sudo** command. ### Create Chroot Jail for SSH Sometimes it is necessary to allow limited access to users via the ssh protocol. For example, a hosting user may require the ability to make patches directly on the server or download content through secure protocols. In such cases, for the sake of security measures, it is correct to create a chroot prison for SSH, granting access rights to users only to certain directories. To create a new root directory chroot prison for SSH using the chroot mechanism, follow these steps: 1. Connect to your Linux server via SSH (or open a terminal on it) and create the jail directory: # mkdir -p /home/test 2. Define the required files according to sshd\_config. After authentication, the ChrootDirectory parameter specifies the path to the directory where chroot redirection will occur. The directory must include the files and directories needed to support the user's session. An interactive session requires, at a minimum, a shell, common **sh**, and basic **/dev** nodes, such as **null**, **zero**, **stdin**, **stdout**, **stderr**, and **tty** devices: \# ls -l /dev/{null,zero,stdin,stdout,stderr,random,tty} 3. As shown below, use the mknod command to create /dev files. The following example uses the -m option to set file permissions, where c stands for a character file and two numbers indicate the major and minor file numbers: \# mkdir -p /home/test/dev/ \# cd /home/test/dev/ \# mknod -m 666 null c 1 3 \# mknod -m 666 tty c 5 0 \# mknod -m 666 zero c 1 5 \# mknod -m 666 random c 1 8 4. Set the appropriate permission for chroot jail. It is important that the root user own the chroot jail, its subdirectories, and subfiles and not any other group or user: \# chown root:root /home/test \# chmod 0755 /home/test \# ls -ld /home/test ### Configure Interactive Shell for SSH Chroot Jail After creating the path to the directory where the chroot redirect will occur, you need to set up an interactive shell for the SSH Chroot Jail. To start, create a fake copy of the root directory and then copy some binaries like bash and ls from the /bin/ directory to the new root directory. To do this, follow these steps: Firstly, create a bin directory and a usr/bin link to it: on RHEL-based systems, the default PATH that sshd sets for users includes /usr/bin but not /bin. Then copy the /bin/bash file to the bin directory like this: ``` mkdir -p /home/test/bin /home/test/usr ln -s ../bin /home/test/usr/bin cp -v /bin/bash /home/test/bin/ ``` Then, determine the shared libraries required by bash and copy them into the jail, keeping their original paths. Library names and locations differ between distributions (for example, /lib64 on RHEL-based systems and /lib/x86\_64-linux-gnu on Debian and Ubuntu), so take the paths from the ldd output instead of typing them by hand: ``` ldd /bin/bash for l in $(ldd /bin/bash | grep -o '/[^ ]*'); do cp -v --parents $l /home/test; done ``` ### Create and Configure SSH User ![Create and Configure SSH User](https://blog.ishosting.com/hs-fs/hubfs/blog/what-is-chroot-jail/ssh-user.png?width=1536&height=440&name=ssh-user.png) If a root user with his own access works on the site, then you will need to create a new user to work with the site. You cannot work as the **root** user. Every time you add new SSH users to the system, you will need to copy the updated account files to the /home/test/etc directory. To create and configure an SSH user, follow these steps: 1. Create an SSH user using the useradd command and set a secure password for the user. Set bash as the login shell with -s: on Debian and Ubuntu, useradd sets /bin/sh by default, and there is no sh in the jail. The passwd command takes the user name and asks for the new password interactively: ``` useradd -s /bin/bash username passwd username ``` 2. Create a chroot jail shared configuration directory /home/test/etc and copy the updated account files (/etc/passwd and /etc/group) to this directory as: \# mkdir /home/test/etc \# cp -vf /etc/{passwd,group} /home/test/etc/ ### Configure SSH to Use Chroot Jail Setting up SSH to use a chroot jail is easy to do by running the following commands: 1. Open the sshd\_config file: \# vi /etc/ssh/sshd\_config 2. Add/change the lines below in the file: #define username to apply chroot jail to Match User username #specify chroot jail ChrootDirectory /home/test 3. Save the file, exit, and restart the SSH service. On RHEL-based systems (AlmaLinux, Rocky Linux, Fedora), it is called sshd; on Debian and Ubuntu, it is called ssh (on Ubuntu 24.04, systemctl restart sshd fails with "Unit sshd.service not found"): ``` # RHEL-based systems systemctl restart sshd # Debian and Ubuntu systemctl restart ssh ``` ### Create the SSH User’s Home Directory and Add Linux Commands If, when checking the operation of the chroot jail, you realize that the SSH user is locked and cannot run any external commands (ls, date, uname, etc.), but only executes bash and its built-in commands, such as pwd, history, echo etc. Example: \# ssh username@192.168.0.10 -bash-4.1$ ls -bash-4.1$ date -bash-4.1$ username Create the SSH user's home directory and add the required commands. Directories are created using a command like mkdir directoryname, where the command name is an abbreviation for make directory. 1. To create a home directory for the SSH user, run the following commands: \# mkdir -p /home/test/home/username \# chown -R username:username /home/test/home/username \# chmod -R 0700 /home/test/home/username 2. Copy some commands like ls, date, and mkdir to the bin directory: \# cp -v /bin/ls /home/test/bin/ \# cp -v /bin/date /home/test/bin/ \# cp -v /bin/mkdir /home/test/bin/ 3. Check the shared libraries for the commands from the previous step and copy them into the jail the same way as for bash: ``` ldd /bin/ls for bin in /bin/ls /bin/date /bin/mkdir; do for l in $(ldd $bin | grep -o '/[^ ]*'); do cp -v --parents $l /home/test; done done ``` ## SFTP Check with Chroot Jail ![SFTP Check with Chroot Jail](https://blog.ishosting.com/hs-fs/hubfs/blog/what-is-chroot-jail/checking.png?width=1536&height=440&name=checking.png) To allow the user to connect only via SFTP and run a final test, follow these steps: 1. Add the following line to the /etc/ssh/sshd\_config file inside the Match User username block, right after the ChrootDirectory line. If you put it before the Match block, it will apply to all users, including you: #Enable sftp to chrooted jail ForceCommand internal-sftp 2. Save the file and exit. Then restart the SSH service: ``` # RHEL-based systems systemctl restart sshd # Debian and Ubuntu systemctl restart ssh ``` 3. Check using SSH (As a result, you will receive an error message): \# ssh username@192.168.0.10 4. Also, try using SFTP like this: \# sftp username@192.168.0.10 ## Additional Security Techniques ![Additional Security Techniques](https://blog.ishosting.com/hs-fs/hubfs/blog/what-is-chroot-jail/additional-measures.png?width=1536&height=440&name=additional-measures.png) When you log into the server, you are usually taken to your account's home directory, which is reserved for storing files and creating directories in a directory that requires the necessary protection and restriction of access. Besides creating a chroot jail, there are additional effective security measures discussed in the following sections. ### Restricting Network Access Using Firewalls If you have a router, you can use it to restrict programs from accessing the Internet. To do this, you need to go into the settings of your built-in or installed firewall and add restrictions for each program that you want to restrict. And [VPN](https://ishosting.com/en/vpn) will help expand the functionality of firewalls. You can learn about the main types and operating principles of firewalls in our article [Web Fortress: Understanding the Importance of Firewall](https://blog.ishosting.com/en/how-does-firewall-work/). ###### Personal VPN This is for those who want to remain undetected online and secure their data. Dedicated IP and complete anonymity. [Watch](https://ishosting.com/en/vpn) ### Using Linux Features to Reduce Privileges Linux has very limited rights for the average user. It can only control its own directory and open specific files from the root for reading. Superuser privileges are vital when configuring the OS and solving various problems because they are not available to change or install programs. On Linux distributions, gaining user privileges requires granting root access. Such rights allow you to perform necessary actions in the root directory, easily manipulate the system, and expand the functionality of the OS. Here, additional protection of the system is necessary to prevent accidental changes that may be made by other computer users. Using special tools to reduce privileges is another effective way to protect and keep your system secure. ![products](https://blog.ishosting.com/hs-fs/hubfs/blog/what-is-chroot-jail/products.png?width=1536&height=440&name=products.png) ### Seccomp Recently, **containers**, specially dedicated environments reminiscent of **sandboxes**, but representing a more universal technology, are increasingly being used to run unsafe programs. Special mechanisms are used to increase the security level of such modern containerization tools, one of which is **Seccomp**. **Seccomp (secure computing mode)** is a secure computing mode, a feature of the Linux kernel, to limit the actions available in a container (for example, limiting your application's access). Seccomp allows you to run Docker containers with minimal privileges, where important system calls are blocked by the default profile. The default Seccomp profile disables about 44 of the 300+ system calls found on modern 64-bit Linux systems and provides reasonable default behavior for running containers with Seccomp. The default Seccomp profile in Docker is a list of allowed calls and blocks calls not on that list, such as manipulations and functions on kernel modules (create\_module, delete\_module, init\_module or finit\_module), using the kernel keyring, which is not namespaced (add\_key, keyctl, request\_key), etc. Default Seccomp profiles are a useful innovation because they limit the capabilities of attackers and reduce the likelihood of attacks. However, this is clearly not enough since many unblocked problems have weak points, and it is simply impossible to block all potentially dangerous calls. Despite its moderate security, it offers broad compatibility with various applications. ### SELinux **SELinux** is not only an access control system at the kernel level but also a universal solution that can effectively cope with many current tasks. SELinux quickly became the de facto standard for secure Linux environments: it is enabled by default in Red Hat Enterprise Linux, Fedora, and their derivatives (such as AlmaLinux and Rocky Linux). Debian and Ubuntu also offer SELinux packages but use AppArmor by default. SELinux works based on the terms: - Domain is a list of actions that can be performed (relative to processes). - Role is a list of domains that can be applied. - Type is a list of actions that can be performed (relative to directories and files). - Security context is about roles, types, and domains. SELinux has three major modes of operation: 1. Enforcing (default). All actions except those allowed are blocked, and attempts at prohibited actions are recorded in the log. The user receives only those privileges that are necessary for work. Enforcing is a strict mode that can be replaced with the other two options. 2. Permissive. Violations are also recorded in the log but are not blocked. 3. Disabled. The forced access control system is disabled. The advantage of such a strict SELinux policy is that it provides the highest level of information security, but configuring the system in this mode requires a lot of effort from system administrators, and there is a risk of restricting user access, which is the principal disadvantage of SELinux. In the face of such restrictions and risks, many administrators choose to disable SELinux on their workstations to avoid risks and problems. To prevent this, critical applications and services such as httpd, named, dhcpd, and mysqld have configured targeted policies that prevent attackers from gaining access to valuable data. Applications that do not have a policy set run in the unconfined\_t domain and are not protected by SELinux. Thus, correctly selected target policies can provide acceptable security without creating additional problems for the user. SELinux includes all the necessary components to protect Linux operating systems and applications from unauthorized access, but because of its complexity, it makes it impractical. ### AppArmor How secure is Linux with AppArmor? **Apparmor** is a third security model that allows access control to be tied to programs rather than users. AppArmor provides isolation through profiles loaded into the kernel, typically at boot. This system also operates in mixed modes: 1. Enforce. The kernel enforces the rules contained in the profile file. Violations will not be tolerated, and a corresponding entry will be made to the log. 2. Complain. Work in warning mode: registers violations without blocking the actions themselves. AppArmor complements the traditional Unix Discretionary Access Control (DAC) model by providing Mandatory Access Control (MAC) with a path-based approach based on the Linux Security Modules (LSM) architecture. It has been included in the main Linux kernel since version 2.6.36, and Canonical has supported its development since 2009. **AppArmor** is an effective and easy-to-use Linux application security system. AppArmor protects the operating system and applications from threats, ensuring good behavior and preventing the exploitation of known and unknown application flaws, unlike **Seccomp**. And, in order to facilitate development, AppArmor uses nested files and has a lower barrier to entry than **SELinux**, which is extremely impractical because of its complexity. ## Conclusion Most services running on the system can see the structure of the server's file system. This is not safe for information stored on the server. In order to prevent the theft of confidential information, chroot jail methods were developed. Setting up a chroot jail along with the necessary resources to run commands and processes in the new root directory, as well as innovative mechanisms for securing the Linux kernel, helps to audit effectively and securely administer the system. ###### 24/7 Support Rely on us. is\*hosting technical support is available 24/7 and does not ignore customers. [Read More](https://ishosting.com/en/support) Table of Contents - [What is Chroot Jail and What Is It Used For](https://blog.ishosting.com/en/what-is-chroot-jail#what-is-chroot-jail) - [Chroot Jail Setup](https://blog.ishosting.com/en/what-is-chroot-jail#chroot-jail-setup) - [SFTP Check with Chroot Jail](https://blog.ishosting.com/en/what-is-chroot-jail#sftp-check) - [Additional Security Techniques](https://blog.ishosting.com/en/what-is-chroot-jail#additional-security-techniques) - [Conclusion](https://blog.ishosting.com/en/what-is-chroot-jail#conclusion) ## Related articles ![Obsidian on VPS: Self-Hosted Sync Without the Subscription](https://blog.ishosting.com/hubfs/blog/obsidian-on-vps/obsidian-on-vps.png) Hosting ### Obsidian on VPS: Self-Hosted Sync Without the Subscription Want free, private note syncing? Learn how to install and configure a self-hosted Obsidian sync server on a VPS to... is\*hosting team 28 Jul 2026 9 min reading ![How to Host a CS2 Server, and When Do You Really Need It?](https://blog.ishosting.com/hubfs/blog/how-to-host-a-cs2-server/how-to-host-a-cs2-server.png) Hosting ### How to Host a CS2 Server, and When Do You Really Need It? Set up your own CS2 dedicated server on a VPS. Covers requirements, installation, configuration, and how to invite... is\*hosting team 15 Jan 2026 13 min reading ![NetBird on VPS: Run Your Own Zero Trust Network Without Handing Keys to a SaaS Provider](https://blog.ishosting.com/hubfs/blog/netbird-on-vps/netbird-on-vps.png) Hosting ### NetBird on VPS: Run Your Own Zero Trust Network Without Handing Keys to a SaaS... Step-by-step 2026 guide to deploying NetBird on VPS hosting. Secure your servers with an open-source, zero-trust mesh... is\*hosting team 21 Jul 2026 8 min reading ## Subscribe to Newsletter The latest news, profitable discounts, and informative articles - subscribe to the is\*hosting blog and be the first to receive a useful newsletter. - **Services** Services - [Virtual Private Servers](https://ishosting.com/en/vps) - [Dedicated Servers](https://ishosting.com/en/dedicated) - [Storage](https://ishosting.com/en/storage) - [VPN](https://ishosting.com/en/vpn) - [Special Offers](https://ishosting.com/en/special-offers) - --- - **Company** Company - [About Us](https://ishosting.com/en/about) - [Data Centers](https://ishosting.com/en/datacenters) - [Blog](https://blog.ishosting.com/en) - [Contacts](https://ishosting.com/en/about#offices) - --- - **Information** Information - [Knowledge Base](https://help.ishosting.com/en) - [Support](https://ishosting.com/en/support) - [Payments Methods](https://ishosting.com/en/payment-methods) - --- - **Account** Account - [Create Account](https://my.ishosting.com/en/register) --- © 2026 WEBRAIN OÜ, Harju maakond, Tallinn, Kesklinna linnaosa, Endla tn 4, 10142 - [![](https://blog.ishosting.com/hs-fs/hubfs/raw_assets/public/ishosting-theme/images/rating-sm.png?width=328&height=70&name=rating-sm.png) ![](https://blog.ishosting.com/hs-fs/hubfs/raw_assets/public/ishosting-theme/images/rating.png?width=421&height=70&name=rating.png)](https://hostadvice.com/hosting-company/ishosting-reviews/#main-info) --- - [Terms of Use](https://ishosting.com/en/terms-of-use) - [Privacy Policy](https://ishosting.com/en/privacy-policy) - [KYC Policy](https://ishosting.com/en/kyc-policy) - [SLA](https://ishosting.com/en/service-level-agreement) - [AUP](https://ishosting.com/en/acceptable-use-policy) - en - [en](https://blog.ishosting.com/en) - [ru](https://blog.ishosting.com/ru/what-is-chroot-jail) ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "abstract" : "A chroot jail isolates a process in a restricted directory, hardening your Linux server. Learn what it is, how it works, and how to set one up on your VPS.", "alternativeHeadline" : "Chroot Jail Explained: What It Is & How to Use It on Linux", "articleSection" : "How to", "author" : { "@type" : "Organization", "name" : "Natasha M.", "sameAs" : [ "https://www.linkedin.com/company/is-hosting", "https://twitter.com/ishostingcom", "https://www.instagram.com/is.hosting" ], "url" : "https://blog.ishosting.com/en/author/natasha-m" }, "dateModified" : "2026-11-09T16:05:21.000Z", "datePublished" : "2024-03-20T23:00:00.000Z", "description" : "A chroot jail isolates a process in a restricted directory, hardening your Linux server. Learn what it is, how it works, and how to set one up on your VPS.", "headline" : "Chroot Jail: How to Restrict Access to a Specific Directory", "image" : [ { "@type" : "ImageObject", "height" : 1348, "name" : "Chroot Jail: How to Restrict Access to a Specific Directory", "url" : "https://help.ishosting.com/hubfs/blog/what-is-chroot-jail/chroot-jail.png", "width" : 2396 } ], "inLanguage" : "en", "mainEntityOfPage" : { "@id" : "https://blog.ishosting.com/en/what-is-chroot-jail", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "address" : [ { "@type" : "PostalAddress", "addressCountry" : "EE", "addressLocality" : "Tallinn", "addressRegion" : "Harju maakond", "postalCode" : "10120", "streetAddress" : "Kesklinna linnaosa, Tuukri tn 19-315" }, { "@type" : "PostalAddress", "addressCountry" : "GB", "addressLocality" : "London", "addressRegion" : "England", "postalCode" : "W1W 7LT", "streetAddress" : "85 Great Portland Street, First Floor" } ], "description" : "is*hosting is an IaaS provider since 2005. We provide VPS, VPN, dedicated servers and data storage to help you achieve your biggest dreams.", "email" : "sales@ishosting.com", "foundingDate" : "2005", "legalName" : "WEBRAIN OÜ", "logo" : { "@type" : "ImageObject", "height" : 26, "url" : "https://help.ishosting.com/hubfs/logo-ishosting.png", "width" : 138 }, "name" : "is*hosting" }, "thumbnailUrl" : "https://help.ishosting.com/hubfs/blog/what-is-chroot-jail/chroot-jail.png", "timeRequired" : "PT9M", "url" : "https://blog.ishosting.com/en/what-is-chroot-jail", "wordCount" : 2980 } ``` ```json { "@context" : "https://schema.org", "@type" : "BreadcrumbList", "itemListElement" : [ { "@type" : "ListItem", "item" : "https://blog.ishosting.com/en", "name" : "Blog", "position" : 1 }, { "@type" : "ListItem", "item" : "https://blog.ishosting.com/en/tag/how-to", "name" : "How to", "position" : 2 }, { "@type" : "ListItem", "item" : "https://blog.ishosting.com/en/what-is-chroot-jail", "name" : "Chroot Jail: How to Restrict Access to a Specific Directory", "position" : 3 } ] } ``` ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Natasha M.", "url" : "https://blog.ishosting.com/en/author/natasha-m" }, "dateModified" : "2026-11-09T16:05:21.052Z", "datePublished" : "2024-03-20T23:00:00.000Z", "headline" : "Chroot Jail Explained: What It Is & How to Use It on Linux", "image" : [ "https://blog.ishosting.com/hubfs/blog/what-is-chroot-jail/chroot-jail.png" ], "mainEntityOfPage" : { "@id" : "https://blog.ishosting.com/en/what-is-chroot-jail", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://blog.ishosting.com/hubfs/logo-ishosting.png" }, "name" : "WEBRAIN OÜ" } } ```