Get information about a service or website IP address for the whitelist

During periods of mobile internet restrictions, only services and websites included in the whitelist remain accessible.

A white list is a list of socially significant and highly popular Russian services and websites. The list is updated and regulated by the Ministry of Digital Development, Communications and Mass Media of the Russian Federation (Mintsifry).

To include a service or website in the white list, you must submit a request to Mintsifry. The request can only be submitted by its owner, who is a legal entity or an individual entrepreneur. Individuals cannot submit a request. Each request is reviewed by Mintsifry on an individual basis.

When submitting a request, you will need information about the public IP addresses of the website or service. The IP addresses must comply with the requirements. In the Servercore Control panel, you can get information about the IP address of your service or website.

Mintsifry may request confirmation that the specified IP addresses are within the Servercore infrastructure. To receive such confirmation, create a ticket.

Requirements for the IP address

The IP address must be located in Russia and must be allocated in the Servercore infrastructure exclusively for your website or service.

Not suitable:

• public floating IP addresses of the cloud platform;
• direct public IP addresses of the cloud platform;
• public shared IP addresses of a dedicated server.

Products where IP addresses can be allocated exclusively for your service or website:

• Dedicated servers;
• Cloud servers;
• Managed Kubernetes;
• Cloud load balancers;
• Firewalls;
• Cloud powered by VMware.

In some products, IP addresses cannot be allocated for your service or website:

• VDS servers—one public IP address from a shared subnet is allocated to the server; assigning an IP address of a different type is not possible. Instead of a VDS server, you can create a cloud server in a public subnet;

• S3—service IP addresses that process traffic from many users simultaneously are used to access buckets. To have an IP address allocated, you can deploy your own solution on a dedicated server or cloud server that will receive traffic at the IP address of the dedicated or cloud server and proxy the traffic to S3;

• CDN — service IP addresses of multiple CDN servers are used to access content, which cannot be allocated exclusively for your service or website.

Get information about a service or website IP address

1. Check if the IP address is located in Russia.
2. Look up the IP address of your service or website.
3. If an IP address is not dedicated solely to your service or website— change the IP address. Not all products allow you to change the IP address.

1. Check if the IP address is located in Russia

An IP address is located in the same location as the device it is assigned to.

Hardware firewalls and Cloud powered by VMware are located in Russia. To check the device location in other products, see the instructions:

Dedicated server

1. In the Control panel, on the top menu, click Products and select Dedicated servers.

2. In the Servers section, see the server location in the server card under its name.

3. If the server is not in Russia, order a dedicated server in Russia; when ordering the server, select a dedicated VLAN for it.

Cloud server

1. In the Control panel, on the top menu, click Products and select Cloud servers.

2. In the Servers section, see the server location in the server card under its name.

3. If the server is not in Russia, create a cloud server in Russia; when creating the server, select a public subnet for it.

Managed Kubernetes

1. In the Control panel, on the top menu, click Products and select Managed Kubernetes.

2. In the cluster card, see the cluster location in the Pool field.

3. If the cluster is not in Russia, create a Managed Kubernetes cluster in Russia.

Cloud load balancer

1. In the Control panel, on the top menu, click Products and select Cloud servers.

2. Go to the Load balancers section.

3. In the balancer card, see the balancer location under its name.

4. If the load balancer is not in Russia, create a load balancer in Russia; when creating, select a public subnet.

5. If you created a balancer in Russia, re-create the cloud servers behind the balancer in Russia, in the same location as the balancer.

Firewalls

You can get information depending on the firewall type — hardware or virtual:

• hardware firewalls are located in Russia;

• you deploy virtual firewalls yourself on a cloud server or in the VMware-based cloud. IP addresses in the VMware-based cloud are located in Russia, while in a cloud server, they may be located outside of Russia.

If you have a virtual firewall deployed on a cloud server, check the server location:

1. In the Control panel, on the top menu, click Products and select Cloud servers.

2. In the Servers section, see the server location in the server card under its name.

3. If the server is not in Russia, create a cloud server in Russia; when creating the server, select a public subnet for it.

2. Look up the IP address

Dedicated server

1. In the Control panel, on the top menu, click Products and select Dedicated servers.

2. In the server card, next to the public IP address, click to view the IP address.

3. Check if the IP address is allocated for your service or website:

   • if a VLAN with a number is indicated next to the IP address, for example VLAN — 1234, the server is using a public dedicated IP address, which is allocated for your service or website;

   • if VLAN — shared is indicated, the server is using a public shared IP address, which is not dedicated to your service or website. You can change the IP address.

Cloud server

1. In the Control panel, in the top menu, click Products and select Cloud Servers.

2. Open the server page → Ports tab.

3. See the IP address in the public network port card.

4. Check if the port IP address is allocated for your service or website:

   • if a public IP address is specified, for example 203.0.113.4, and a public subnet with a mask, for example 203.0.113.0/29, the server uses an IP address from a public subnet, which is allocated for your service or website;

   • if only a public IP address is specified, for example 203.0.113.4, the server uses a direct public IP address, which is not allocated for your service or website. You can change the IP address;

   • if a pair of IP addresses is specified, for example 192.168.10.21 ← 203.0.113.4, and a private subnet with a mask, for example 192.168.10.21/24, the server uses a public floating IP address, which is not allocated for your service or website. You can change the IP address.

Managed Kubernetes

A Managed Kubernetes cluster is created by default with a Kube API public IP address that cannot be dedicated to your service or website. To access the cluster via an IP address that is dedicated solely to your service or website, a load balancer must be created for the cluster with an IP address from a public subnet.

1. If the cluster does not have a load balancer, create one in a public subnet; to do this, go to step 3.

2. In the Control panel, in the top menu, click Products and select Cloud Servers.

3. Go to the Load Balancers section.

4. Open the load balancer page.

5. In the Network field, view the load balancer IP address.

6. Check if the IP address is allocated for your service or website:

   • if a public IP address is specified, for example 203.0.113.4, and a public subnet with a mask, for example 203.0.113.0/29, the server uses an IP address from a public subnet, which is allocated for your service or website;

   • if a pair of IP addresses is specified, for example 192.168.10.21 ← 203.0.113.4, and a private subnet with a mask, for example 192.168.10.21/24, the server uses a public floating IP address, which is not allocated for your service or website. You can change the IP address.

Cloud load balancer

1. In the Control panel, in the top menu, click Products and select Cloud Servers.

2. Go to the Load Balancers section.

3. Open the balancer page.

4. In the Network field, view the load balancer IP address.

5. Check if the IP address is allocated for your service or website:

   • if a public IP address is specified, for example 203.0.113.4, and a public subnet with a mask, for example 203.0.113.4/29, the load balancer uses an IP address from a public subnet, which is allocated for your service or website;

   • if a pair of IP addresses is specified, for example 192.168.10.21 ← 203.0.113.4, and a private subnet, for example 192.168.0.0/24, the load balancer uses a public floating IP address, which is not allocated for your service or website. You can change the IP address.

Firewalls

You can look up the IP address depending on the firewall type — hardware or virtual:

• a hardware firewall is placed by default in a public dedicated subnet, the IP addresses from which are allocated only for your service or website. You can view the IP address in the Control panel: in the top menu click Products → Firewalls → view the IP address in the firewall card;

• you deploy a virtual firewall yourself on a cloud server or in the VMware-based cloud, and the server IP address is used for access. Depending on where the firewall is deployed, check the IP address using the instructions for a cloud server or the VMware-based cloud.

Cloud powered by VMware

All public IP addresses in Cloud powered by VMware are allocated exclusively for your service or website.

1. In the Control panel, in the top menu, click Products and select VMware-based Cloud.

2. In the Virtual Data Centers section, open the data center page.

3. To see the IP address:

   • Edge router — open the Edge Gateways tab → list of router IP addresses.

   • from a Direct Connected subnet — open the Direct Connected subnets tab.

3. Change the IP address

Dedicated server

To change the IP address to one dedicated to your service or website, add additional public IP addresses.

Cloud server

1. If you do not yet have a public subnet in the server location, create a public subnet.

2. Add the server to a public subnet.

Managed Kubernetes

To access the cluster via an IP address that is dedicated solely to your service or website, you need to create a load balancer for the cluster with an IP address from a public subnet.

1. If you do not yet have a public subnet in the cluster location, create a public subnet.

2. Create a load balancer with an IP address from a public subnet via Ingress API or via Gateway API.

Cloud load balancer

1. If you do not yet have a public subnet in the load balancer location, create a public subnet.

2. Create a load balancer in a public subnet.

Firewalls

You can change the IP address for a virtual firewall deployed on a cloud server.

1. If you do not yet have a public subnet in the server location, create a public subnet.

2. Add the server to a public subnet.