Can u identify a VPS?

draco02

Power Member
Joined
Jun 16, 2017
Messages
650
Reaction score
115
If there are 2 vps from one dedicated server, and the 2 vps visit a website, is it possible that the Website identifies that both vps are from the same dedicated server?
 
Depends... If you're trying to playing with secure banking system with that setup - They can probably match and ban both boxes with canvas/webgl and other fingerprinting techniques.

If it's just a blog - then it's a no.
 
If they have same ip or their range is close, yes.
 
If they have same ip or their range is close, yes.
Theyre from the same range
But if they visit youtube and there are thousand other users from the same ip range online i think they cant tell
 
tracerouting the IPs may show it's part of the same node.

Open command prompt and type

"tracert IP" for both IPs
 
tracerouting the IPs may show it's part of the same node.

Open command prompt and type

"tracert IP" for both IPs
Thanks now someone knows things better
What does the command do??
 
Theyre from the same range
But if they visit youtube and there are thousand other users from the same ip range online i think they cant tell

Hosting - Datacentar IP`s can be easily checked.
There is a difference between Residential and Datacentar IPs - so short answer to your question is YES, they know that you are from a VPS / Dedi.
 
Hosting - Datacentar IP`s can be easily checked.
There is a difference between Residential and Datacentar IPs - so short answer to your question is YES, they know that you are from a VPS / Dedi.
You didnt unterstand my whole question
Ofc they know that because the user agent gives Generic info about the hardware, but do they know that 2 vps are from one node? That is the question
Ofc they know it is a vps/dedi
 
Ahh so i see the ip range right?
Here is an example of two Linux OpenVZ VPS hosted on the same node but different IP ranges

C:\Users\hello>tracert 176.31.210.206

Tracing route to host55.rocketspr.com [176.31.210.206]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms routerlogin.net [192.168.0.1]
2 14 ms 19 ms 19 ms 10.86.240.1
3 18 ms 17 ms 18 ms brnt-core-2b-xe-232-0.network.virginmedia.net [62.252.115.205]
4 * * * Request timed out.
5 * * * Request timed out.
6 14 ms 19 ms 18 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
7 * * * Request timed out.
8 15 ms 29 ms 18 ms uk-lon01b-ri1-ae-25-0.aorta.net [84.116.136.102]
9 22 ms 20 ms 17 ms be100-109.ldn-1-a9.uk.eu [213.186.32.169]
10 24 ms 19 ms 21 ms be103.gra-g1-nc5.fr.eu [91.121.215.178]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 15 ms 17 ms 20 ms ns3079671.ip-147-135-131.eu [147.135.131.49]
16 26 ms 19 ms 18 ms host55.rocketspr.com [176.31.210.206]

Trace complete.

C:\Users\hello>tracert 176.31.136.231

Tracing route to 231-136-31-176.entrenalia.net [176.31.136.231]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms routerlogin.net [192.168.0.1]
2 16 ms 20 ms 18 ms 10.86.240.1
3 13 ms 18 ms 19 ms brnt-core-2a-xe-013-0.network.virginmedia.net [80.2.147.165]
4 * * * Request timed out.
5 13 ms 14 ms 14 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
6 * * * Request timed out.
7 13 ms 60 ms 17 ms uk-lon01b-ri1-ae-25-0.aorta.net [84.116.136.102]
8 14 ms 19 ms 18 ms be100-109.ldn-1-a9.uk.eu [213.186.32.169]
9 24 ms 19 ms 20 ms be103.gra-g1-nc5.fr.eu [91.121.215.178]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 24 ms 18 ms 19 ms ns3079671.ip-147-135-131.eu [147.135.131.49]
15 21 ms 19 ms 18 ms 231-136-31-176.entrenalia.net [176.31.136.231]

Trace complete.

147.135.131.49 is the node (Dedicated server) IP.
 
You didnt unterstand my whole question
Ofc they know that because the user agent gives Generic info about the hardware, but do they know that 2 vps are from one node? That is the question
Ofc they know it is a vps/dedi
Ahh so i see the ip range right?

You are mixing things up - User Agent have nothing to do with your IP.
Yes the IP range.
 
Run your servers through this website and look through all the previous records. Including A, MX, records ect.

Most likely the IP associated with your VPS now had a different identity before and depending on the privacy/configuration of previous owners you can often find the root hosts along with all other domains/IP running on those servers.

This tool can find all those hidden PBNs, trace back the original domain registar of any domain and find any other domains/websites owned by the same person at that time. It's like Wayback Machine for DNS records, it's actually really cool.

Code:
https://securitytrails.com/dns-trails
 
Run your servers through this website and look through all the previous records. Including A, MX, records ect.

Most likely the IP associated with your VPS now had a different identity before and depending on the privacy/configuration of previous owners you can often find the root hosts along with all other domains/IP running on those servers.

This tool can find all those hidden PBNs, trace back the original domain registar of any domain and find any other domains/websites owned by the same person at that time. It's like Wayback Machine for DNS records, it's actually really cool.

Code:
https://securitytrails.com/dns-trails
Thank you a lot!
 
No worries.

Also, be sure to check the 'IP Neighbors to xxx.xxx.xx.xxx" yellow button near top left.

That will give you a full range of IPs on the range, and summarize how many 'sites/domains' are on each neighbor IP. Often you will find the main webhost domain, cpanel records, ect.

I use this often to check what other domains web hosts have, check the neighboring IPs/domains for spam score/blacklists before building out any important whitehat business.
 
Here is an example of two Linux OpenVZ VPS hosted on the same node but different IP ranges

C:\Users\hello>tracert 176.31.210.206

Tracing route to host55.rocketspr.com [176.31.210.206]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms routerlogin.net [192.168.0.1]
2 14 ms 19 ms 19 ms 10.86.240.1
3 18 ms 17 ms 18 ms brnt-core-2b-xe-232-0.network.virginmedia.net [62.252.115.205]
4 * * * Request timed out.
5 * * * Request timed out.
6 14 ms 19 ms 18 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
7 * * * Request timed out.
8 15 ms 29 ms 18 ms uk-lon01b-ri1-ae-25-0.aorta.net [84.116.136.102]
9 22 ms 20 ms 17 ms be100-109.ldn-1-a9.uk.eu [213.186.32.169]
10 24 ms 19 ms 21 ms be103.gra-g1-nc5.fr.eu [91.121.215.178]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 15 ms 17 ms 20 ms ns3079671.ip-147-135-131.eu [147.135.131.49]
16 26 ms 19 ms 18 ms host55.rocketspr.com [176.31.210.206]

Trace complete.

C:\Users\hello>tracert 176.31.136.231

Tracing route to 231-136-31-176.entrenalia.net [176.31.136.231]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms routerlogin.net [192.168.0.1]
2 16 ms 20 ms 18 ms 10.86.240.1
3 13 ms 18 ms 19 ms brnt-core-2a-xe-013-0.network.virginmedia.net [80.2.147.165]
4 * * * Request timed out.
5 13 ms 14 ms 14 ms m686-mp2.cvx1-b.lis.dial.ntli.net [62.254.42.174]
6 * * * Request timed out.
7 13 ms 60 ms 17 ms uk-lon01b-ri1-ae-25-0.aorta.net [84.116.136.102]
8 14 ms 19 ms 18 ms be100-109.ldn-1-a9.uk.eu [213.186.32.169]
9 24 ms 19 ms 20 ms be103.gra-g1-nc5.fr.eu [91.121.215.178]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 24 ms 18 ms 19 ms ns3079671.ip-147-135-131.eu [147.135.131.49]
15 21 ms 19 ms 18 ms 231-136-31-176.entrenalia.net [176.31.136.231]

Trace complete.

147.135.131.49 is the node (Dedicated server) IP.
its not the IP of dedicated server but the IP of the network, it could be anything a router a vlan you cannot say its dedicated server.
They may know that IP ranges are same, maximum they can do to find your hosting company.
 
I don't think they can catch you. Because a vps company can have unlimited ip's in the same range doesn't mean all used by same user.
 
its not the IP of dedicated server but the IP of the network, it could be anything a router a vlan you cannot say its dedicated server.
They may know that IP ranges are same, maximum they can do to find your hosting company.
Yes that's why I said may be able to but in the example I gave I know for a fact it's the same server.
 
Back
Top