API Documentation

The VNC Resolver is powered by an API which can be used to fetch information from the service.

Note that requests are rate-limited to prevent abuse.

API Objects:

VNC Object

{
	id: number;
	ip: string;
	port: number;
	city: string;
	state: string;
	country: string;
	clientname: string;
	screenres: string;
	hostname: string;
	osname: string;
	openports: string;
	username: string;
	password: string;
	createdat; number;
}
				
General Info

id is the Scan ID of the VNC. This is unique to this VNC, and this particular scan.

ip is the IP Address of the VNC.

hostname is the rDNS hostname of the VNC.

port is the port number the VNC is listening on.

createdat is when the VNC was added to the Resolver database.

VNC Info

clientname is the desktop name the VNC sent when the scan was taken.

screenres is the screen resolution the VNC was at when the scan was taken.

osname is the OS the VNC is running when the scan was taken (probed by nmap, so results may be a little inaccurate)

username is the username required to login to the VNC when the scan was taken.

password is the password required to login to the VNC when the scan was taken.

Geolocation Info

country is the country the VNC is located in.

city is the approximate city the VNC is located in.

state is the approximate state the VNC is located in.

API Endpoints

Fetching a random VNC server:

This endpoint always returns a completely random VNC server.

$ curl https://computernewb.com/vncresolver/api/scans/vnc/random

Fetching a specific VNC server (via ID):

This endpoint is useful if you have IDs from a /api/random or search response.

$ curl https://computernewb.com/vncresolver/api/scans/vnc/id/69530176

Searching VNC servers

Note that additionally, there is a full querystring parameter when searching. If set to true, then the API will send full VNC objects instead of IDs, avoiding having to call the API multiple times.

by Client Name:

This endpoint will return all VNCs in the scan's database with a specific client name. To find all VNCs with the client name "JDownloader", for example, you could run:

$ curl https://computernewb.com/vncresolver/api/scans/vnc/search?clientname=JDownloader
by ISO 3166-1 alpha-2 country code:

You can also use country ISO 3166-1 alpha-2 codes. To fetch a server in Romania, for example, you would use "RO", like so:

$ curl https://computernewb.com/vncresolver/api/scans/vnc/search?country=RO

For a full list, see: https://en.wikipedia.org/wiki/List_of_ISO_3166_country_codes. Note that some countries don't have any VNCs available (you will receive a "Country name is not valid." error response if so)

by ASN:

Finally, you can use AS numbers to search.

$ curl https://computernewb.com/vncresolver/api/scans/vnc/search?asn=AS16276

Fetching current stats:

This endpoint retreieves the current status of the API backend and the number of VNCs in the scan's database.

$ curl https://computernewb.com/vncresolver/api/scans/vnc/stats

Fetching scans:

This endpoint retreieves all valid scan IDs which can be passed to the VNC Resolver API.

$ curl https://computernewb.com/vncresolver/api/scans