Ascio Web Service v2

• Select programming language:
• C#
• PHP 5
• PHP 5 Classes
• Perl
• Java Axis
• Python
• NodeJS
• SOAP

The Ascio Availability Check Documentation

The Ascio has different modes that differ in speed and quality:

Availability Check modes

Speed Check (Fast)

The Speed Check will rely on cached data only. The cached data is derived primarily by the zone crawler that collects raw names from zones and similar data sources every day.

This means, that when a Speed Check is performed, the system will look for the name in the database and based on the finding it will reply with available or not available.

The Speed Check is as the name implies the fastest way of performing an availability check and it should be used when many names are checked in one operation. As the fast check is based on cached information there will be situations where the information is not up to date and therefore returns an incorrect answer. If the cached data has not been recently updated, the result of the Speed Check will therefore reply with available or not available and a description telling that the result is based on older data. Another limitation to the Speed Check is, that it will not be able to tell if an available domain is regular or premium.

Smart Check (Smart)

The Smart check will start looking for the name in the cached data and if not found here, it will continue to look for the name using NS lookup.

This means that if the name is found in the cached data the system will answer with not available; if the name is not found, the system will continue to search for the availability via NS lookup.

The Smart check will not reply with the same speed as the Speed check, as NS lookups take longer time. Instead the Smart check will respond with a higher certainty, as the answer is based on several data sources. The Smart check can be used for both high and low volume searches – though the importance of response time should be considered for high volume searches. This check is the optimum choice when multiple TLDs are involved.

Smart-Live Check (SmartLive)

The Smart-Live check will start looking for the name in the cached data. If the name is not found here, it will continue to search for the name using NS lookup. If the name is not found here, it continues to search for the name using live lookup.

This means that if the name is found in at any stage of the method, it will answer with not available.

This check should only be used for low volume checks, as the response time is high

Live Check (Live)

The Live check will only perform live lookup of a name. The checks are based on EPP, WHOIS server, WHOIS at a web site or finger at the registry level. As Ascio is accredited at many registries, the availability-check can query most TLDs directly via EPP.

This means that the name is always checked at the authoritative source: the Registry, which should guarantee that the answer is accurate. In practice, experience tells us that some of the small Registries do not always respond correctly, so there will always be a risk that the answer is not correct – but the Live Check will always provide the best answer.

Result codes

Result errors

Last updated on 14.04.2015

package ascio.v2.examples;
import com.ascio.www._2007._01.*;
import com.ascio.www._2007._01.holders.*;
import ascio.lib.*;

public class AvailabilityCheckExample {
	public static Response main() {
		AscioConfig config = new AscioConfig();
		V2 env = config.getTesting().getV2();

		try {
			/**outputs holders*/

			ResponseHolder availabilityCheckResultHolder = new ResponseHolder();
			ArrayOfAvailabilityCheckResultHolder resultsHolder = new ArrayOfAvailabilityCheckResultHolder();

			env.getClient().availabilityCheck(env.getSessionId(), new String[]{
		}, new String[]{
		}, QualityType.Fast, availabilityCheckResultHolder, resultsHolder);

			Response response = availabilityCheckResultHolder.value;

			System.out.println("AvailabilityCheck ResultCode\t: " + response.getResultCode().toString());
			System.out.println("AvailabilityCheck Message\t: " + response.getMessage());
			if(response.getResultCode() == 400) {
				for( String value : response.getValues()) {
					System.out.println("Error:	" + value);
				}
			}
			return response;
		} catch (Exception e) {
			System.out.print(e);
		}
		return new Response();package ascio.v2.examples;
import com.ascio.www._2007._01.*;
import com.ascio.www._2007._01.holders.*;
import ascio.lib.*;

public class AvailabilityCheckExample {
	public static Response main() {
		AscioConfig config = new AscioConfig();
		V2 env = config.getTesting().getV2();

		try {
			/**outputs holders*/

			ResponseHolder availabilityCheckResultHolder = new ResponseHolder();
			ArrayOfAvailabilityCheckResultHolder resultsHolder = new ArrayOfAvailabilityCheckResultHolder();

			env.getClient().availabilityCheck(env.getSessionId(), new String[]{
		}, new String[]{
		}, QualityType.Fast, availabilityCheckResultHolder, resultsHolder);

			Response response = availabilityCheckResultHolder.value;

			System.out.println("AvailabilityCheck ResultCode\t: " + response.getResultCode().toString());
			System.out.println("AvailabilityCheck Message\t: " + response.getMessage());
			if(response.getResultCode() == 400) {
				for( String value : response.getValues()) {
					System.out.println("Error:	" + value);
				}
			}
			return response;
		} catch (Exception e) {
			System.out.print(e);
		}
		return new Response();