To include a service or website in the whitelist, you must submit a request to Mintsifry. Only the owner, who is a legal entity or an individual entrepreneur, can submit a request. Individuals cannot submit requests. Each request is considered by Mintsifry individually.
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.
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 another type of IP address is not possible. Instead of a VDS server, you can create a cloud server in a public subnet;
S3 — service IP addresses are used to access buckets, which process traffic from many users simultaneously. For an IP address to be allocated, you can deploy your own solution on a dedicated server or cloud server, which will receive traffic on the dedicated or cloud server's IP address and proxy 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
If the IP address is not allocated exclusively for your service or website — change the IP address. Changing the IP address is not available for all products.
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
Cloud server
Managed Kubernetes
Cloud load balancer
Firewalls
In the Control panel, on the top menu, click Products and select Dedicated servers.
In the Servers section, see the server location in the server card under its name.
If the server is not in Russia, order a dedicated server in Russia; when ordering the server, select a dedicated VLAN for it.
In the Control panel, on the top menu, click Products and select Cloud servers.
In the Servers section, see the server location in the server card under its name.
If the server is not in Russia, create a cloud server in Russia; when creating the server, select a public subnet for it.
In the Control panel, on the top menu, click Products and select Managed Kubernetes.
In the cluster card, see the cluster location in the Pool field.
If you created a balancer in Russia, re-create the cloud servers behind the balancer in Russia, in the same location as the balancer.
You can get information depending on the firewall type — hardware or virtual:
hardware firewalls are located in Russia;
virtual firewalls are deployed by you on a cloud server or in a Cloud powered by VMware. IP addresses in Cloud powered by VMware are located in Russia; those on a cloud server may be located outside of Russia.
If you have a virtual firewall deployed on a cloud server, check the server location:
In the Control panel, on the top menu, click Products and select Cloud servers.
In the Servers section, see the server location in the server card under its name.
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
Cloud server
Managed Kubernetes
Cloud load balancer
Firewalls
Cloud powered by VMware
In the Control panel, on the top menu, click Products and select Dedicated servers.
In the server card, click next to the public IP address and see the IP address.
Check if the IP address is allocated for your service or website:
if a VLAN is indicated next to the IP address with a number, for example VLAN — 1234, the server uses a public dedicated IP address, which is allocated for your service or website;
if VLAN — shared is indicated, the server uses a public shared IP address, which is not allocated for your service or website. You can change the IP address.
In the Control panel, on the top menu, click Products and select Cloud servers.
Open the server page → Ports tab.
See the IP address in the public network port card.
Check if the port IP address is allocated for your service or website:
if a public IP address is indicated, 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 indicated, 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 indicated, 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.
A Managed Kubernetes cluster is created with a public Kube API IP address by default, which cannot be allocated for your service or website. To access the cluster via an IP address that is allocated exclusively for your service or website, a load balancer with an IP address from a public subnet must be created for the cluster.
If the cluster does not have a balancer, create one in a public subnet; to do this, go to step 3.
In the Control panel, on the top menu, click Products and select Cloud servers.
Go to the Load balancers section.
If the cluster has a balancer, open the balancer page.
See its IP address in the Network field.
Check if the IP address is allocated for your service or website:
if a public IP address is indicated, for example 203.0.113.4, and a public subnet with a mask, for example 203.0.113.0/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 indicated, 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 load balancer uses a public floating IP address, which is not allocated for your service or website. You can change the IP address.
In the Control panel, on the top menu, click Products and select Cloud servers.
Go to the Load balancers section.
Open the balancer page.
See its IP address in the Network field.
Check if the IP address is allocated for your service or website:
if a public IP address is indicated, 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 indicated, 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.
You can look up the IP address depending on the firewall type — hardware or virtual:
a hardware firewall is placed in a public dedicated subnet by default, from which IP addresses are allocated exclusively for your service or website. You can see the IP address in the Control panel: on the top menu, click Products → Firewalls → see the IP address in the firewall card;
you deploy a virtual firewall yourself on a cloud server or in Cloud powered by VMware; the server's IP address is used for access. Depending on where the firewall is deployed, look up the IP address according to the instructions for a cloud server or Cloud powered by VMware.
All public IP addresses in Cloud powered by VMware are allocated exclusively for your service or website.
In the Control panel, on the top menu, click Products and select Cloud powered by VMware.
In the Virtual data centers section, open the data center page.
To see the IP address:
for an Edge router — open the Edge routers tab → router IP address list.
for a Direct Connected subnet — open the Direct Connected subnets tab.
To access the cluster via an IP address that is allocated exclusively for your service or website, you need to create a load balancer with an IP address from a public subnet for the cluster.