A web service is a software system designed to support interoperable machine-to-machine interaction over a network. It has an interface described in a machine-processable format (specifically WSDL). Other systems interact with the web service in a manner prescribed by its description using SOAP-messages, typically conveyed using HTTP with an XML serialization in conjunction with other web-related standards.
The Internet Corporation for Assigned Names and Numbers (ICANN) is the organization that governs the rules and regulations for domain name registrations. ICANN requires, for various reasons including to determine ownership of a domain should a dispute transpire, that a publicly accessible database be maintained that contains the contact information of all domain registrants. In layman's terms this means your domain name will be searchable by anyone and those search results will include your full name, physical address and other contact information. In order to protect your privacy in this regard, Domain.com offers WHOIS Domain Privacy which then masks your information using our own and implements a procedure for you to control who is able to then gain access to your contact information via a WHOIS search. Whenever you buy a domain name, no matter what domain name registration service you use, you are subject to the same ICANN rules, for this reason it is important to use a reputable service who cares about your privacy. Domain.com always recommends enabling WHOIS Domain Privacy.
^ Compare: Oya 2008, "Under the current Web Services, […] stakeholder systems must follow the predefined rules for a particular business service including those about business protocols to send/receive messages and about system operation. […] More flexible mechanism is desired where freely built and autonomously running systems can exchange business messages without pre-agreed strict rules. We call it Autonomous Web Services (AWS) and proposed the framework called Dynamic Model Harmonization (DMH) with its algorithm, which dynamically adjusts different business process models between systems […]."
Web services allow different organizations or applications from multiple sources to communicate without the need to share sensitive data or IT infrastructure. All information is instead shared through a programmatic interface across a network. This interface can then be added to a GUI, like a web page, to deliver specific functionality to users. Due to this, web services are not specific to one programming language or operating system and do not require the use of browsers or HTML.
"All the standard Web Services works using following components:" ... the problem with this answer is that it suggests that web services do or must operate within the SOAP/WSDL mechanism. This is inaccurate. Representational State Transfer (REST) is another very popular paradigm for implementing web services. Some major websites have deprecated their SOAP services in favor of REST web services. – scottb Jul 7 '15 at 15:50
Web services are almost like normal a web page. The difference is that they are formatted to make it very easy for a program to pull data from the page, to the point of probably not using any HTML. They generally also are more reliable as to the consistency of the format, may use a different formal process to define the content such soap or raw xml, and there is often also a descriptor document that formally defines the structure for the data.
If you are looking for a domain, WhoIs domain lookup can tell you if it's already owned by another entity and provide contact information for the domain name owner. WhoIs domain information can help you determine the proper contact for any domain listed in the Whois database. A WhoIs lookup identifies the administrator contact information, billing contact and the technical contact for each domain name listing or IP in the WhoIs database. A WhoIs IP search can also help you potentially determine the source of spam and other details related to a website.
Functional and non-functional testing of Web services is done with the help of WSDL parsing. Regression testing is performed by identifying the changes made to upgrade software. Web service regression testing needs can be categorized in three different ways, namely, changes in WSDL, changes in the code, and selective re-testing of operations. We can capture the above three needs in three intermediate forms of Subset WSDL, namely, Difference WSDL (DWSDL), Unit WSDL (UWSDL), and Reduced WSDL (RWSDL), respectively. These three Subset WSDLs are then combined to form Combined WSDL (CWSDL) that is further used for regression testing of the Web service. This will help in Automated Web Service Change Management (AWSCM), by performing the selection of the relevant test cases to construct a reduced test suite from the old test suite. 
Now we discussed in the previous topic about WSDL and how it contains information on what the Web service actually does. But how can a client application locate a WSDL file to understand the various operations offered by a web service? So UDDI is the answer to this and provides a repository on which WSDL files can be hosted. So the client application will have complete access to the UDDI, which acts as a database containing all the WSDL files.
You'll receive a WhoisGuard subscription absolutely FREE with every eligible domain registration or transfer. WhoisGuard subscription expiration is based on purchase date rather than activation date. WhoisGuard provides subscription pursuant to its Services Agreement with Namecheap. Terms and conditions apply. Visit the WhoisGuard page for details.