whois.uniregistry.net Open in urlscan Pro
2620:57:400d::20  Public Scan

Submitted URL: http://rdap.uniregistry.net/
Effective URL: https://whois.uniregistry.net/
Submission: On July 05 via api from GB — Scanned from CA

Form analysis 1 forms found in the DOM

POST /whois/

<form class="form-inline lookup-form" role="form" action="/whois/" method="POST">
  <div class="form-group">
    <label class="sr-only" for="lookup-name">Name</label>
    <input name="keyword" type="text" class="form-control input-lg" id="lookup-name" placeholder="Domain name, nameserver, registrar...">
  </div>
  <button type="submit" class="btn btn-default input-lg">LOOKUP</button>
</form>

Text Content

­
Toggle navigation



WHOIS LOOKUP

Query our extensions
Name
LOOKUP
scroll-down
RDAP API

The API interface complies with the behavior stated in the RDAP's RFCs:

 * RFC7480 - HTTP Usage in the Registration Data Access Protocol (RDAP)
 * RFC7481 - Security Services for the Registration Data Access Protocol (RDAP)
 * RFC7482 - Registration Data Access Protocol (RDAP) Query Format
 * RFC7483 - JSON Responses for the Registration Data Access Protocol (RDAP)
 * RFC7484 - Finding the Authoritative Registration Data (RDAP) Service
 * RFC8056 - Extensible Provisioning Protocol (EPP) and Registration Data Access
   Protocol (RDAP) Status Mapping

This implementation conforms to the RDAP Operational Profile for gTLD Registries
and Registrars version 1.0. You can query for Domains, Nameservers, and Entities
(Registrar objects). Querying for Contact objects is not supported.

Queries can be done for an exact match when the resource is specified directly
in the URL. For example, to query for domain names, point the RESTful client to:
/rdap/domain/example.com where example.com is the TLD to query.

Queries can also be done using the asterisk as the wildcard character to match
zero or more trailing characters. For example, a domain search by
name:/rdap/domains?name=exam*.com will return results for the domain names
exam.com, exams.com, example.com, etc.

The only content-type supported in our responses is application/rdap+json. If an
RDAP client sends the Accept header in its request we will ignore it.


USAGE OF OUR WHOIS TOOLS

The WHOIS information provided in this page has been redacted in compliance with
ICANN's Temporary Specification for gTLD Registration Data.

The data in this record is provided by UNR for informational purposes only, and
it does not guarantee its accuracy. UNR is authoritative for whois information
in top-level domains it operates under contract with the Internet Corporation
for Assigned Names and Numbers. Whois information from other top-level domains
is provided by a third-party under license to UNR.

This service is intended only for query-based access. By using this service, you
agree that you will use any data presented only for lawful purposes and that,
under no circumstances will you use (a) data acquired for the purpose of
allowing, enabling, or otherwise supporting the transmission by e-mail,
telephone, facsimile or other communications mechanism of mass unsolicited,
commercial advertising or solicitations to entities other than your existing
customers; or (b) this service to enable high volume, automated, electronic
processes that send queries or data to the systems of any Registrar or any
Registry except as reasonably necessary to register domain names or modify
existing domain name registrations.

UNR reserves the right to modify these terms at any time. By submitting this
query, you agree to abide by this policy. All rights reserved.

For more information on Whois status codes, please visit https://icann.org/epp

You can learn more about Whois by reading ICANN's educational and policy
materials, available at https://whois.icann.org.

Copyright © 2023 - Tucows Registry. All rights reserved