Weblate 81fa459c6c Update translation files
Updated by "Update PO files to match POT (msgmerge)" add-on in Weblate.
2024-08-09 23:16:26 +00:00
2024-08-03 00:10:23 +02:00
2024-08-10 01:16:07 +02:00
2024-07-10 22:25:27 +02:00
2024-08-03 16:52:14 +02:00
2024-08-10 00:56:46 +02:00
2024-08-08 17:10:47 +02:00
2024-07-10 22:25:27 +02:00
2024-08-09 23:16:26 +00:00
2024-08-07 14:31:44 +02:00
2024-07-10 22:25:27 +02:00
2024-08-03 16:52:14 +02:00
2024-08-02 23:24:52 +02:00
2024-07-19 01:36:14 +02:00
2024-07-11 00:05:24 +02:00
2024-07-10 22:25:27 +02:00
2024-07-10 22:25:27 +02:00
2024-08-05 01:30:27 +02:00
2024-08-05 01:30:27 +02:00
2024-07-11 00:05:24 +02:00
2024-07-10 22:25:27 +02:00
2024-08-08 17:10:47 +02:00
2024-07-11 00:05:24 +02:00
2024-07-31 02:10:55 +02:00
2024-08-03 00:06:38 +02:00
2024-07-10 22:25:27 +02:00
2024-08-09 23:02:58 +02:00
2024-08-08 02:14:27 +02:00
2024-08-03 00:06:38 +02:00
2024-07-22 14:45:21 +02:00
2024-07-28 01:04:08 +02:00
2024-07-31 02:10:55 +02:00

Domain Watchdog

Domain Watchdog is a standalone application that utilizes RDAP to gather publicly accessible information about domain names, track their history, and automatically purchase them. For more information please check the wiki !

Why use it?

  • Historical Tracking: Know the history of a domain name, from its inception to its release into the public domain.
  • Detailed Monitoring: Follow the evolution of a domain name and the entities that manage it in detail.
  • Auto-purchase Domain: You want the domain name of your dreams, but it is already taken? Domain Watchdog detects the deletion of the domain name on WHOIS and can trigger the purchase of the domain name via a provider's API

Although the RDAP and WHOIS protocols allow you to obtain precise information about a domain, it is not possible to perform a reverse search to discover a list of domain names associated with an entity. Additionally, accessing a detailed history of events (ownership changes, renewals, etc.) is not feasible with these protocols.

How it works?

The latest version of the WHOIS protocol was standardized in 2004 by RFC 3912.1 This protocol allows anyone to retrieve key information concerning a domain name, an IP address, or an entity registered with a registry.

ICANN launched a global vote in 2023 to propose replacing the WHOIS protocol with RDAP. As a result, registries and registrars will no longer be required to support WHOIS from 2025 (WHOIS Sunset Date).2

Domain Watchdog uses the RDAP protocol, which will soon be the new standard for retrieving information concerning domain names. The data is organized in a SQL database to minimize space by ensuring an entity is not repeated.

Connector Provider

A connector is a way to order a domain name. It is important to mention that this project does not act as a payment intermediary. Indeed, the user's credentials are directly used to enable the purchase via the provider's API. To this end, the user gives his consent to define the legal framework in which the use of his account with the provider's API will be made.

The table below lists the supported API connector providers:

Provider Documentation Supported
OVH https://api.ovh.com Yes
GANDI https://api.gandi.net/docs/domains/ Yes
NAMECHEAP https://www.namecheap.com/support/api/methods/domains/create/

Watchlist

A watchlist is a list of domain names, triggers and possibly an API connector. They allow you to follow the life of the listed domain names and send you a notification when a change has been detected.

If a domain has expired and a connector is linked to the Watchlist, then Domain Watchdog will try to order it via the connector provider's API.

Note: If the same domain name is present on several Watchlists, on the same principle as the raise condition, it is not possible to predict in advance which user will win the domain name. The choice is left to chance.

Useful documentation

Note

Disclaimer

Warning

  • Domain Watchdog is an opensource project distributed under GNU Affero General Public License v3.0 or later license
  • In the internal opration, everything is done to perform the least possible RDAP requests: rate limit, intelligent caching system, etc.
  • Please note that this project is NOT affiliated IN ANY WAY with the API Providers used to order domain names.
  • The project installers are responsible for the use of their own instance.
  • In no event the owner of this project will not be held responsible for other instances over which he has no control.

Licensing

This source code of this project is licensed under GNU Affero General Public License v3.0 or later. Contributions are welcome as long as they do not contravene the Code of Conduct.


  1. RFC 3912 : WHOIS Protocol Specification. (2004). IETF Datatracker. https://datatracker.ietf.org/doc/html/rfc3912 ↩︎

  2. 2023 Global Amendments to the Base gTLD Registry Agreement (RA), Specification 13, and 2013 Registrar Accreditation Agreement (RAA) - ICANN. (2023). https://www.icann.org/resources/pages/global-amendment-2023-en ↩︎

Description
An app that uses RDAP to collect publicly available info about domains, track their history, and purchase them
Readme AGPL-3.0 Cite this repository 9.7 MiB
Languages
PHP 69.4%
TypeScript 27.9%
Twig 1.4%
JavaScript 0.5%
Dockerfile 0.4%
Other 0.3%