diff --git a/docs/astro.config.mjs b/docs/astro.config.mjs index a895a1c..c4d364d 100644 --- a/docs/astro.config.mjs +++ b/docs/astro.config.mjs @@ -30,41 +30,48 @@ export default defineConfig({ {icon: 'seti:docker', label: 'Docker', href: 'https://hub.docker.com/r/maelgangloff/domain-watchdog'} ], sidebar: [ - {label: 'Getting started', slug: 'features'}, + {label: 'Getting started', slug: 'features', translations: {fr: 'Premiers pas'}}, { label: 'Installation & Configuration', + translations: {fr: 'Installation & Configuration'}, items: [ - {label: 'Installation', autogenerate: {directory: 'install-config/install'}}, + {label: 'Installation', autogenerate: {directory: 'install-config/install'}, translations: {fr: 'Installation'}}, {slug: 'install-config/configuration'}, {slug: 'install-config/upgrade'}, ] }, { label: 'Features', + translations: {fr: 'Fonctionnalités'}, items: [ {slug: 'features/search/domain-search'}, - {label: 'Domain back-order', autogenerate: {directory: 'features/backorder'}}, - {label: 'Domain tracking', autogenerate: {directory: 'features/tracking'}}, - {label: 'Infrastructure', autogenerate: {directory: 'features/infrastructure'}}, + {label: 'Domain back-order', autogenerate: {directory: 'features/backorder'}, translations: {fr: 'Achat automatisé'}}, + {label: 'Domain tracking', autogenerate: {directory: 'features/tracking'}, translations: {fr: 'Suivi des domaines'}}, + {label: 'Infrastructure', autogenerate: {directory: 'features/infrastructure'}, translations: {fr: 'Infrastructure'}}, ] }, { label: 'Developing', + translations: {fr: 'Développement'}, items: [ {slug: 'developing/technical-stack'}, {slug: 'developing/implementing-new-provider'}, {slug: 'developing/translation'}, - {label: 'Contributing', autogenerate: {directory: 'developing/contributing'}} + {label: 'Contributing', autogenerate: {directory: 'developing/contributing'}, translations: {fr: 'Contribuer'}} ], }, - {label: 'Legal', autogenerate: {directory: 'legal'}, collapsed: true}, - {slug: 'acknowledgment'}, - {label: 'Definitions', autogenerate: {directory: 'definitions'}, collapsed: true}, + {label: 'Legal', autogenerate: {directory: 'legal'}, collapsed: true, translations: {fr: 'Légal'}}, + {slug: 'acknowledgment', translations: {fr: 'Remerciements'}}, + {label: 'Definitions', autogenerate: {directory: 'definitions'}, collapsed: true, translations: {fr: 'Définitions'}}, ], locales: { en: { label: 'English', lang: 'en' + }, + fr: { + label: 'Français', + lang: 'fr' } }, head: [ @@ -133,8 +140,8 @@ _paq.push(['enableHeartBeatTimer']); }), starlightKbd({ types: [ - {id: 'mac', label: 'macOS', default: true}, - {id: 'windows', label: 'Windows'}, + {id: 'generic', label: 'Generic', default: true}, + {id: 'mac', label: 'macOS'} ], }), ], diff --git a/docs/src/content/docs/en/features/search/domain-search.mdx b/docs/src/content/docs/en/features/search/domain-search.mdx index 8db8ad1..09a91cf 100644 --- a/docs/src/content/docs/en/features/search/domain-search.mdx +++ b/docs/src/content/docs/en/features/search/domain-search.mdx @@ -17,7 +17,7 @@ To search for a domain name: 1. Enter the domain in the search bar. - 2. Press to submit the query. + 2. Press to submit the query. ![Search for a domain name](../../../../../assets/images/search-domain.png) @@ -29,6 +29,6 @@ If the extension you are searching for does **not** have an official RDAP server By default, if the domain information stored in the database is still considered valid, the system returns the existing record without performing a new RDAP query. If you need to force an RDAP update for a given domain: -* Press when submitting the search. +* Press when submitting the search. This triggers a fresh lookup against the RDAP server. diff --git a/docs/src/content/docs/fr/definitions/dns.mdx b/docs/src/content/docs/fr/definitions/dns.mdx new file mode 100644 index 0000000..57dda89 --- /dev/null +++ b/docs/src/content/docs/fr/definitions/dns.mdx @@ -0,0 +1,78 @@ +--- +title: Protocole DNS +description: Qu'est-ce que le DNS ? Comprendre le système de noms de domaine, comment il traduit les noms de domaine en adresses IP et son rôle dans la navigation Internet. +--- + +import {LinkCard} from "@astrojs/starlight/components"; + +Le **DNS (Domain Name System)** est le système de nommage décentralisé pour les ordinateurs, les services ou toute ressource connectée à Internet ou à un réseau privé. +Il agit comme "l'annuaire d'Internet", traduisant les noms de domaine lisibles par les humains en informations lisibles par les machines. + +## Une architecture hiérarchique + +L'architecture DNS est une base de données distribuée et hiérarchique ressemblant à un arbre inversé. Cette structure, connue sous le nom d'**Espace de Noms de Domaine** (Domain Name Space), est traitée de droite à gauche : + +[Image of DNS hierarchical structure] + + * **Niveau Racine (Root)** : Le sommet de la hiérarchie, représenté par un point unique optionnel (`.`) à la fin d'un nom de domaine complet (FQDN). + * **Domaines de premier niveau (TLD)** : Le niveau visible le plus élevé (par exemple, `.com`, `.org`, `.fr`). + * **Domaines de second niveau (SLD)** : Le nom spécifique enregistré par une entité (par exemple, `example` dans `example.com`). + * **Sous-domaines** : Subdivisions supplémentaires pour des services spécifiques ou des structures organisationnelles (par exemple, `www`, `blog` ou `api`). + +## Serveurs faisant autorité + +Les serveurs DNS faisant autorité détiennent les enregistrements de ressources définitifs pour une zone de domaine spécifique. Contrairement aux résolveurs récursifs qui mettent les réponses en cache, les serveurs faisant autorité fournissent les données originales. + +[Image of DNS resolution process] + +Lorsqu'un client demande un domaine, la chaîne de résolution interroge : + +1. **Serveurs Racines** : Dirigent vers les serveurs TLD. +2. **Serveurs TLD** : Dirigent vers les serveurs de noms faisant autorité du domaine. +3. **Serveur faisant autorité** : Renvoie l'adresse IP finale (ou un autre enregistrement). + + + +## Enregistrements GLUE + +Un enregistrement GLUE est un enregistrement A (ou AAAA) **fourni par la zone parente** pour éviter les dépendances circulaires. Normalement, la zone parente ne fait que déléguer, mais ici, elle doit fournir des données. +Ils sont strictement nécessaires lorsque le serveur de noms d'un domaine est un sous-domaine du domaine lui-même (par exemple, `example.com` utilise `ns1.example.com` comme serveur de noms). Sans l'enregistrement GLUE dans la zone `.com` pointant vers l'IP de `ns1`, le résolveur serait bloqué dans une boucle en essayant de résoudre le nom du serveur de noms. + +### Exemple : `ns.icann.org` + +Dans cet exemple, `icann.org` utilise `ns.icann.org` comme l'un de ses serveurs de noms. + +Pour résoudre `icann.org`, vous devez interroger `ns.icann.org`, mais vous ne pouvez pas trouver `ns.icann.org` sans d'abord résoudre `icann.org`. + +Lors de l'interrogation du serveur TLD `.org` (`A0.ORG.AFILIAS-NST.INFO`), le serveur renvoie les enregistrements de serveur de noms (NS) dans la **Section Autorité**, mais de manière cruciale, il fournit également les adresses IP dans la **Section Additionnelle**. Ce sont les enregistrements GLUE. + +```text title="Requête DNS de ns.icann.org utilisant la commande dig" {17-18} +; <<>> DiG 9.20.15 <<>> ns.icann.org @A0.ORG.AFILIAS-NST.INFO +;; global options: +cmd +;; Got answer: +;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52458 +;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 3 + +;; QUESTION SECTION: +;ns.icann.org. IN A + +;; AUTHORITY SECTION: +icann.org. 3600 IN NS ns.icann.org. +icann.org. 3600 IN NS a.icann-servers.net. +icann.org. 3600 IN NS c.icann-servers.net. +icann.org. 3600 IN NS b.icann-servers.net. + +;; ADDITIONAL SECTION: +ns.icann.org. 3600 IN A 199.4.138.53 +ns.icann.org. 3600 IN AAAA 2001:500:89::53 + +;; Query time: 241 msec +;; SERVER: 199.19.56.1#53(A0.ORG.AFILIAS-NST.INFO) (UDP) +``` + +## Voir aussi + + - [Domain Name System (Système de noms de domaine)](https://fr.wikipedia.org/wiki/Domain_Name_System) sur Wikipédia diff --git a/docs/src/content/docs/fr/definitions/dnssec.mdx b/docs/src/content/docs/fr/definitions/dnssec.mdx new file mode 100644 index 0000000..d1d7514 --- /dev/null +++ b/docs/src/content/docs/fr/definitions/dnssec.mdx @@ -0,0 +1,52 @@ +--- +title: DNSSEC +description: Sécurisez votre résolution de domaine. En savoir plus sur DNSSEC (Extensions de sécurité du système de noms de domaine) et comment il protège les utilisateurs contre les données DNS falsifiées. +--- + +import {LinkCard} from "@astrojs/starlight/components"; + +**DNSSEC (Domain Name System Security Extensions)** ajoute une couche de sécurité cryptographique au protocole DNS. Il défend contre des attaques spécifiques, telles que l'**empoisonnement du cache DNS** et les **attaques de l'homme du milieu**, en garantissant que les données DNS reçues sont identiques à celles publiées par le propriétaire de la zone. + +## Ce que fait DNSSEC + +DNSSEC utilise la cryptographie à clé publique pour établir une **Chaîne de Confiance**. + + * **Authentification de l'origine** : Vérifie que les données proviennent du bon serveur faisant autorité. + * **Intégrité des données** : Garantit que les données n'ont pas été modifiées en transit. + * **Déni d'existence authentifié** : Prouve de manière sécurisée qu'un domaine ou un enregistrement n'existe *pas* (en utilisant NSEC/NSEC3). + +De nouveaux enregistrements de ressources permettent cette validation : + + * `RRSIG` : La signature numérique associée à un jeu d'enregistrements. + * `DNSKEY` : La clé publique utilisée pour vérifier le RRSIG. + * `DS` (Delegation Signer) : Un hachage de la clé de la zone enfant, stocké dans la zone parente pour lier la chaîne de confiance. + +## Ce que DNSSEC ne fait pas + + * **Pas de chiffrement** : Les requêtes et réponses DNS restent en texte clair (contrairement à DoH ou DoT). + * **Pas de validation d'identité** : Il ne valide pas la légitimité du propriétaire du domaine (par exemple, il n'empêche pas les domaines de phishing, il prouve juste que l'IP du domaine de phishing est correcte). + +## Configurer DNSSEC sur votre nom de domaine + +La mise en œuvre de DNSSEC implique deux étapes principales : + +1. **Signature de la zone** : Le serveur de noms faisant autorité génère des clés (`ZSK` et `KSK`) et signe les données de la zone, créant des enregistrements `RRSIG` et `DNSKEY`. +2. **Établissement de la confiance** : Le propriétaire du domaine doit envoyer l'enregistrement `DS` (hachage de la KSK) au Bureau d'enregistrement (Registrar). Le Bureau d'enregistrement transmet cela au Registre pour publication dans la zone TLD parente. + + + +## L'adoption de DNSSEC + +L'adoption est un processus descendant commençant par la Zone Racine. Alors que la Racine et la plupart des TLD sont signés, l'adoption au niveau de l'utilisateur final (domaines de second niveau) dépend du support du bureau d'enregistrement et de la sensibilisation du titulaire. + + + +## Voir aussi + + - [Carte mondiale DNSSEC](https://stats.labs.apnic.net/dnssec) des laboratoires APNIC diff --git a/docs/src/content/docs/fr/definitions/domain-lifecycle.mdx b/docs/src/content/docs/fr/definitions/domain-lifecycle.mdx new file mode 100644 index 0000000..f5b54c3 --- /dev/null +++ b/docs/src/content/docs/fr/definitions/domain-lifecycle.mdx @@ -0,0 +1,42 @@ +--- +title: Cycle de vie d'un domaine +description: Explorez le cycle de vie d'un domaine, de l'enregistrement et du renouvellement à l'expiration et la rédemption. Connaissez les phases critiques pour gérer votre nom de domaine. +--- + +import {LinkCard} from "@astrojs/starlight/components"; + +Le **Cycle de vie d'un domaine** définit les statuts qu'un nom de domaine traverse de sa création à sa suppression. +Comprendre ces phases est critique pour éviter la perte involontaire d'un domaine. + +## Le cycle de vie générique + +Pour la plupart des domaines de premier niveau génériques (gTLD) régulés par l'ICANN, le cycle suit ce chemin : + +1. **Disponible** : Le domaine est ouvert à l'enregistrement. +2. **Enregistré (Actif)** : Le domaine est détenu et fonctionnel. Il peut être mis à jour, transféré ou renouvelé (généralement 1 à 10 ans). +3. **Période de grâce de renouvellement automatique** : (0–45 jours) Le domaine expire. Le propriétaire peut généralement le renouveler au tarif standard. Le domaine peut cesser de résoudre (ServerHold). +4. **Période de rédemption** : (30 jours) Le domaine est supprimé du bureau d'enregistrement mais conservé par le registre. La récupération est possible mais nécessite des **frais de restauration** plus élevés. +5. **Suppression en attente** (Pending Delete) : (5 jours) Le domaine est programmé pour une suppression définitive. Il ne peut être ni récupéré ni renouvelé. +6. **Libéré** : Le domaine devient à nouveau **Disponible** pour l'enregistrement public. + + + +## Cas particuliers de certains ccTLD + +Les domaines de premier niveau géographiques (ccTLD) fonctionnent selon des réglementations locales, ce qui conduit à des cycles de vie divers : + + * **Pas de périodes de grâce** : Certains ccTLD entrent en "Suppression en attente" immédiatement après l'expiration. + * **Renouvellement pré-expiration** : Certains registres exigent que les frais de renouvellement soient payés des semaines avant la date d'expiration réelle. + * **Processus manuels** : La restauration dans certains ccTLD peut nécessiter une intervention manuelle et de la paperasse. + +\ + +## Voir aussi + + - [Cycle de vie d'un nom de domaine gTLD typique](https://www.icann.org/en/contracted-parties/accredited-registrars/resources/gtld-lifecycle) sur le site de l'ICANN diff --git a/docs/src/content/docs/fr/definitions/domain-name.mdx b/docs/src/content/docs/fr/definitions/domain-name.mdx new file mode 100644 index 0000000..29062dc --- /dev/null +++ b/docs/src/content/docs/fr/definitions/domain-name.mdx @@ -0,0 +1,53 @@ +--- +title: Nom de domaine +description: Définissez votre identité en ligne. Une explication de ce qu'est un nom de domaine et de sa structure. +--- +Un **Nom de Domaine** est une chaîne d'identification lisible par l'homme utilisée pour localiser des ressources sur Internet. Il mappe des adresses IP numériques complexes vers des noms mémorables. + +## La structure d'un nom de domaine + +Un nom de domaine se lit hiérarchiquement de droite à gauche : + +1. **Domaine de premier niveau (TLD)** : Le suffixe (par exemple, `.com`, `.fr`). +2. **Domaine de second niveau (SLD)** : Le nom unique choisi par le titulaire (par exemple, `example`). +3. **Sous-domaine** : préfixes pour des services spécifiques (par exemple, `www`, `api`). + +Un **Nom de Domaine Complètement Qualifié (FQDN)** inclut tous les labels jusqu'à la racine (par exemple, `www.example.com.`). + +## Les statuts EPP + +Le protocole EPP (Extensible Provisioning Protocol) attribue des codes de statut aux domaines pour indiquer leur état ou des restrictions. Ceux-ci sont visibles dans les recherches WHOIS/RDAP. + +### Statuts serveur (définis par le registre) + +Le registre peut appliquer des codes EPP pour modifier l'état d'un nom de domaine. Ce sont tous les codes sauf ceux commençant par `client`, qui sont réservés aux bureaux d'enregistrement. +Les codes génériques sont listés dans la documentation de l'ICANN. + +Certains registres ont développé des codes supplémentaires pour décrire des cas non standard. +Par exemple, l'AFNIC a ajouté le code `server trade prohibited` pour décrire l'interdiction de l'opération de `trade` (cession) sur un nom de domaine. +Cette opération fait partie de l'extension EPP de l'AFNIC et n'est pas une opération standard pour un nom de domaine. + +### Statuts client (définis par le bureau d'enregistrement) + +Les bureaux d'enregistrement peuvent également appliquer des codes EPP à un nom de domaine. Ces codes commencent toujours par `client` pour les distinguer des codes appliqués par le registre. + +Certains codes ont le même effet que ceux appliqués par le registre. + +Par exemple, les codes `client hold` et `server hold` bloquent la résolution de la zone DNS d'un nom de domaine. +Cela signifie que la zone DNS du domaine de premier niveau ne contient plus les enregistrements `NS` nécessaires à la délégation de la zone du nom de domaine. +Cela entraîne l'arrêt complet des services pour le nom de domaine. +Ce code est souvent utilisé par le bureau d'enregistrement pour encourager fortement le titulaire à payer les frais de renouvellement (lorsque le nom de domaine n'est pas dans sa période de rédemption). + +## Nom de domaine internationalisé (IDN) + +Un IDN est un nom de domaine qui contient des caractères autres que le format ASCII standard (a-z, 0-9 et traits d'union). Cela inclut les caractères avec des diacritiques (accents) ou des caractères d'écritures non latines (arabe, chinois, cyrillique, etc.). + +Pour fonctionner dans le système DNS hérité, les IDN sont convertis dans un format compatible ASCII appelé **Punycode**, qui commence toujours par `xn--`. + +| Affichage | Punycode | +|:-----------------:|:------------------------:| +| `maëlgangloff.fr` | `xn--malgangloff-0bb.fr` | + +## Voir aussi + + - [Codes de statut EPP](https://icann.org/epp) sur le site de l'ICANN diff --git a/docs/src/content/docs/fr/definitions/epp.mdx b/docs/src/content/docs/fr/definitions/epp.mdx new file mode 100644 index 0000000..09fef0b --- /dev/null +++ b/docs/src/content/docs/fr/definitions/epp.mdx @@ -0,0 +1,44 @@ +--- +title: Protocole EPP +description: Qu'est-ce qu'un bureau d'enregistrement de noms de domaine ? Apprenez leur rôle dans la gestion de l'enregistrement et du transfert des noms de domaine pour le public. +--- + +import {LinkCard} from "@astrojs/starlight/components"; + +L'**Extensible Provisioning Protocol (EPP)** est le protocole de couche application standard pour l'allocation d'objets au sein des registres sur Internet. Bien qu'il soit principalement utilisé pour les noms de domaine, il peut également gérer les contacts et les objets hôtes. + +## Les acteurs + +### Client (Bureau d'enregistrement) + +Le Bureau d'enregistrement (Registrar) agit comme le Client EPP. Il envoie des commandes XML pour créer, mettre à jour, renouveler ou supprimer des noms de domaine en fonction des demandes des clients. + + + +### Serveur (Registre) + +Le Registre agit comme le Serveur EPP. Il traite les commandes, valide la logique (par exemple, "ce domaine est-il disponible ?"), met à jour la base de données centrale et renvoie des réponses de succès ou d'erreur. + + + +## Le mécanisme du protocole + +EPP utilise des messages **XML** transportés sur **TCP**, sécurisés par **TLS**. C'est un protocole à états, ce qui signifie qu'une session est établie (Connexion) avant que les commandes ne soient exécutées. + +Les commandes EPP courantes incluent : + + * `` : Vérifier la disponibilité. + * `` : Enregistrer un nouvel objet. + * `` : Récupérer les détails de l'objet. + * `` : Initier un transfert de bureau d'enregistrement. + * `` : Récupérer les notifications asynchrones du Registre. + +## Voir aussi + + - [RFC 5730 - Extensible Provisioning Protocol (EPP)](https://datatracker.ietf.org/doc/html/rfc5730) diff --git a/docs/src/content/docs/fr/definitions/icann.mdx b/docs/src/content/docs/fr/definitions/icann.mdx new file mode 100644 index 0000000..eaf4655 --- /dev/null +++ b/docs/src/content/docs/fr/definitions/icann.mdx @@ -0,0 +1,38 @@ +--- +title: ICANN +description: En savoir plus sur l'ICANN (Internet Corporation for Assigned Names and Numbers), l'organisation à but non lucratif coordonnant les identifiants uniques de l'Internet mondial. +--- + +import {LinkCard} from "@astrojs/starlight/components"; + +L'**ICANN (Internet Corporation for Assigned Names and Numbers)** est l'organisation à but non lucratif responsable de la coordination de la maintenance et de la sécurité des identifiants uniques de l'Internet mondial. + +L'ICANN agit comme le principal organe de gouvernance pour l'infrastructure technique du DNS. Ses responsabilités incluent : + + * **Fonctions IANA** : Gestion de l'allocation de l'espace d'adressage IP et de la Zone Racine du DNS. + * **Développement de politiques** : Faciliter la création de politiques mondiales pour le système de noms de domaine via un modèle multipartite. + +## Gestion des domaines de premier niveau + +L'ICANN décide quels nouveaux domaines de premier niveau (TLD) sont ajoutés à la Zone Racine. + + * Elle supervise le **Programme des nouveaux gTLD**, qui a étendu Internet de quelques douzaines d'extensions (comme `.com`) à plus de 1 000 (comme `.app`, `.shop`). + * Elle délègue les **ccTLD** (comme `.uk`, `.fr`) à des gestionnaires nationaux spécifiques, bien qu'elle ait moins de contrôle direct sur leurs politiques locales. + + + +## Accréditation des bureaux d'enregistrement + +L'ICANN gère le système d'accréditation pour les bureaux d'enregistrement souhaitant vendre des TLD génériques. L'accréditation garantit que les entreprises gérant les enregistrements de domaines respectent les normes de sécurité, de stabilité et de conservation des données. + + + +## Voir aussi + + - [Site officiel](https://www.icann.org/) diff --git a/docs/src/content/docs/fr/definitions/rdap.mdx b/docs/src/content/docs/fr/definitions/rdap.mdx new file mode 100644 index 0000000..1687c4e --- /dev/null +++ b/docs/src/content/docs/fr/definitions/rdap.mdx @@ -0,0 +1,29 @@ +--- +title: Protocole RDAP +description: Le protocole d'accès aux données moderne. Comprendre RDAP (Registration Data Access Protocol) pour un accès fiable et structuré aux données d'enregistrement et de propriété des domaines. +--- + +import {LinkCard} from "@astrojs/starlight/components"; + +Le **RDAP (Registration Data Access Protocol)** est la norme moderne pour accéder aux données d'enregistrement. Il a été conçu pour remplacer l'ancien protocole WHOIS en remédiant à son manque de standardisation et de sécurité. + +## Améliorations clés par rapport à WHOIS + + * **Données structurées (JSON)** : Contrairement à WHOIS, qui renvoie du texte libre non structuré, RDAP renvoie des données au format JSON. Cela permet une analyse automatisée facile et un affichage cohérent par les clients. + * **Requêtes standardisées** : RDAP utilise des services web RESTful (HTTP/HTTPS). + * **Internationalisation** : Support natif des caractères non latins (IDN). + * **Accès différencié** : RDAP prend en charge l'authentification, permettant aux registres d'afficher des données limitées au public (conformité RGPD) tout en fournissant des données complètes aux autorités accréditées. + + + +## État du déploiement + +L'ICANN rend obligatoire la mise en œuvre de RDAP pour tous les bureaux d'enregistrement accrédités et les registres gTLD. +Alors que WHOIS est encore largement utilisé par les systèmes hérités, RDAP est la source faisant autorité pour les données d'enregistrement gTLD. L'adoption parmi les ccTLD est volontaire et en cours. + +## Voir aussi + + - [Tableau de bord de déploiement RDAP](https://deployment.rdap.org) diff --git a/docs/src/content/docs/fr/definitions/registrar.mdx b/docs/src/content/docs/fr/definitions/registrar.mdx new file mode 100644 index 0000000..276792f --- /dev/null +++ b/docs/src/content/docs/fr/definitions/registrar.mdx @@ -0,0 +1,36 @@ +--- +title: Bureau d'enregistrement +description: Qu'est-ce qu'un bureau d'enregistrement de noms de domaine ? Apprenez leur rôle dans la gestion de l'enregistrement et du transfert des noms de domaine pour le public. +--- + +import {LinkCard} from "@astrojs/starlight/components"; + +Un **Bureau d'enregistrement** (Registrar) est une entité commerciale accréditée qui vend des enregistrements de noms de domaine au public. Il agit comme intermédiaire entre le Titulaire (le propriétaire du domaine) et le Registre (l'opérateur de la base de données). + + + +## Responsabilités principales + +### Gestion administrative + + * **Enregistrement & Renouvellement** : Gestion de l'achat et du renouvellement périodique des domaines. + * **Gestion du cycle de vie** : Gestion des périodes de grâce, des frais de rédemption et des transferts. + * **Précision des données** : Collecte et maintien d'informations de contact précises pour les répertoires WHOIS/RDAP. + +### Services techniques + + * **Interface EPP** : Traduction des actions de l'utilisateur en commandes EPP envoyées au Registre. + * **Hébergement DNS** : La plupart des bureaux d'enregistrement fournissent des serveurs de noms par défaut, permettant aux utilisateurs de gérer leurs enregistrements DNS (A, MX, CNAME) via un tableau de bord convivial. + * **DNSSEC** : Facilitation de la rotation et de la publication des enregistrements DS. + + + +## Voir aussi + + - [Bureau d'enregistrement (Domain name registrar)](https://fr.wikipedia.org/wiki/Registrar) sur Wikipédia diff --git a/docs/src/content/docs/fr/definitions/registry.mdx b/docs/src/content/docs/fr/definitions/registry.mdx new file mode 100644 index 0000000..55594e2 --- /dev/null +++ b/docs/src/content/docs/fr/definitions/registry.mdx @@ -0,0 +1,33 @@ +--- +title: Registre +description: Comprendre le registre de noms de domaine. Apprenez comment ces organisations gèrent la base de données centrale pour tous les noms de domaine sous un TLD spécifique. +--- + +import {LinkCard} from "@astrojs/starlight/components"; + +Un **Registre** (ou Opérateur de Registre) est l'organisation responsable de la maintenance de la base de données maître de tous les noms de domaine enregistrés sous un domaine de premier niveau (TLD) spécifique. + +## Rôles techniques + +Le Registre est la source faisant autorité pour son TLD. Ses devoirs incluent : + + * **Génération du fichier de zone** : Publication du fichier de zone qui dirige le trafic DNS mondial vers les bons serveurs de noms pour chaque domaine de l'extension. + * **Gestion IDN & DNSSEC** : Application des politiques pour les caractères spéciaux et gestion de la signature cryptographique de la zone TLD. + * **Serveur WHOIS/RDAP** : Exploitation du service d'annuaire qui fournit des informations publiques sur les domaines enregistrés. + +## Rôles opérationnels + +Les registres ne vendent généralement pas directement au public. Au lieu de cela, ils : + + * Définissent les **Politiques d'Utilisation Acceptable** pour le TLD. + * Fixent le prix de gros pour les domaines. + * Accréditent et se connectent avec les **Bureaux d'enregistrement** via EPP. + + + +## Voir aussi + + - [Registre de noms de domaine](https://fr.wikipedia.org/wiki/Registre_de_noms_de_domaine) sur Wikipédia diff --git a/docs/src/content/docs/fr/definitions/top-level-domain.mdx b/docs/src/content/docs/fr/definitions/top-level-domain.mdx new file mode 100644 index 0000000..89d65ad --- /dev/null +++ b/docs/src/content/docs/fr/definitions/top-level-domain.mdx @@ -0,0 +1,50 @@ +--- +title: Domaine de premier niveau (TLD) +description: Un aperçu des domaines de premier niveau (TLD), leur classification (gTLD, ccTLD, etc.) et la structure de la zone racine DNS. +--- + +Un **Domaine de premier niveau (TLD)** est le segment le plus à droite d'un nom de domaine (après le dernier point). Les TLD sont le niveau le plus élevé de la hiérarchie DNS en dessous de la racine. + +## Classifications des TLD + +### TLD Générique (gTLD) + +Initialement destinés à des cas d'utilisation spécifiques, la plupart des gTLD sont maintenant ouverts à tous. + + * **Hérités** : `.com` (commercial), `.net` (réseau), `.org` (organisation). + * **Nouveaux gTLD** : Des milliers d'extensions de niche comme `.app`, `.blog`, `.guru`. + * **Restreints** : Les domaines comme `.bank` ou `.pharmacy` nécessitent une vérification d'éligibilité. + * **Marque** : TLD fermés pour les entreprises, par exemple, `.google` ou `.bmw`. + +### TLD Code Pays (ccTLD) + +Réservés aux pays et territoires (deux lettres, basées sur ISO 3166). + + * **Exemples** : `.uk` (Royaume-Uni), `.de` (Allemagne), `.io` (Territoire britannique de l'océan Indien). + * **Règles** : Les politiques varient strictement selon les pays. Certains exigent une résidence locale (par exemple, `.no`, `.ca`), tandis que d'autres sont commercialisés mondialement (par exemple, `.tv`, `.ai`). + +### TLD Sponsorisé (sTLD) + +Gérés par des organisations privées représentant une communauté spécifique. + + * `.gov` (Gouvernement américain) + * `.edu` (Institutions américaines accréditées) + * `.aero` (Industrie aéronautique) + +### TLD d'infrastructure + + * `.arpa` : Géré par l'IANA, utilisé exclusivement pour l'infrastructure technique (par exemple, les recherches DNS inverses). + +## TLD réservés + +Selon la [RFC 2606](https://tools.ietf.org/html/rfc2606), quatre TLD sont réservés en permanence pour les tests et la documentation afin d'éviter toute confusion dans les environnements de production : + + * `.test` + * `.example` + * `.invalid` + * `.localhost` + +## Voir aussi + + - [Domaine de premier niveau (Wikipédia)](https://fr.wikipedia.org/wiki/Domaine_de_premier_niveau) + - [Base de données de la zone racine IANA](https://www.iana.org/domains/root/db) diff --git a/docs/src/content/docs/fr/definitions/whois.mdx b/docs/src/content/docs/fr/definitions/whois.mdx new file mode 100644 index 0000000..5a5b992 --- /dev/null +++ b/docs/src/content/docs/fr/definitions/whois.mdx @@ -0,0 +1,97 @@ +--- +title: Protocole WHOIS +description: Obtenez un aperçu de WHOIS. Apprenez comment ce protocole est utilisé pour interroger des bases de données afin d'obtenir des informations sur l'utilisateur enregistré ou les attributaires d'un nom de domaine. +--- + +import {LinkCard} from "@astrojs/starlight/components"; + +WHOIS est un protocole de requête/réponse basé sur du texte (écoutant sur le **Port TCP 43**) largement utilisé pour interroger des bases de données qui stockent les utilisateurs enregistrés ou les attributaires d'une ressource Internet, telle qu'un nom de domaine ou un bloc d'adresses IP. + +## Cas d'utilisation principaux + + * **Vérification de la disponibilité** : Vérifier si un nom de domaine spécifique est disponible à l'enregistrement. + * **Identification de la propriété** : Identifier le Titulaire ou le Bureau d'enregistrement gérant le domaine. + * **Dépannage technique** : Trouver les serveurs de noms faisant autorité ou les contacts techniques pour résoudre les problèmes de réseau. + * **Juridique & Abus** : Fournir un dossier pour l'application de la loi, la protection de la propriété intellectuelle et le signalement des abus. + +## Registres Thick (Lourd) vs Thin (Léger) + +Comprendre les réponses WHOIS nécessite de comprendre comment le Registre TLD stocke les données. + +### Registre Thin (par exemple, .com, .net) + +Le Registre ne stocke que des données techniques (DNSSEC, serveurs de noms) et un pointeur vers le Bureau d'enregistrement. + +Pour obtenir les coordonnées complètes, une seconde requête WHOIS doit être envoyée au **serveur WHOIS du Bureau d'enregistrement**. + +### Registre Thick (par exemple, .org, .info, la plupart des ccTLD) + +Le Registre stocke *toutes* les informations, y compris les coordonnées du Titulaire et les données administratives. + +Une seule requête au Registre fournit l'enregistrement complet. + +## Exemple : Requête WHOIS récursive + +L'outil de ligne de commande standard `whois` gère souvent automatiquement la redirection du "Registre Thin". +Cependant, voir les étapes brutes aide à comprendre le protocole. + +Dans l'exemple ci-dessous pour un **TLD Thin** (`.com`), nous interrogeons d'abord le Registre, qui nous dirige vers le Bureau d'enregistrement. + +### Requête au Registre (Verisign) + +Notez le champ `Registrar WHOIS Server` dans la réponse. + +```text title="Requête WHOIS au Registre" +$ whois --verbose example.com -h whois.verisign-grs.com. +Using server whois.verisign-grs.com.. +Query string: "example.com" + + Domain Name: EXAMPLE.COM + Registry Domain ID: 2336799_DOMAIN_COM-VRSN + Registrar WHOIS Server: whois.iana.org + Registrar URL: http://res-dom.iana.org + Updated Date: 2025-08-14T07:01:39Z + Creation Date: 1995-08-14T04:00:00Z + Registry Expiry Date: 2026-08-13T04:00:00Z + Registrar: RESERVED-Internet Assigned Numbers Authority + Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited + Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited + Name Server: A.IANA-SERVERS.NET + Name Server: B.IANA-SERVERS.NET + DNSSEC: signedDelegation +>>> Last update of whois database: 2025-11-20T08:05:54Z <<< +``` + +### Requête au Bureau d'enregistrement (IANA) + +Suite au renvoi, nous interrogeons le Bureau d'enregistrement spécifique pour obtenir les détails de propriété. + +```text title="Requête WHOIS au Bureau d'enregistrement" +$ whois --verbose example.com -h whois.iana.org +Using server whois.iana.org.. +Query string: "example.com" + +% IANA WHOIS server +% for more information on IANA, visit http://www.iana.org +% This query returned 1 object + +domain: EXAMPLE.COM +organisation: Internet Assigned Numbers Authority +created: 1992-01-01 +source: IANA +``` + +## Considérations de confidentialité + +Depuis la mise en œuvre du **RGPD** (Règlement Général sur la Protection des Données) et des lois mondiales similaires sur la confidentialité, la sortie WHOIS a considérablement changé. + + * **Rédaction des données** : La plupart des champs personnels (Nom, Email, Téléphone) sont désormais remplacés par des espaces réservés comme `DATA REDACTED` ou `Redacted for Privacy`. + * **Proxies de confidentialité** : Les bureaux d'enregistrement fournissent souvent des services qui remplacent les détails du titulaire par les coordonnées génériques du bureau d'enregistrement pour empêcher le spam et le harcèlement. + * **Accès par niveaux** : Les données complètes et non rédigées ne sont souvent plus accessibles publiquement de manière anonyme et nécessitent une demande légale légitime ou une accréditation. + + + +## Voir aussi + + * [RFC 3912 - Spécification du protocole WHOIS](https://datatracker.ietf.org/doc/html/rfc3912) diff --git a/docs/src/content/docs/fr/features/backorder/connector.mdx b/docs/src/content/docs/fr/features/backorder/connector.mdx new file mode 100644 index 0000000..60bc09a --- /dev/null +++ b/docs/src/content/docs/fr/features/backorder/connector.mdx @@ -0,0 +1,39 @@ +--- +title: Connecteurs +description: Découvrez comment fonctionne un Connecteur, ses prérequis et comment il s'intègre aux API des bureaux d'enregistrement. +--- + +import {LinkCard, Steps} from '@astrojs/starlight/components'; + +Un Connecteur permet à Domain Watchdog de communiquer avec l'API d'un bureau d'enregistrement (registrar) pour effectuer des actions telles que l'enregistrement de domaine. + +## Créer un Connector + + +1. Choisissez un fournisseur d'API externe dans la liste des bureaux d'enregistrement supportés. + + +2. Saisissez les informations requises en utilisant les identifiants obtenus depuis l'espace client de votre fournisseur. + :::tip{icon="heart"} + Un lien vous permet d'accéder directement à la page du fournisseur pour récupérer ces informations d'authentification. + ::: + +3. Examinez et acceptez les conditions requises. Pour rappel, vous pouvez supprimer un Connecteur à tout moment depuis votre espace personnel. + +4. Cliquez sur le bouton pour créer votre Connecteur. **Félicitations 🎉** + + +## Considérations juridiques + +Ces exigences légales garantissent que toutes les opérations sur les domaines sont conformes aux politiques des bureaux d'enregistrement et aux réglementations applicables. + +Domain Watchdog agit uniquement en tant qu'interface technique et ne sert pas d'intermédiaire de paiement. +Vos identifiants sont transmis directement à l'API du fournisseur pour les opérations sur les domaines. +En créant un Connecteur, vous consentez aux conditions du fournisseur et à l'utilisation de vos identifiants pour les opérations autorisées. + +En particulier, vous devez consentir à ces élements : + + - Accepter les conditions d'utilisation de l'API du fournisseur + - Confirmer que vous avez l'âge légal pour accepter ces conditions + +Les conditions d'utilisation pouvant changer à tout moment, le lien vers ces conditions est toujours accessible sur la page listant les Connecteurs. diff --git a/docs/src/content/docs/fr/features/backorder/supported-registrar.mdx b/docs/src/content/docs/fr/features/backorder/supported-registrar.mdx new file mode 100644 index 0000000..2a330c2 --- /dev/null +++ b/docs/src/content/docs/fr/features/backorder/supported-registrar.mdx @@ -0,0 +1,108 @@ +--- +title: Liste des registrars supportés +description: Liste des bureaux d'enregistrement supportés pour la récupération de domaines, avec détails sur la compatibilité. +--- + +import {LinkButton} from '@astrojs/starlight/components'; + +:::caution[Rappel] + * Veuillez noter que ce projet N'EST PAS affilié aux fournisseurs d'API utilisés pour commander des noms de domaine. + * Les installeurs du projet sont responsables de l'utilisation de leur propre instance. + * En aucun cas, le mainteneur de ce projet ne pourra être tenu responsable d'autres cas sur lesquels il n'a aucun contrôle. +::: + +## OVH + +| Champ | Description | Requis | +|----------------|-------------------------------------------------------------------------------------------------|:------:| +| App key | La clé qui permet à OVH d'identifier votre application | Requis | +| App secret key | La clé secrète associée à votre application | Requis | +| Consumer key | La clé secrète qui lie l'application à votre compte | Requis | +| Endpoint | Permet de choisir quel serveur utiliser (Europe, États-Unis ou Canada) | Requis | +| Subsidiary | Le pays lié à la filiale OVH associée à votre compte | Requis | +| Pricing mode | Choisissez si vous voulez payer pour un nom de domaine Premium ou uniquement les prix standards | Requis | + + + Récupérer mon token sur le site d'OVH + + +## Gandi + +| Champ | Description | Requis | +|------------|------------------------------------------------------------|:---------:| +| Token | Le token d'authentification de votre compte | Requis | +| Sharing ID | Indique l'organisation qui paiera pour le produit commandé | Optionnel | + + + Récupérer mon token sur le site de Gandi + + +## Namecheap + +:::caution +Ce fournisseur exige que l'adresse IPv4 de votre instance soit renseignée sur son interface web lors de la création de la connexion API. Cette information doit également être saisie dans la configuration. +::: + +| Champ | Description | Requis | +|----------|------------------------------------------------------|:--------:| +| API user | L'utilisateur API tel que donné par le Fournisseur | Requis | +| API key | La clé API telle que donnée par le Fournisseur | Requis | + + + Récupérer mon token sur le site de Namecheap + + +## AutoDNS + +:::caution +Ce fournisseur ne fournit pas de liste des TLD supportés. Merci de vérifier si le domaine que vous souhaitez enregistrer est supporté. +::: + +| Champ | Description | Requis | +|---------------|--------------------------------------------------------------|:--------:| +| Username | Le nom d'utilisateur du compte | Requis | +| Password | Le mot de passe du compte | Requis | +| Owner consent | Consentement d'achat | Requis | +| Context | Le "contexte" tel que donné par le Fournisseur | Requis | +| Contact ID | ID de contact du titulaire des noms de domaine achetés | Requis | + + + Récupérer mon token sur le site d'AutoDNS + + +## Name.com + +:::caution +Ce fournisseur ne fournit pas de liste des TLD supportés. Merci de vérifier si le domaine que vous souhaitez enregistrer est supporté. +::: + +| Champ | Description | Requis | +|----------|---------------------------------------------|:--------:| +| Username | Le nom d'utilisateur du compte | Requis | +| Token | Le token d'authentification de votre compte | Requis | + + + Récupérer mon token sur le site de Name.com + + +## Serveur EPP personnalisé + +Ce type de connecteur vous permet de lier directement votre instance à un registre via le protocole EPP. +Cela nécessite que vous ayez signé un contrat avec un registre ; vous êtes alors considéré comme un bureau d'enregistrement à part entière. + +Actuellement, l'implémentation de cette fonctionnalité n'a pas été testée ; vos retours sont importants ! diff --git a/docs/src/content/docs/fr/features/index.mdx b/docs/src/content/docs/fr/features/index.mdx new file mode 100644 index 0000000..f74fbb1 --- /dev/null +++ b/docs/src/content/docs/fr/features/index.mdx @@ -0,0 +1,100 @@ +--- +title: Premiers pas +description: Guide étape par étape pour créer un compte, rechercher des domaines, suivre les changements et activer l'achat automatique avec les Connecteurs. +--- + +import {LinkCard, Steps} from '@astrojs/starlight/components'; + +Sur cette page, vous trouverez un guide étape par étape pour débuter avec **Domain Watchdog** et explorer ses principales fonctionnalités. +Le menu latéral de gauche vous permet de naviguer rapidement entre toutes les sections. + +:::note +Selon la configuration de l'instance sur laquelle vous effectuez ces actions, certaines options peuvent être limitées ou masquées. +::: + +----- + +## Créer un compte + +Si votre instance autorise l'inscription des utilisateurs, vous pouvez créer un compte directement depuis l'interface. + + +1. Cliquez sur le bouton **S'inscrire**. +2. Saisissez votre **adresse email** et votre **mot de passe**. +3. Un email de confirmation sera envoyé pour vérifier votre adresse. + + +Après avoir confirmé votre email, vous pouvez vous connecter et commencer à utiliser toutes les fonctionnalités disponibles. + +----- + +## Rechercher un nom de domaine + +Domain Watchdog utilise le **protocole RDAP**, en remplacement de WHOIS, pour récupérer des informations sur les noms de domaine. + +:::tip[En savoir plus] +Pour lire la documentation relative à la recherche de noms de domaine, vous pouvez cliquer sur le lien ci-dessous. + + +::: + +----- + +## Créer une Watchlist + +Une **Watchlist** est une collection de noms de domaine, de déclencheurs et optionnellement d'un Connecteur API. +Elle vous permet de : + + - surveiller les changements d'état des domaines + - recevoir des notifications (email ou webhook : Slack, Mattermost, Discord, etc.) + - acheter automatiquement (optionnel) un domaine lorsqu'il expire + +:::tip[En savoir plus] +Pour lire la documentation relative à la Watchlist, veuillez cliquer sur le lien ci-dessous. + + +::: + +### Notifications de la Watchlist + +Lorsqu'un domaine change d'état, vous recevrez automatiquement une notification. +Vous pouvez également exporter les événements de domaine sous forme de flux **iCalendar**. + +----- + +## Créer un Connecteur + +Un **Connecteur** est utilisé pour commander automatiquement (backorder) un nom de domaine en utilisant l'API de son fournisseur. + +:::tip[En savoir plus] +Pour lire la documentation relative au Connecteur, vous pouvez cliquer sur le lien ci-dessous. + + +::: + +### Liste des registrars supportés + + + +----- + +### Tableau de suivi + +La page du Tableau de suivi affiche une liste de tous les noms de domaine que vous surveillez via vos Watchlists. +Cette liste est ordonnée, ce qui signifie que les noms de domaine sont classés selon leur date de suppression estimée. + +:::tip[En savoir plus] +Pour lire la documentation relative au Tableau de suivi, vous pouvez cliquer sur le lien ci-dessous. + + +::: diff --git a/docs/src/content/docs/fr/features/infrastructure/icann-registrar-list.mdx b/docs/src/content/docs/fr/features/infrastructure/icann-registrar-list.mdx new file mode 100644 index 0000000..3b8d27c --- /dev/null +++ b/docs/src/content/docs/fr/features/infrastructure/icann-registrar-list.mdx @@ -0,0 +1,4 @@ +--- +title: Liste des registrars de l'ICANN +--- + diff --git a/docs/src/content/docs/fr/features/infrastructure/tld-list.mdx b/docs/src/content/docs/fr/features/infrastructure/tld-list.mdx new file mode 100644 index 0000000..dd4c862 --- /dev/null +++ b/docs/src/content/docs/fr/features/infrastructure/tld-list.mdx @@ -0,0 +1,3 @@ +--- +title: Liste des TLD +--- diff --git a/docs/src/content/docs/fr/features/search/domain-search.mdx b/docs/src/content/docs/fr/features/search/domain-search.mdx new file mode 100644 index 0000000..9fae769 --- /dev/null +++ b/docs/src/content/docs/fr/features/search/domain-search.mdx @@ -0,0 +1,33 @@ +--- +title: Recherche de noms de domaine +description: Aperçu de la fonctionnalité de recherche de domaine +--- + +import {Steps} from "@astrojs/starlight/components" +import {Kbd} from "starlight-kbd/components" + +:::tip[Le saviez-vous ?] +Dans ce projet, tout est fait pour minimiser le nombre de requêtes vers les serveurs RDAP. Des limitations imposées aux utilisateurs finaux aident à contrôler le flux de requêtes RDAP. +Ces limitations peuvent être configurées pour chaque instance, dans les variables d'environnement. +::: + +La fonctionnalité de recherche de domaine permet aux utilisateurs de consulter des informations sur un nom de domaine via l'interface utilisateur. + +Pour rechercher un nom de domaine : + + +1. Saisissez le domaine dans la barre de recherche. +2. Appuyez sur pour soumettre la requête. + + +Si l'extension que vous recherchez ne possède pas de serveur RDAP officiel, un message d'erreur vous informera qu'aucun serveur RDAP n'est disponible. + +## Mise à jour forcée + +Par défaut, si les informations du domaine stockées dans la base de données sont toujours considérées comme valides, le système renvoie l'enregistrement existant sans effectuer de requête RDAP. + +Si vous devez forcer une mise à jour RDAP pour un domaine donné : + + * Appuyez sur lors de la recherche. + +Cela déclenche une nouvelle requête auprès du serveur RDAP. diff --git a/docs/src/content/docs/fr/features/tracking/tracking-table.mdx b/docs/src/content/docs/fr/features/tracking/tracking-table.mdx new file mode 100644 index 0000000..a24f913 --- /dev/null +++ b/docs/src/content/docs/fr/features/tracking/tracking-table.mdx @@ -0,0 +1,5 @@ +--- +title: Tableau de suivi +--- + +![Tableau de suivi](../../../../../assets/images/tracking-table.png) diff --git a/docs/src/content/docs/fr/features/tracking/watchlist.mdx b/docs/src/content/docs/fr/features/tracking/watchlist.mdx new file mode 100644 index 0000000..30b9cba --- /dev/null +++ b/docs/src/content/docs/fr/features/tracking/watchlist.mdx @@ -0,0 +1,31 @@ +--- +title: Watchlist +description: Découvrez comment fonctionne une Watchlist de domaines, permettant aux utilisateurs de suivre des domaines et de recevoir des mises à jour sur les changements. +--- + +import {Steps} from '@astrojs/starlight/components'; + +Une Watchlist est une liste de noms de domaine, de déclencheurs et éventuellement d'un connecteur API. +Elles vous permettent de suivre le cycle de vie des noms de domaine listés et de vous envoyer une notification lorsqu'un changement a été détecté. + +Si un domaine a expiré et qu'un connecteur est lié à la Watchlist, une tentative de commande sera alors effectuée via l'API du bureau d'enregistrement associé au Connecteur. + +:::note +Si le même nom de domaine est présent sur plusieurs Watchlist, il n'est pas possible de prédire à l'avance quel utilisateur remportera le nom de domaine. Le choix est laissé au hasard... +::: + +## Créer une Watchlist + + +1. Choisissez un nom pour votre Watchlist afin de la retrouver plus facilement. +2. Ajoutez les noms de domaine que vous souhaitez suivre. +3. Sélectionnez les événements pour lesquels vous souhaitez recevoir une notification par email. +4. Ajoutez optionnellement un connecteur pour tenter d'acheter automatiquement un nom de domaine qui devient disponible. +5. Cliquez sur le bouton pour créer votre Watchlist. **Félicitations 🎉** + + +Maintenant, c'est à votre tour de créer une Watchlist ! + +## Limitations + +Selon la configuration de l'instance, il existe plusieurs limitations pour encadrer le comportement des utilisateurs. diff --git a/docs/src/content/docs/fr/index.mdx b/docs/src/content/docs/fr/index.mdx new file mode 100644 index 0000000..445393d --- /dev/null +++ b/docs/src/content/docs/fr/index.mdx @@ -0,0 +1,17 @@ +--- +title: Domain Watchdog +description: Une app qui utilise RDAP pour collecter les données publiques à propos des noms de domaines, les suivres et les acheter dès qu'ils deviennent disponibles +template: splash +hero: + tagline: Votre compagnon dans la quête de noms de domaines 🔍 + image: + file: ../../../assets/logo.png + actions: + - text: Get started + link: /en/features + icon: right-arrow + - text: Demo + link: https://demo.domainwatchdog.eu + icon: external + variant: minimal +--- diff --git a/docs/src/content/docs/fr/install-config/configuration.mdx b/docs/src/content/docs/fr/install-config/configuration.mdx new file mode 100644 index 0000000..878609e --- /dev/null +++ b/docs/src/content/docs/fr/install-config/configuration.mdx @@ -0,0 +1,42 @@ +--- +title: Configuration +description: Guide de configuration expliquant les variables d'environnement et les paramètres nécessaires pour lancer et personnaliser le projet. +--- + +import {LinkCard} from '@astrojs/starlight/components'; + + + +## Variables d'environnement + +| Variable | Description | Défaut | +|--------------------------------|---------------------------------------------------------|:---------------------------:| +| `DATABASE_URL` | Lire la documentation Symfony | | +| `OUTGOING_IP` | IPv4 sortante, requise par certains fournisseurs | | +| `INFLUXDB_ENABLED` | Activer la connexion avec InfluxDB | `false` | +| `INFLUXDB_URL` | URL InfluxDB | `http://localhost:8086` | +| `INFLUXDB_TOKEN` | Jeton (Token) InfluxDB | | +| `INFLUXDB_BUCKET` | Nom du bucket InfluxDB | `domainwatchdog` | +| `INFLUXDB_ORG` | Organisation InfluxDB | `domainwatchdog` | +| `LIMITED_FEATURES` | Limiter certaines fonctionnalités pour les utilisateurs | `false` | +| `LIMIT_MAX_WATCHLIST` | Nombre max. de listes de surveillance par utilisateur | `0` | +| `LIMIT_MAX_WATCHLIST_DOMAINS` | Nombre max. de domaines par liste de surveillance | `0` | +| `LIMIT_MAX_WATCHLIST_WEBHOOKS` | Nombre max. de webhooks par liste de surveillance | `0` | +| `MAILER_SENDER_NAME` | Nom de l'expéditeur des e-mails | `Domain Watchdog` | +| `MAILER_SENDER_EMAIL` | Adresse e-mail de l'expéditeur | `notifications@example.com` | +| `REGISTRATION_ENABLED` | Activer l'inscription des utilisateurs | `true` | +| `REGISTRATION_VERIFY_EMAIL` | Vérifier les e-mails lors de l'inscription | `false` | +| `MAILER_DSN` | Lire la documentation Symfony | `null://null` | +| `OAUTH_CLIENT_ID` | ID Client (OAuth 2.0) pour le SSO externe | | +| `OAUTH_CLIENT_SECRET` | Secret Client (OAuth 2.0) | | +| `OAUTH_AUTHORIZATION_URL` | URL d'autorisation (OAuth 2.0) | | +| `OAUTH_TOKEN_URL` | URL de jeton (OAuth 2.0) | | +| `OAUTH_USERINFO_URL` | URL des informations utilisateur (OAuth 2.0) | | +| `OAUTH_SCOPE` | Scope (OAuth 2.0) | | + + +## Authentification + +Actuellement, il n'est pas possible de supprimer votre compte, de réinitialiser votre mot de passe ou d'activer l'authentification multifacteur. + +L'inscription directe des utilisateurs dans l'interface est recommandée pour les instances individuelles. Pour les environnements multi-utilisateurs, la méthode recommandée est d'utiliser un SSO externe via le protocole OAuth 2.0. diff --git a/docs/src/content/docs/fr/install-config/install/docker-compose.mdx b/docs/src/content/docs/fr/install-config/install/docker-compose.mdx new file mode 100644 index 0000000..1d56c9b --- /dev/null +++ b/docs/src/content/docs/fr/install-config/install/docker-compose.mdx @@ -0,0 +1,25 @@ +--- +title: Installation Docker Compose +description: Guide pour installer le projet en utilisant Docker Compose, avec les étapes de configuration et les notes de déploiement. +--- + +import {LinkCard} from '@astrojs/starlight/components'; + +1. Téléchargez le fichier [docker-compose.yml](https://github.com/maelgangloff/domain-watchdog/blob/develop/docker-compose.yml) et modifiez-le selon vos besoins +2. Téléchargez le fichier [.env](https://github.com/maelgangloff/domain-watchdog/blob/develop/.env) et modifiez-le selon vos besoins + + +3. Ajoutez des fichiers statiques pour personnaliser votre instance (sous `public/content`) +4. Récupérez la dernière version de l'image Domain Watchdog depuis Docker Hub + +```shell +docker compose pull +``` + +5. Démarrez le projet en environnement de production + +```shell +docker compose up +``` + +Par défaut, le conteneur écoute sur http://localhost:8080, mais vous pouvez configurer cela dans les variables d'environnement. diff --git a/docs/src/content/docs/fr/install-config/install/manual-install.mdx b/docs/src/content/docs/fr/install-config/install/manual-install.mdx new file mode 100644 index 0000000..c0211c6 --- /dev/null +++ b/docs/src/content/docs/fr/install-config/install/manual-install.mdx @@ -0,0 +1,86 @@ +--- +title: Installation manuelle +description: Guide d'installation manuelle avec les prérequis système, les dépendances et les instructions étape par étape pour installer le projet depuis la source. +--- + +import {FileTree, LinkCard, Steps} from '@astrojs/starlight/components'; + +Pour déployer une instance Domain Watchdog, veuillez vous référer à la documentation Symfony sur [Comment déployer une application Symfony](https://symfony.com/doc/current/deployment.html). + +## Prérequis + +- PHP 8.4 ou supérieur +- PostgreSQL 16 ou supérieur + +Afin de récupérer des informations sur les noms de domaine, Domain Watchdog interrogera le serveur RDAP responsable du TLD. +Il est crucial que l'instance Domain Watchdog soit placée dans un environnement propre à partir duquel ces serveurs peuvent être interrogés. +En particulier, les serveurs DNS et les certificats racines du système doivent être de confiance. + +## Étapes + +Cloner le dépôt : + +```shell +git clone https://github.com/maelgangloff/domain-watchdog.git +``` + +### Backend + + +1. Installer les dépendances + ```shell + composer install + ``` +2. Configurer les variables d'environnement + ```shell + cp .env .env.local + ``` + + +3. Générer la paire de clés cryptographiques pour la signature JWT + ```shell + php bin/console lexik:jwt:generate-keypair + ``` +4. Exécuter les migrations de base de données + ```shell + php bin/console doctrine:migrations:migrate + ``` +5. Démarrer le serveur Symfony + ```shell + symfony server:start + ``` +6. Construire les assets + ```shell + php bin/console assets:install + ``` +7. N'oubliez pas de configurer les workers pour traiter la [file d'attente de messages](https://symfony.com/doc/current/messenger.html) + + +### Frontend + + +1. Installer les dépendances + ```shell + yarn install + ``` +2. Générer les fichiers de langue + ```shell + yarn run ttag:po2json + ``` +3. Effectuer le build final + ```shell + yarn build + ``` +4. Ajoutez et modifiez les fichiers suivants si nécessaire + + - public + - content + - home.md + - privacy.md + - tos.md + - faq.md + - icons-512.png + - banner.png + - favicon.ico + + diff --git a/docs/src/content/docs/fr/install-config/upgrade.mdx b/docs/src/content/docs/fr/install-config/upgrade.mdx new file mode 100644 index 0000000..0bbd312 --- /dev/null +++ b/docs/src/content/docs/fr/install-config/upgrade.mdx @@ -0,0 +1,52 @@ +--- +title: Mise à jour manuelle +description: Guide de mise à jour expliquant comment mettre à jour le projet en toute sécurité, incluant les migrations et les détails de version. +--- + +import {Steps} from "@astrojs/starlight/components"; + +**Toute mise à jour est sous votre responsabilité. Faites une sauvegarde des données si nécessaire.** + +Récupérer les mises à jour depuis le dépôt distant : + +```shell +git pull origin master +``` + +## Backend + + +1. Installer les dépendances + ```shell + composer install + ``` +2. Exécuter les migrations de base de données + ```shell + php bin/console doctrine:migrations:migrate + ``` +3. Vider le cache Symfony + ```shell + php bin/console cache:clear + ``` +4. Construire les assets + ```shell + php bin/console assets:install + ``` + + +## Frontend + + +1. Installer les dépendances + ```shell + yarn install + ``` +2. Générer les fichiers de langue + ```shell + yarn run ttag:po2json + ``` +3. Générer le build final + ```shell + yarn build + ``` + diff --git a/docs/translations/fr.po b/docs/translations/fr.po deleted file mode 100644 index abf528d..0000000 --- a/docs/translations/fr.po +++ /dev/null @@ -1,2728 +0,0 @@ -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2025-11-20 13:19+0000\n" -"PO-Revision-Date: 2025-11-20 14:22+0000\n" -"Last-Translator: Maël Gangloff \n" -"Language-Team: French \n" -"Language: fr\n" -"MIME-Version: 1.0\n" -"Content-Type: text/plain; charset=UTF-8\n" -"Content-Transfer-Encoding: 8bit\n" -"Plural-Forms: nplurals=2; plural=n > 1;\n" -"X-Generator: Weblate 5.14.3\n" - -# -#: src/content/docs/en/acknowledgment.mdx:block 1 (header) -msgid "title: Acknowledgment" -msgstr "title: Remerciements" - -#: src/content/docs/en/acknowledgment.mdx:block 2 (paragraph) -msgid "import { ContributorList } from \"starlight-contributor-list\"" -msgstr "import { ContributorList } from \"starlight-contributor-list\"" - -#: src/content/docs/en/acknowledgment.mdx:block 3 (header) -msgid "Contributors" -msgstr "Contributeurs" - -#: src/content/docs/en/acknowledgment.mdx:block 4 (paragraph) -msgid "" -"A huge thank-you to everyone who has contributed to this project! Your " -"ideas, bug reports, code improvements, and translations all help make this " -"project better for everyone." -msgstr "" -"Un grand merci à ceux qui ont contribué à ce projet ! Vos idées, rapports de " -"bug, amélioration de code et traductions permettent d'améliorer ce projet et " -"d'en faire profiter tout le monde." - -#: src/content/docs/en/acknowledgment.mdx:block 5 (paragraph) -msgid "" -"" -msgstr "" -"" - -#: src/content/docs/en/definitions/dns.mdx:block 1 (header) -msgid "" -"title: DNS Protocol\n" -"description: What is DNS? Understand the Domain Name System, how it translates domain names into IP addresses, and its role in modern internet navigation." -msgstr "" -"title: Protocole DNS\n" -"description: Qu'est-ce que DNS ? Comprendre le DNS, comment il permet de " -"traduire les noms de domaines en adresses IP et son rôle dans Internet." - -#: src/content/docs/en/definitions/dns.mdx:block 2 (paragraph) -msgid "import {LinkCard} from \"@astrojs/starlight/components\";" -msgstr "import {LinkCard} from \"@astrojs/starlight/components\";" - -#: src/content/docs/en/definitions/dns.mdx:block 3 (paragraph) -msgid "" -"**DNS (Domain Name System)** is the decentralized naming system for " -"computers, services, or any resources connected to the internet or a private" -" network. It acts as the \"phonebook of the internet\", translating human-" -"readable domain names into machine-readable infos." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 4 (header) -msgid "The Hierarchical Architecture" -msgstr "Une architecture hiérarchique" - -#: src/content/docs/en/definitions/dns.mdx:block 5 (paragraph) -msgid "" -"The DNS architecture is a distributed, hierarchical database resembling an " -"inverted tree. This structure, known as the **Domain Name Space**, is " -"processed from right to left:" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 6 (unordered list) -msgid "" -"**Root Level**: The top of the hierarchy, represented by a silent single dot" -" (`.`) at the end of a fully qualified domain name." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 6 (unordered list) -msgid "" -"**Top-Level Domains (TLDs)**: The highest visible level (e.g., `.com`, " -"`.org`, `.fr`)." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 6 (unordered list) -msgid "" -"**Second-Level Domains (SLDs)**: The specific name registered by an entity " -"(e.g., `example` in `example.com`)." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 6 (unordered list) -msgid "" -"**Subdomains**: Further subdivisions for specific services or organizational" -" structures (e.g., `www`, `blog`, or `api`)." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 7 (header) -msgid "Authoritative Servers" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 8 (paragraph) -msgid "" -"Authoritative DNS servers hold the definitive resource records for a " -"specific domain zone. Unlike recursive resolvers that cache answers, " -"authoritative servers provide the original data." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 9 (paragraph) -msgid "When a client requests a domain, the resolution chain queries:" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 10 (ordered list) -msgid "**Root Servers**: Directs to the TLD servers." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 10 (ordered list) -msgid "**TLD Servers**: Directs to the domain's authoritative nameservers." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 10 (ordered list) -msgid "" -"**Authoritative Server**: Returns the final IP address (or other record)." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 11 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 12 (header) -msgid "GLUE Records" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 13 (paragraph) -msgid "" -"A GLUE record is an A (or AAAA) record **provided by the parent zone** to " -"prevent circular dependencies. Normally, the parent zone only delegates, but" -" here it must provide data. They are strictly necessary when a domain's " -"nameserver is a subdomain of the domain itself (e.g., `example.com` uses " -"`ns1.example.com` as its nameserver). Without the GLUE record in the `.com` " -"zone pointing to `ns1`'s IP, the resolver would be stuck in a loop trying to" -" resolve the nameserver's name." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 14 (header) -msgid "Example: `ns.icann.org`" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 15 (paragraph) -msgid "" -"In this example, `icann.org` uses `ns.icann.org` as one of its nameservers." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 16 (paragraph) -msgid "" -"To resolve `icann.org`, you must query `ns.icann.org`, but you cannot find " -"`ns.icann.org` without first resolving `icann.org`." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 17 (paragraph) -msgid "" -"When querying the `.org` TLD server (`A0.ORG.AFILIAS-NST.INFO`), the server " -"returns the Nameserver (NS) records in the **Authority Section**, but " -"crucially, it also provides the IP addresses in the **Additional Section**. " -"These are the GLUE records." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 19 (header) -msgid "See also" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 20 (unordered list) -msgid "" -"[Domain Name System](https://en.wikipedia.org/wiki/Domain_Name_System) on " -"Wikipedia" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 1 (header) -msgid "" -"title: DNSSEC description: Secure your domain resolution. Learn about DNSSEC" -" (Domain Name System Security Extensions) and how it protects users from " -"forged DNS data." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 3 (paragraph) -msgid "" -"**DNSSEC (Domain Name System Security Extensions)** adds a layer of " -"cryptographic security to the DNS protocol. It defends against specific " -"attacks, such as **DNS cache poisoning** and **man-in-the-middle attacks**, " -"by ensuring that the DNS data received is identical to what the zone owner " -"published." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 4 (header) -msgid "What DNSSEC does" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 5 (paragraph) -msgid "" -"DNSSEC employs public-key cryptography to establish a **Chain of Trust**." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 6 (unordered list) -msgid "" -"**Origin Authentication**: Verifies that the data comes from the correct " -"authoritative server." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 6 (unordered list) -msgid "**Data Integrity**: Ensures the data has not been modified in transit." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 6 (unordered list) -msgid "" -"**Authenticated Denial of Existence**: Proves securely that a domain or " -"record does *not* exist (using NSEC/NSEC3)." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 7 (paragraph) -msgid "New resource records enable this validation:" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 8 (unordered list) -msgid "`RRSIG`: The digital signature associated with a record set." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 8 (unordered list) -msgid "`DNSKEY`: The public key used to verify the RRSIG." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 8 (unordered list) -msgid "" -"`DS` (Delegation Signer): A hash of the child zone's key, stored in the " -"parent zone to link the trust chain." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 9 (header) -msgid "What DNSSEC does not do" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 10 (unordered list) -msgid "" -"**No Encryption**: DNS queries and responses remain in plain text (unlike " -"DoH or DoT)." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 10 (unordered list) -msgid "" -"**No Identity Validation**: It does not validate the legitimacy of the " -"domain owner (e.g., it doesn't prevent phishing domains, it just proves the " -"phishing domain's IP is correct)." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 11 (header) -msgid "Configure DNSSEC on your Domain Name" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 12 (paragraph) -msgid "Implementing DNSSEC involves two main stages:" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 13 (ordered list) -msgid "" -"**Signing the Zone**: The authoritative nameserver generates keys (`ZSK` and" -" `KSK`) and signs the zone data, creating `RRSIG` and `DNSKEY` records." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 13 (ordered list) -msgid "" -"**Establishing Trust**: The domain owner must send the `DS` record (hash of " -"the KSK) to the Registrar. The Registrar forwards this to the Registry for " -"publication in the parent TLD zone." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 14 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 15 (header) -msgid "The Adoption of DNSSEC" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 16 (paragraph) -msgid "" -"Adoption is a top-down process starting from the Root Zone. While the Root " -"and most TLDs are signed, adoption at the end-user level (Second-Level " -"Domains) relies on registrar support and registrant awareness." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 17 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 19 (unordered list) -msgid "" -"[DNSSEC World Map](https://stats.labs.apnic.net/dnssec) of the APNIC Labs" -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 1 (header) -msgid "" -"title: Domain Lifecycle description: Explore the domain lifecycle, from " -"registration and renewal to expiration and redemption. Know the critical " -"phases for managing your domain name." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 3 (paragraph) -msgid "" -"The **Domain Lifecycle** defines the statuses a domain name traverses from " -"its creation to its deletion. Understanding these phases is critical to " -"prevent unintentional loss of a domain." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 4 (header) -msgid "The Generic Life Cycle" -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 5 (paragraph) -msgid "" -"![Generic Domain Name Life Cycle](https://www.icann.org/en/registrars/gtld-" -"lifecycle.jpg)" -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 6 (paragraph) -msgid "" -"For most Generic Top-Level Domains (gTLDs) regulated by ICANN, the cycle " -"follows this path:" -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 7 (ordered list) -msgid "**Available**: The domain is open for registration." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 7 (ordered list) -msgid "" -"**Registered (Active)**: The domain is owned and functional. It can be " -"updated, transferred, or renewed (typically 1–10 years)." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 7 (ordered list) -msgid "" -"**Auto-Renew Grace Period**: (0–45 days) The domain expires. The owner can " -"usually renew it at the standard rate. The domain may stop resolving " -"(ServerHold)." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 7 (ordered list) -msgid "" -"**Redemption Grace Period**: (30 days) The domain is deleted from the " -"registrar but held by the registry. Recovery is possible but requires a " -"higher **restoration fee**." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 7 (ordered list) -msgid "" -"**Pending Delete**: (5 days) The domain is scheduled for permanent deletion." -" It cannot be recovered or renewed." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 7 (ordered list) -msgid "" -"**Released**: The domain becomes **Available** again for public " -"registration." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 9 (header) -msgid "Special Cases of some ccTLDs" -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 10 (paragraph) -msgid "" -"Country Code Top-Level Domains (ccTLDs) operate under local regulations, " -"leading to diverse lifecycles:" -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 11 (unordered -#: list) -msgid "" -"**No Grace Periods**: Some ccTLDs enter \"Pending Delete\" immediately upon " -"expiration." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 11 (unordered -#: list) -msgid "" -"**Pre-Expiration Renewal**: Some registries require renewal fees to be paid " -"weeks before the actual expiration date." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 11 (unordered -#: list) -msgid "" -"**Manual Processes**: Restoration in some ccTLDs may require manual " -"intervention and paperwork." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 14 (unordered -#: list) -msgid "" -"[Life Cycle of a Typical gTLD Domain " -"Name](https://www.icann.org/en/contracted-parties/accredited-" -"registrars/resources/gtld-lifecycle) on the ICANN website" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 1 (header) -msgid "" -"title: Domain name description: Define your identity online. An explanation " -"of what a domain name is and its structure." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 2 (paragraph) -msgid "" -"A **Domain Name** is a human-readable identification string used to locate " -"resources on the Internet. It maps complex numerical IP addresses to " -"memorable names." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 3 (header) -msgid "The Structure of a Domain Name" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 4 (paragraph) -msgid "A domain name is read hierarchically from right to left:" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 5 (ordered list) -msgid "**Top-Level Domain (TLD)**: The suffix (e.g., `.com`, `.fr`)." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 5 (ordered list) -msgid "" -"**Second-Level Domain (SLD)**: The unique name chosen by the registrant " -"(e.g., `example`)." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 5 (ordered list) -msgid "**Subdomain**: prefixes for specific services (e.g., `www`, `api`)." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 6 (paragraph) -msgid "" -"A **Fully Qualified Domain Name (FQDN)** includes all labels up to the root " -"(e.g., `www.example.com.`)." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 7 (header) -msgid "The EPP Statuses" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 8 (paragraph) -msgid "" -"The Extensible Provisioning Protocol (EPP) assigns status codes to domains " -"to indicate their state or restrictions. These are visible in WHOIS/RDAP " -"lookups." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 9 (header) -msgid "Server Statuses (Set by Registry)" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 10 (paragraph) -msgid "" -"The registry can apply EPP codes to modify the state of a domain name. These" -" are all codes except those beginning with `client`, which are reserved for " -"registrars. Generic codes are listed in the ICANN documentation." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 11 (paragraph) -msgid "" -"Some registries have developed additional codes to describe non-standard " -"cases. For example, AFNIC added the code `server trade prohibited` to " -"describe the prohibition of the `trade` operation on a domain name. This " -"operation is part of AFNIC's EPP extension and is not a standard operation " -"for a domain name." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 12 (header) -msgid "Client Statuses (Set by Registrar)" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 13 (paragraph) -msgid "" -"Registrars can also apply EPP codes to a domain name. These codes always " -"begin with `client` to distinguish them from the codes applied by the " -"registry." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 14 (paragraph) -msgid "Some codes have the same effect as those applied by the registry." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 15 (paragraph) -msgid "" -"For example, the `client hold` and `server hold` codes block the resolution " -"of a domain name's DNS zone. This means that the top-level domain name's DNS" -" zone no longer contains the `NS` records necessary for delegating the " -"domain name's zone. This results in the complete shutdown of services for " -"the domain name. This code is often used by the registrar to strongly " -"encourage the registrant to pay renewal fees (when the domain name is not in" -" its redemption period)." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 16 (header) -msgid "Internationalized Domain Name (IDN)" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 17 (paragraph) -msgid "" -"An IDN is a domain name that contains characters other than the standard " -"ASCII format (a-z, 0-9, and hyphens). This includes characters with " -"diacritics (accents) or characters from non-Latin scripts (Arabic, Chinese, " -"Cyrillic, etc.)." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 18 (paragraph) -msgid "" -"To function in the legacy DNS system, IDNs are converted into an ASCII-" -"compatible format called **Punycode**, which always begins with `xn--`." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 19 (table) -msgid "Display" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 19 (table) -msgid "Punycode" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 19 (table) -msgid "`maëlgangloff.fr`" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 19 (table) -msgid "`xn--malgangloff-0bb.fr`" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 21 (unordered list) -msgid "[EPP Status Codes](https://icann.org/epp) on the ICANN website" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 1 (header) -msgid "" -"title: EPP Protocol description: What is a Domain Name Registrar? Learn " -"their role in managing the registration and transfer of domain names for the" -" public." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 3 (paragraph) -msgid "" -"The **Extensible Provisioning Protocol (EPP)** is the standard application-" -"layer protocol for allocating objects within registries over the Internet. " -"While primarily used for domain names, it can also manage contacts and host " -"objects." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 4 (header) -msgid "The Actors" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 5 (header) -msgid "Client (Registrar)" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 6 (paragraph) -msgid "" -"The Registrar acts as the EPP Client. They send XML commands to create, " -"update, renew, or delete domain names based on customer requests." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 7 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 8 (header) -msgid "Server (Registry)" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 9 (paragraph) -msgid "" -"The Registry acts as the EPP Server. It processes the commands, validates " -"logic (e.g., \"is this domain available?\"), updates the central database, " -"and returns success or error responses." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 10 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 11 (header) -msgid "The Protocol Mechanism" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 12 (paragraph) -msgid "" -"EPP uses **XML** messages transported over **TCP**, secured by **TLS**. It " -"is a stateful protocol, meaning a session is established (Login) before " -"commands are executed." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 13 (paragraph) -msgid "Common EPP commands include:" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 14 (unordered list) -msgid "``: Verify availability." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 14 (unordered list) -msgid "``: Register a new object." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 14 (unordered list) -msgid "``: Retrieve object details." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 14 (unordered list) -msgid "``: Initiate a registrar transfer." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 14 (unordered list) -msgid "``: Retrieve asynchronous notifications from the Registry." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 16 (unordered list) -msgid "" -"[RFC 5730 - Extensible Provisioning Protocol " -"(EPP)](https://datatracker.ietf.org/doc/html/rfc5730)" -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 1 (header) -msgid "" -"title: ICANN description: Learn about ICANN (Internet Corporation for " -"Assigned Names and Numbers), the non-profit organization coordinating the " -"global internet's unique identifiers." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 3 (paragraph) -msgid "" -"**ICANN (Internet Corporation for Assigned Names and Numbers)** is the non-" -"profit organization responsible for coordinating the maintenance and " -"security of the global Internet's unique identifiers." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 4 (paragraph) -msgid "" -"ICANN acts as the primary governance body for the technical infrastructure " -"of the DNS. Its responsibilities include:" -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 5 (unordered list) -msgid "" -"**IANA Functions**: Managing the allocation of IP address space and the Root" -" Zone of the DNS." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 5 (unordered list) -msgid "" -"**Policy Development**: Facilitating the creation of global policies for the" -" domain name system via a multi-stakeholder model." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 6 (header) -msgid "Managing Top-Level Domains" -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 7 (paragraph) -msgid "" -"ICANN decides which new Top-Level Domains (TLDs) are added to the Root Zone." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 8 (unordered list) -msgid "" -"It oversees the **New gTLD Program**, which expanded the internet from a few" -" dozen extensions (like `.com`) to over 1,000 (like `.app`, `.shop`)." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 8 (unordered list) -msgid "" -"It delegates **ccTLDs** (like `.uk`, `.fr`) to specific country managers, " -"although it has less direct control over their local policies." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 10 (header) -msgid "Accrediting Registrars" -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 11 (paragraph) -msgid "" -"ICANN manages the accreditation system for Registrars wishing to sell " -"generic TLDs. Accreditation ensures that companies handling domain " -"registrations adhere to security, stability, and data retention standards." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 14 (unordered list) -msgid "[Official website](https://www.icann.org/)" -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 1 (header) -msgid "" -"title: RDAP Protocol description: The modern data access protocol. " -"Understand RDAP (Registration Data Access Protocol) for reliable and " -"structured access to domain registration and ownership data." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 3 (paragraph) -msgid "" -"The **Registration Data Access Protocol (RDAP)** is the modern standard for " -"accessing registration data. It was designed to replace the legacy WHOIS " -"protocol by addressing its lack of standardization and security." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 4 (header) -msgid "Key Improvements over WHOIS" -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 5 (unordered list) -msgid "" -"**Structured Data (JSON)**: Unlike WHOIS, which returns unstructured free " -"text, RDAP returns data in JSON format. This allows for easy automated " -"parsing and consistent display by clients." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 5 (unordered list) -msgid "**Standardized Queries**: RDAP uses RESTful web services (HTTP/HTTPS)." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 5 (unordered list) -msgid "" -"**Internationalization**: Native support for non-Latin characters (IDNs)." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 5 (unordered list) -msgid "" -"**Differentiated Access**: RDAP supports authentication, allowing registries" -" to show limited data to the public (GDPR compliance) while providing full " -"data to accredited authorities." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 6 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 7 (header) -msgid "Deployment Status" -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 8 (paragraph) -msgid "" -"ICANN mandates RDAP implementation for all accredited Registrars and gTLD " -"Registries. While WHOIS is still widely used by legacy systems, RDAP is the " -"authoritative source for gTLD registration data. Adoption among ccTLDs is " -"voluntary and ongoing." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 10 (unordered list) -msgid "[RDAP Deployment Dashboard](https://deployment.rdap.org)" -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 1 (header) -msgid "" -"title: Registrar description: What is a Domain Name Registrar? Learn their " -"role in managing the registration and transfer of domain names for the " -"public." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 3 (paragraph) -msgid "" -"A **Registrar** is an accredited commercial entity that sells domain name " -"registrations to the public. They act as the intermediary between the " -"Registrant (the domain owner) and the Registry (the database operator)." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 5 (header) -msgid "Core Responsibilities" -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 6 (header) -msgid "Administrative Management" -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 7 (unordered list) -msgid "" -"**Registration & Renewal**: Handling the purchase and periodic renewal of " -"domains." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 7 (unordered list) -msgid "" -"**Lifecycle Management**: Managing grace periods, redemption fees, and " -"transfers." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 7 (unordered list) -msgid "" -"**Data Accuracy**: Collecting and maintaining accurate contact information " -"for WHOIS/RDAP directories." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 8 (header) -msgid "Technical Services" -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 9 (unordered list) -msgid "" -"**EPP Interface**: Translating user actions into EPP commands sent to the " -"Registry." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 9 (unordered list) -msgid "" -"**DNS Hosting**: Most registrars provide default nameservers, allowing users" -" to manage their DNS records (A, MX, CNAME) via a user-friendly dashboard." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 9 (unordered list) -msgid "**DNSSEC**: Facilitating the rotation and publication of DS records." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 10 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 12 (unordered list) -msgid "" -"[Domain name registrar](https://en.wikipedia.org/wiki/Domain_name_registrar)" -" on Wikipedia" -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 1 (header) -msgid "" -"title: Registry description: Understand the Domain Name Registry? Learn how " -"these organizations manage the central database for all domain names under a" -" specific TLD." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 3 (paragraph) -msgid "" -"A **Registry** (or Registry Operator) is the organization responsible for " -"maintaining the master database of all domain names registered under a " -"specific Top-Level Domain (TLD)." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 4 (header) -msgid "Technical Roles" -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 5 (paragraph) -msgid "" -"The Registry is the authoritative source for its TLD. Its duties include:" -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 6 (unordered list) -msgid "" -"**Zone File Generation**: Publishing the zone file that directs global DNS " -"traffic to the correct nameservers for every domain in the extension." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 6 (unordered list) -msgid "" -"**IDN & DNSSEC Management**: Enforcing policies for special characters and " -"managing the cryptographic signing of the TLD zone." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 6 (unordered list) -msgid "" -"**WHOIS/RDAP Server**: Operating the directory service that provides public " -"information about registered domains." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 7 (header) -msgid "Operational Roles" -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 8 (paragraph) -msgid "" -"Registries generally do not sell directly to the public. Instead, they:" -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 9 (unordered list) -msgid "Define the **Acceptable Use Policies** for the TLD." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 9 (unordered list) -msgid "Set the wholesale price for domains." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 9 (unordered list) -msgid "Accredit and connect with **Registrars** via EPP." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 12 (unordered list) -msgid "" -"[Domain name registry](https://en.wikipedia.org/wiki/Domain_name_registry) " -"on Wikipedia" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 1 (header) -msgid "" -"title: Top-Level Domain (TLD) description: An overview of Top-Level Domains " -"(TLDs), their classification (gTLD, ccTLD, etc.), and the structure of the " -"DNS root zone." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 2 (paragraph) -msgid "" -"A **Top-Level Domain (TLD)** is the rightmost segment of a domain name " -"(after the last dot). TLDs are the highest level of the DNS hierarchy below " -"the root." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 3 (header) -msgid "TLD Classifications" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 4 (header) -msgid "Generic TLD (gTLD)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 5 (paragraph) -msgid "" -"Originally intended for specific use cases, most gTLDs are now open to " -"everyone." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 6 (unordered -#: list) -msgid "" -"**Legacy**: `.com` (commercial), `.net` (network), `.org` (organization)." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 6 (unordered -#: list) -msgid "" -"**New gTLDs**: Thousands of niche extensions like `.app`, `.blog`, `.guru`." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 6 (unordered -#: list) -msgid "" -"**Restricted**: Domains like `.bank` or `.pharmacy` require verification of " -"eligibility." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 6 (unordered -#: list) -msgid "**Brand**: Closed TLDs for corporations, e.g., `.google` or `.bmw`." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 7 (header) -msgid "Country Code TLD (ccTLD)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 8 (paragraph) -msgid "" -"Reserved for countries and territories (two letters, based on ISO 3166)." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 9 (unordered -#: list) -msgid "" -"**Examples**: `.uk` (United Kingdom), `.de` (Germany), `.io` (British Indian" -" Ocean Territory)." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 9 (unordered -#: list) -msgid "" -"**Rules**: Policies vary strictly by country. Some require local residency " -"(e.g., `.no`, `.ca`), while others are marketed globally (e.g., `.tv`, " -"`.ai`)." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 10 (header) -msgid "Sponsored TLD (sTLD)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 11 (paragraph) -msgid "Managed by private organizations representing a specific community." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 12 (unordered -#: list) -msgid "`.gov` (US Government)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 12 (unordered -#: list) -msgid "`.edu` (Accredited US institutions)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 12 (unordered -#: list) -msgid "`.aero` (Aviation industry)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 13 (header) -msgid "Infrastructure TLD" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 14 (unordered -#: list) -msgid "" -"`.arpa`: Managed by IANA, used exclusively for technical infrastructure " -"(e.g., reverse DNS lookups)." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 15 (header) -msgid "Reserved TLDs" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 16 (paragraph) -msgid "" -"Per [RFC 2606](https://tools.ietf.org/html/rfc2606), four TLDs are " -"permanently reserved for testing and documentation to avoid confusion in " -"production environments:" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 17 (unordered -#: list) -msgid "`.test`" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 17 (unordered -#: list) -msgid "`.example`" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 17 (unordered -#: list) -msgid "`.invalid`" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 17 (unordered -#: list) -msgid "`.localhost`" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 19 (unordered -#: list) -msgid "" -"[Top-level domain (Wikipedia)](https://en.wikipedia.org/wiki/Top-" -"level_domain)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 19 (unordered -#: list) -msgid "[IANA Root Zone Database](https://www.iana.org/domains/root/db)" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 1 (header) -msgid "" -"title: WHOIS Protocol description: Get an overview of WHOIS. Learn how this " -"protocol is used to query databases for information about the registered " -"user or assignees of a domain name." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 3 (paragraph) -msgid "" -"WHOIS is a text-based query/response protocol (listening on **TCP Port 43**)" -" widely used for querying databases that store the registered users or " -"assignees of an Internet resource, such as a domain name or an IP address " -"block." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 4 (header) -msgid "Core Use Cases" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 5 (unordered list) -msgid "" -"**Availability Check**: Verifying if a specific domain name is available for" -" registration." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 5 (unordered list) -msgid "" -"**Ownership Identification**: Identifying the Registrant or the Registrar " -"managing the domain." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 5 (unordered list) -msgid "" -"**Technical Troubleshooting**: Finding the authoritative nameservers or the " -"technical contacts to resolve network issues." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 5 (unordered list) -msgid "" -"**Legal & Abuse**: Providing a record for law enforcement, intellectual " -"property protection, and abuse reporting." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 6 (header) -msgid "Thick vs. Thin Registries" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 7 (paragraph) -msgid "" -"Understanding WHOIS responses requires understanding how the TLD Registry " -"stores data." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 8 (header) -msgid "Thin Registry (e.g., .com, .net)" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 9 (paragraph) -msgid "" -"The Registry only stores technical data (DNSSEC, Nameservers) and a pointer " -"to the Registrar." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 10 (paragraph) -msgid "" -"To get the full contact details, a second WHOIS query must be sent to the " -"**Registrar's WHOIS server**." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 11 (header) -msgid "Thick Registry (e.g., .org, .info, most ccTLDs)" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 12 (paragraph) -msgid "" -"The Registry stores *all* information, including the Registrant's contact " -"details and administrative data." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 13 (paragraph) -msgid "A single query to the Registry provides the full record." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 14 (header) -msgid "Example: Recursive WHOIS Query" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 15 (paragraph) -msgid "" -"The standard `whois` command line tool often handles the \"Thin Registry\" " -"redirect automatically. However, seeing the raw steps helps understand the " -"protocol." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 16 (paragraph) -msgid "" -"In the example below for a **Thin TLD** (`.com`), we first query the " -"Registry, which points us to the Registrar." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 17 (header) -msgid "Request to the Registry (Verisign)" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 18 (paragraph) -msgid "Note the `Registrar WHOIS Server` field in the response." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 20 (header) -msgid "Request to the Registrar (IANA)" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 21 (paragraph) -msgid "" -"Following the referral, we query the specific Registrar to get the ownership" -" details." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 23 (header) -msgid "Privacy Considerations" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 24 (paragraph) -msgid "" -"Since the implementation of the **GDPR** (General Data Protection " -"Regulation) and similar global privacy laws, the WHOIS output has changed " -"significantly." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 25 (unordered list) -msgid "" -"**Data Redaction**: Most personal fields (Name, Email, Phone) are now " -"replaced with placeholders like `DATA REDACTED` or `Redacted for Privacy`." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 25 (unordered list) -msgid "" -"**Privacy Proxies**: Registrars often provide services that replace the " -"registrant's details with the registrar's generic contact information to " -"prevent spam and harassment." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 25 (unordered list) -msgid "" -"**Tiered Access**: Full, unredacted data is often no longer publicly " -"available anonymously and requires a legitimate legal request or " -"accreditation." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 26 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 28 (unordered list) -msgid "" -"[RFC 3912 - WHOIS Protocol " -"Specification](https://datatracker.ietf.org/doc/html/rfc3912)" -msgstr "" - -#: src/content/docs/en/developing/contributing/code-of-conduct.md:block 1 -#: (header) -msgid "" -"title: Code of Conduct description: Code of conduct outlining community " -"standards and guidelines for respectful collaboration within the project." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 1 -#: (header) -msgid "" -"title: Pull Requests description: Instructions for submitting pull requests." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 2 -#: (paragraph) -msgid "" -"When you want to propose a change to the source code, you will need to " -"create a Pull Request on this project's GitHub repository." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 3 -#: (paragraph) -msgid "" -"Note that if you are modifying several different parts, you should split it " -"into multiple Pull Requests. This will make it easier to review and merge " -"your proposals." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 4 -#: (paragraph) -msgid "You will then be asked to fill in a few fields:" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 5 -#: (header) -msgid "Title" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 6 -#: (paragraph) -msgid "" -"The Pull Request title should briefly describe the proposed changes. Please " -"be concise and precise. For example, to add support for a new, fictitious " -"provider called \"FakeRegistrar,\" you could write something like \"Add " -"support for FakeRegistrar provider\"." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 7 -#: (header) -msgid "Description" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 8 -#: (paragraph) -msgid "" -"For complex changes, please provide as much detail as possible. If your " -"changes modify an existing API, you must mention this in the description, as" -" it may have repercussions on projects related to Domain Watchdog." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 9 -#: (paragraph) -msgid "" -"If the proposal modifies the frontend, it would be best to include " -"screenshots (desktop and mobile versions) to better visualize the proposal." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 10 -#: (header) -msgid "Change Type" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 11 -#: (paragraph) -msgid "A checklist allows you to choose the type of change proposed:" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 13 -#: (paragraph) -msgid "" -"This checklist helps to better identify the project's impact on the PR." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 14 -#: (header) -msgid "Compliance Checklist" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 15 -#: (paragraph) -msgid "" -"The checklist below allows you to self-assess the conformity of your " -"proposal before submitting it for review:" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 17 -#: (paragraph) -msgid "" -"In any case, if you experience any difficulties creating a PR, feel free to " -"open one; we will help you ensure it complies with these requirements." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 1 -#: (header) -msgid "" -"title: Implementing a new provider description: Step-by-step guide to adding" -" a new Provider, with backend, frontend, and testing instructions to " -"integrate a registrar into the project." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 2 -#: (paragraph) -msgid "" -"import {FileTree, Steps, Code, LinkCard} from " -"\"@astrojs/starlight/components\";" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 3 -#: (paragraph) -msgid "" -"This project aims to be compatible with as many registrars as possible, " -"giving users a choice when creating a Connector." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 4 -#: (paragraph) -msgid "" -"::::caution Only registrars with a public and documented API can be offered." -" Using a registrar's private API is strictly prohibited. ::::" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 5 -#: (paragraph) -msgid "" -"Adding a new Provider is straightforward. Simply follow the steps below." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 6 -#: (paragraph) -msgid "" -"This guide explains how to add support for a new domain registrar. You’ll " -"implement both the Backend (Provider logic) and the Frontend (configuration " -"form)." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 7 -#: (header) -msgid "Prerequisites" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 9 -#: (header) -msgid "Backend" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 10 -#: (paragraph) -msgid "" -"In this section, you’ll implement the logic required to interact with the " -"new Provider’s API." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 14 -#: (paragraph) -msgid "" -"**Well done!** 🎉 You have now completed the Backend implementation. Let’s " -"continue with the Frontend! 🚀" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 15 -#: (header) -msgid "Frontend" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 19 -#: (paragraph) -msgid "**Great job!** 🎉 Your Frontend implementation is now complete." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 20 -#: (header) -msgid "Testing" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 24 -#: (paragraph) -msgid "That's it! You’ve now finished implementing a new Provider. ✨" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 1 (header) -msgid "" -"title: Technical stack description: Overview of the project's technical " -"stack, including frameworks, languages, and architecture used throughout the" -" system." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 2 (paragraph) -msgid "" -"This page lists the main technologies used in the project, with links to " -"their documentation. Specific version information can be found in the " -"project’s dependency files (`composer.lock`, `package.json`, etc.). The " -"architecture diagram below summarizes how these services interact." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 3 (paragraph) -msgid "" -"![Technical stack diagram](../../../../assets/images/dw-stack-diagram.png)" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 5 (header) -msgid "Framework" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 6 (paragraph) -msgid "The programming language is **PHP**." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 7 (paragraph) -msgid "" -"The backend is developed using the **Symfony** framework " -"([documentation](https://symfony.com/doc))." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 8 (paragraph) -msgid "" -"The API is made possible by the **API Platform** project " -"([documentation](https://api-platform.com/docs/symfony/))." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 9 (header) -msgid "SQL database" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 10 (paragraph) -msgid "" -"This project requires a **PostgreSQL** database " -"([documentation](https://www.postgresql.org/docs/current/))." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 11 (paragraph) -msgid "" -"Other database types cannot be used because some migrations were " -"specifically written to leverage the performance of this database management" -" system." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 12 (header) -msgid "Key-value database" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 13 (paragraph) -msgid "A **Redis-compatible** key-value database is required to:" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 14 (unordered -#: list) -msgid "Cache certain values" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 14 (unordered -#: list) -msgid "Implement locks to limit the possibility of conditional raises" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 14 (unordered -#: list) -msgid "" -"Store messages to be distributed to workers to process asynchronous actions." -" For example: updating domain names in a Watchlist on a high-priority RDAP " -"client queue." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 15 (header) -msgid "Time Series database" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 16 (paragraph) -msgid "" -"The **InfluxDB** database is optional. A data point is added for the " -"following events:" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 17 (unordered -#: list) -msgid "" -"RDAP requests from your instance: response time, requested domain name, HTTP" -" status code, IP address of the RDAP server, etc." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 17 (unordered -#: list) -msgid "" -"User notifications: adding events to a domain name, changing EPP statuses, " -"etc." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 18 (header) -msgid "SSO authentication" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 19 (paragraph) -msgid "An **OAuth 2.0** server is not required to authenticate users." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 20 (paragraph) -msgid "" -"Using Single Sign-On (SSO) allows you to delegate user authentication to a " -"third party. This can be useful if you only want people within your " -"organization to be able to use this project instance. Furthermore, you can " -"then configure advanced security policies such as passwordless login, " -"passkeys, multifactor authentication, and more." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 23 (paragraph) -msgid "The language for frontend development is **TypeScript**." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 24 (paragraph) -msgid "" -"The framework used for the frontend is **React** " -"([documentation](https://react.dev/reference/react))." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 25 (header) -msgid "Component Library" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 26 (paragraph) -msgid "" -"The component library used is **Ant Design** " -"([documentation](https://ant.design/components/overview/))." -msgstr "" - -#: src/content/docs/en/developing/translation.mdx:block 1 (header) -msgid "" -"title: Translation description: This project is available in several " -"languages, the current translation status is available here." -msgstr "" - -#: src/content/docs/en/developing/translation.mdx:block 2 (paragraph) -msgid "" -"The project is translated into several languages to allow as many people as " -"possible to easily understand the interface. Feel free to contribute and add" -" a translation!" -msgstr "" - -#: src/content/docs/en/developing/translation.mdx:block 3 (paragraph) -msgid "The current status of the translation is given below." -msgstr "" - -#: src/content/docs/en/developing/translation.mdx:block 4 (paragraph) -msgid "" -"[![Translation status](https://weblate.vinceh121.me/widget/domain-" -"watchdog/domain-watchdog-dashboard/open-" -"graph.png)](https://weblate.vinceh121.me/engage/domain-watchdog/)" -msgstr "" - -#: src/content/docs/en/developing/translation.mdx:block 5 (paragraph) -msgid "" -"If you don't find your language in the list above, feel free to open an " -"issue on the project repository and request that a new language be added." -msgstr "" - -#: src/content/docs/en/developing/translation.mdx:block 6 (paragraph) -msgid "" -"Once the language is added, you can start suggesting translations in the " -"translation space. This project uses Weblate for community translation." -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 1 (header) -msgid "" -"title: Connector description: Learn how the Backorder Connector works, its " -"flow, requirements, and how it integrates with registrar APIs for domain " -"backordering." -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 2 (paragraph) -msgid "import {LinkCard, Steps} from '@astrojs/starlight/components';" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 3 (paragraph) -msgid "" -"A Connector allows Domain Watchdog to communicate with an external domain " -"registrar’s API to perform actions such as domain registration." -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 4 (header) -msgid "Create a Connector" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 6 (ordered list) -msgid "" -"Enter the required information using the credentials obtained from your " -"provider’s customer area :::tip{icon=\"heart\"} A link allows you to " -"directly access the Provider's page to retrieve this authentication " -"information :::" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 6 (ordered list) -msgid "" -"Review and consent to the required terms. As a reminder, you can delete a " -"Connector at any time from your personal space." -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 6 (ordered list) -msgid "" -"Click the button to create your Connector. **Congratulations 🎉** " -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 7 (header) -msgid "Legal considerations" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 8 (paragraph) -msgid "" -"These legal requirements ensure that all domain operations comply with " -"registrar policies and applicable regulations." -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 9 (paragraph) -msgid "" -"Domain Watchdog acts only as a technical interface and does not serve as a " -"payment intermediary. Your credentials are transmitted directly to the " -"provider’s API for domain operations. By creating a Connector, you consent " -"to the provider’s terms and the use of your credentials for authorized " -"operations." -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 10 (paragraph) -msgid "In particular, you must consent to:" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 11 (unordered -#: list) -msgid "Accept the provider’s API Terms of Use" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 11 (unordered -#: list) -msgid "Confirm that you are of legal age to accept these terms" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 12 (paragraph) -msgid "" -"Since the terms of use may change at any time, the link to these terms is " -"always accessible on the page listing the Connectors." -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 1 -#: (header) -msgid "" -"title: Supported registrar list description: List of registrars supported " -"for domain backorders, with details on compatibility." -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 2 -#: (paragraph) -msgid "import {LinkButton} from '@astrojs/starlight/components';" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 3 -#: (paragraph) -msgid ":::caution[Reminder]" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 4 -#: (unordered list) -msgid "" -"Please note that this project is NOT affiliated IN ANY WAY with the API " -"Providers used to order domain names." -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 4 -#: (unordered list) -msgid "" -"The project installers are responsible for the use of their own instance." -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 4 -#: (unordered list) -msgid "" -"Under no circumstances will the owner of this project be held responsible " -"for other cases over which he has no control. :::" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 5 -#: (header) -msgid "OVH" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "Field" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "Required" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "App key" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "the key that allows OVH to identify your application" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "App secret key" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "the secret key associated with your application" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "Consumer key" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "the secret key that links the application to your account" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "Endpoint" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "" -"allows you to choose which server to use (Europe, United States or Canada)" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "Subsidiary" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "the country linked to the OVH subsidiary associated with your account" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "Pricing mode" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "" -"choose whether you want to pay for a Premium domain name or only standard " -"prices" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 7 -#: (paragraph) -msgid "" -"" -" Retrieve my token from the OVH website " -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 8 -#: (header) -msgid "Gandi" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 9 -#: (table) -msgid "Token" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 9 -#: (table) -msgid "your account authentication token" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 9 -#: (table) -msgid "Sharing ID" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 9 -#: (table) -msgid "indicates the organization that will pay for the ordered product" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 9 -#: (table) -msgid "Optional" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 10 -#: (paragraph) -msgid "" -" Retrieve my " -"token from the Gandi website " -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 11 -#: (header) -msgid "Namecheap" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 12 -#: (paragraph) -msgid "" -":::caution This provider requires that the IPv4 address of your instance be " -"entered on its web interface when creating the API connection. This " -"information must also be entered in the configuration. :::" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 13 -#: (table) -msgid "API user" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 13 -#: (table) -msgid "the API user as given by the Provider" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 13 -#: (table) -msgid "API key" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 13 -#: (table) -msgid "the API key as given by the Provider" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 14 -#: (paragraph) -msgid "" -" Retrieve my" -" token from the Namecheap website " -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 15 -#: (header) -msgid "AutoDNS" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 16 -#: (paragraph) -msgid "" -":::caution This provider does not provide a list of supported TLD. Please " -"double-check if the domain you want to register is supported. :::" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "Username" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "the account username" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "Password" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "the account password" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "Owner consent" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "purchase consent" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "Context" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "the \"context\" as given by the Provider" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "Contact ID" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "Contact ID of the domain name holder of the purchased domains" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 18 -#: (paragraph) -msgid "" -" Retrieve my token from " -"the AutoDNS website " -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 19 -#: (header) -msgid "Name.com" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 22 -#: (paragraph) -msgid "" -" Retrieve my token from " -"the Name.com website " -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 23 -#: (header) -msgid "Custom EPP server" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 24 -#: (paragraph) -msgid "" -"This type of connector allows you to directly link your instance to a " -"registry via the EPP protocol. This requires that you have signed a contract" -" with a registry; you are then considered a registry in your own right." -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 25 -#: (paragraph) -msgid "" -"Currently, the implementation of this feature has not been tested; your " -"feedback is important!" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 1 (header) -msgid "" -"title: Getting started description: Step-by-step guide to creating an " -"account, searching domains, tracking changes, and enabling auto-purchase " -"with Connectors." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 3 (paragraph) -msgid "" -"On this page, you'll find a step-by-step guide to getting started with " -"**Domain Watchdog** and exploring its main features. The sidebar menu on the" -" left allows you to quickly navigate between all documentation sections." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 4 (paragraph) -msgid "" -":::note Depending on the configuration of the instance on which you're " -"performing these actions, some options may be limited or hidden. :::" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 5 (header) -msgid "Create an account" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 6 (paragraph) -msgid "" -"If your instance allows user registration, you can create an account " -"directly from the interface." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 7 (paragraph) -msgid "![User registration](../../../../assets/images/user-register.png)" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 9 (paragraph) -msgid "" -"After confirming your email, you can log in and start using all available " -"features." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 10 (header) -msgid "Search for a domain name" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 11 (paragraph) -msgid "" -"Domain Watchdog uses the **RDAP protocol**, the modern replacement for " -"WHOIS, to retrieve accurate information about domain names." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 12 (paragraph) -msgid "" -"![Search for a domain name](../../../../assets/images/search-domain.png)" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 13 (paragraph) -msgid "" -":::tip[Read more] To read the documentation related to domain name search, " -"please click on the link below." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 14 (paragraph) -msgid "" -" :::" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 15 (header) -msgid "Create a Watchlist" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 16 (paragraph) -msgid "" -"A **Watchlist** is a collection of domain names, triggers, and optionally an" -" API Connector. It allows you to:" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 17 (unordered list) -msgid "monitor domain status changes" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 17 (unordered list) -msgid "" -"receive notifications (email or webhook: Slack, Mattermost, Discord, etc.)" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 17 (unordered list) -msgid "optionally auto-purchase a domain when it expires" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 18 (paragraph) -msgid "![Create a Watchlist](../../../../assets/images/create-watchlist.png)" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 19 (paragraph) -msgid "" -":::tip[Read more] To read the documentation related to the Watchlist, please" -" click on the link below." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 20 (paragraph) -msgid "" -" :::" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 21 (header) -msgid "Watchlist notifications" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 22 (paragraph) -msgid "" -"When a domain changes state, you’ll automatically receive a notification. " -"You can also export domain events as **iCalendar** feeds." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 24 (paragraph) -msgid "" -"A **Connector** is used to automatically order (backorder) a domain name " -"using its provider’s API." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 25 (paragraph) -msgid "![Create a Connector](../../../../assets/images/create-connector.png)" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 26 (paragraph) -msgid "" -":::tip[Read more] To read the documentation related to Connector, please " -"click on the link below." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 27 (paragraph) -msgid "" -" :::" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 28 (header) -msgid "Supported registrar list" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 29 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 30 (header) -msgid "Tracking table" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 31 (paragraph) -msgid "" -"The Tracking table page displays a list of all the domain names you monitor " -"via your Watchlists. This list is ordered, meaning the domain names are " -"arranged according to their estimated deletion date." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 32 (paragraph) -msgid "![Tracking table](../../../../assets/images/tracking-table.png)" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 33 (paragraph) -msgid "" -":::tip[Read more] To read the documentation related to the Tracking table, " -"please click on the link below." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 34 (paragraph) -msgid "" -" :::" -msgstr "" - -#: src/content/docs/en/features/infrastructure/icann-registrar-list.mdx:block -#: 1 (header) -msgid "title: ICANN Registrar list" -msgstr "" - -#: src/content/docs/en/features/infrastructure/tld-list.mdx:block 1 (header) -msgid "title: TLD list" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 1 (header) -msgid "title: Domain search description: Domain search feature overview" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 2 (paragraph) -msgid "" -"import {Steps} from \"@astrojs/starlight/components\" import {Kbd} from " -"\"starlight-kbd/components\"" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 3 (paragraph) -msgid "" -":::tip[Did you know?] In this project, everything is done to minimize the " -"number of requests to RDAP servers. Limitations imposed on end users help " -"control the flow of RDAP requests. These limitations can be configured for " -"each instance, in the environment variables. :::" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 4 (paragraph) -msgid "" -"The domain search feature allows users to look up information about a domain" -" name through the user interface." -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 5 (paragraph) -msgid "To search for a domain name:" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 7 (paragraph) -msgid "" -"![Search for a domain name](../../../../../assets/images/search-domain.png)" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 8 (paragraph) -msgid "" -"If the extension you are searching for does **not** have an official RDAP " -"server, an error message will inform you that no RDAP server is available." -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 9 (header) -msgid "Force Update" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 10 (paragraph) -msgid "" -"By default, if the domain information stored in the database is still " -"considered valid, the system returns the existing record without performing " -"a new RDAP query." -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 11 (paragraph) -msgid "If you need to force an RDAP update for a given domain:" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 12 (unordered -#: list) -msgid "" -"Press when submitting " -"the search." -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 13 (paragraph) -msgid "This triggers a fresh lookup against the RDAP server." -msgstr "" - -#: src/content/docs/en/features/tracking/tracking-table.mdx:block 1 (header) -msgid "title: Tracking table" -msgstr "" - -#: src/content/docs/en/features/tracking/tracking-table.mdx:block 2 -#: (paragraph) -msgid "![Tracking table](../../../../../assets/images/tracking-table.png)" -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 1 (header) -msgid "" -"title: Watchlist description: Learn how the domain watchlist works, enabling" -" users to monitor domains and receive updates on changes." -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 2 (paragraph) -msgid "import {Steps} from '@astrojs/starlight/components';" -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 3 (paragraph) -msgid "" -"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." -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 4 (paragraph) -msgid "" -"If a domain has expired and a connector is linked to the Watchlist, then an " -"order attempt will be made though the Connector provider's API." -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 5 (paragraph) -msgid "" -":::note If the same domain name is present on several Watchlists, on the " -"same principle as the race condition, it is not possible to predict in " -"advance which user will win the domain name. The choice is left to chance..." -" :::" -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 7 (paragraph) -msgid "" -"![Create a Watchlist](../../../..//../assets/images/create-watchlist.png)" -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 9 (paragraph) -msgid "Now, it's your turn to create a Watchlist!" -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 10 (header) -msgid "Limitations" -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 11 (paragraph) -msgid "" -"Depending on the instance configuration, there are several limitations to " -"frame user behavior." -msgstr "" - -#: src/content/docs/en/index.mdx:block 1 (header) -msgid "" -"title: Domain Watchdog description: An app that uses RDAP to collect " -"publicly available info about domains, track their history, and purchase " -"then when they expire template: splash hero: tagline: Your companion in the " -"quest for domain names 🔍 image: file: ../../../assets/logo.png actions: - " -"text: Get started link: /en/features icon: right-arrow - text: Demo link: " -"https://demo.domainwatchdog.eu icon: external variant: minimal" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 1 (header) -msgid "" -"title: Configuration description: Configuration guide explaining environment" -" variables and settings required to run and customize the project." -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 2 (paragraph) -msgid "import {LinkCard} from '@astrojs/starlight/components';" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 4 (header) -msgid "Environment variables" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Variable" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Default" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`DATABASE_URL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Please check Symfony config" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OUTGOING_IP`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Outgoing IPv4, needed for some providers" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`INFLUXDB_ENABLED`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Enable the connection with InfluxDB" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`false`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`INFLUXDB_URL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "InfluxDB URL" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`http://localhost:8086`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`INFLUXDB_TOKEN`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "InfluxDB token" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`INFLUXDB_BUCKET`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "InfluxDB bucket name" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`domainwatchdog`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`INFLUXDB_ORG`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "InfluxDB organization" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`LIMITED_FEATURES`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Limit certain features for users" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`LIMIT_MAX_WATCHLIST`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Maximum number of Watchlists per user" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`0`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`LIMIT_MAX_WATCHLIST_DOMAINS`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Maximum number of domains per Watchlist" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`LIMIT_MAX_WATCHLIST_WEBHOOKS`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Maximum number of webhooks per Watchlist" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`MAILER_SENDER_NAME`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Name of the sender of emails" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`Domain Watchdog`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`MAILER_SENDER_EMAIL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Sender's email address" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`notifications@example.com`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`REGISTRATION_ENABLED`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Enable user registration" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`true`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`REGISTRATION_VERIFY_EMAIL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Verify email addresses during registration" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`MAILER_DSN`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`null://null`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OAUTH_CLIENT_ID`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Client ID (OAuth 2.0) for using external SSO" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OAUTH_CLIENT_SECRET`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Client secret (OAuth 2.0)" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OAUTH_AUTHORIZATION_URL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Authorization URL (OAuth 2.0)" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OAUTH_TOKEN_URL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Token URL (OAuth 2.0)" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OAUTH_USERINFO_URL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "User Info URL (OAuth 2.0)" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OAUTH_SCOPE`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Scope (OAuth 2.0)" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 6 (header) -msgid "Authentication" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 7 (paragraph) -msgid "" -"Currently, there is no way to delete your account, reset your password, or " -"enable multifactor authentication." -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 8 (paragraph) -msgid "" -"Registering users directly in the interface is recommended for individual " -"instances. For multi-user environments, the recommended method is to use " -"external SSO via the OAuth 2.0 protocol." -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 1 -#: (header) -msgid "" -"title: Docker Compose installation description: Guide to installing the " -"project using Docker Compose, with setup steps, and deployment notes." -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 3 -#: (ordered list) -msgid "" -"Download the [docker-compose.yml](https://github.com/maelgangloff/domain-" -"watchdog/blob/develop/docker-compose.yml) and modify it as needed" -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 3 -#: (ordered list) -msgid "" -"Download the [.env](https://github.com/maelgangloff/domain-" -"watchdog/blob/develop/.env) and modify it as needed " -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 3 -#: (ordered list) -msgid "Add static files to customize your instance (under `public/content`)" -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 3 -#: (ordered list) -msgid "Pull the latest version of the Domain Watchdog image from Docker Hub" -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 5 -#: (ordered list) -msgid "Start the project in production environment" -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 7 -#: (paragraph) -msgid "" -"By default, the container listens on http://localhost:8080, but you can " -"configure this in environment variables." -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 1 -#: (header) -msgid "" -"title: Manual installation description: Manual installation guide with " -"system requirements, dependencies, and step-by-step instructions to install " -"the project from source." -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 2 -#: (paragraph) -msgid "" -"import {FileTree, LinkCard, Steps} from '@astrojs/starlight/components';" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 3 -#: (paragraph) -msgid "" -"To deploy a Domain Watchdog instance, please refer to the Symfony " -"documentation on [How to deploy a Symfony " -"application](https://symfony.com/doc/current/deployment.html)." -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 5 -#: (unordered list) -msgid "PHP 8.4 or higher" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 5 -#: (unordered list) -msgid "PostgreSQL 16 or higher" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 6 -#: (paragraph) -msgid "" -"In order to retrieve information about domain names, Domain Watchdog will " -"query the RDAP server responsible for the TLD. It is crucial that the Domain" -" Watchdog instance is placed in a clean environment from which these servers" -" can be queried. In particular, the DNS servers and root certificates of the" -" system must be trusted." -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 7 -#: (header) -msgid "Steps" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 8 -#: (paragraph) -msgid "Clone the repository:" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 12 -#: (ordered list) -msgid "Generate the cryptographic key pair for the JWT signature" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 12 -#: (ordered list) -msgid "Run database migrations" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 12 -#: (ordered list) -msgid "Start the Symfony server" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 12 -#: (ordered list) -msgid "Build assets" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 12 -#: (ordered list) -msgid "" -"Don't forget to set up workers to process the [message " -"queue](https://symfony.com/doc/current/messenger.html) " -msgstr "" - -#: src/content/docs/en/install-config/upgrade.mdx:block 1 (header) -msgid "" -"title: Manual Upgrade description: Upgrade guide explaining how to safely " -"update the project, including migrations, and versioning details." -msgstr "" - -#: src/content/docs/en/install-config/upgrade.mdx:block 2 (paragraph) -msgid "import {Steps} from \"@astrojs/starlight/components\";" -msgstr "" - -#: src/content/docs/en/install-config/upgrade.mdx:block 3 (paragraph) -msgid "" -"**Any updates are your responsibility. Make a backup of the data if " -"necessary.**" -msgstr "" - -#: src/content/docs/en/install-config/upgrade.mdx:block 4 (paragraph) -msgid "Fetch updates from the remote repository:" -msgstr "" - -#: src/content/docs/en/legal/faq.md:block 1 (header) -msgid "title: FAQ" -msgstr "" - -#: src/content/docs/en/legal/license.md:block 1 (header) -msgid "" -"title: License description: Licensing information detailing usage rights, " -"redistribution terms, and legal conditions for contributing and using the " -"project." -msgstr "" - -#: src/content/docs/en/legal/license.md:block 2 (paragraph) -msgid "" -"This entire project is licensed under [*GNU Affero General Public License " -"v3.0 or later*](https://www.gnu.org/licenses/agpl-3.0.txt). Contributions " -"are welcome as long as they do not contravene the Code of Conduct." -msgstr "" - -#: src/content/docs/en/legal/security.md:block 1 (header) -msgid "" -"title: Security policy description: Security policy describing vulnerability" -" reporting, and guidelines to keep the project secure." -msgstr "" - -#: src/content/docs/en/legal/security.md:block 2 (header) -msgid "Reporting a Vulnerability" -msgstr "" - -#: src/content/docs/en/legal/security.md:block 3 (paragraph) -msgid "" -"If you want to report a vulnerability, please contact the maintainer of this" -" repository. Thanks!" -msgstr "" diff --git a/docs/translations/translations.pot b/docs/translations/translations.pot deleted file mode 100644 index 02d85f5..0000000 --- a/docs/translations/translations.pot +++ /dev/null @@ -1,2967 +0,0 @@ -# -msgid "" -msgstr "" - -#: src/content/docs/en/acknowledgment.mdx:block 1 (header) -msgid "title: Acknowledgment" -msgstr "" - -#: src/content/docs/en/acknowledgment.mdx:block 2 (paragraph) -msgid "import { ContributorList } from \"starlight-contributor-list\"" -msgstr "" - -#: src/content/docs/en/acknowledgment.mdx:block 3 (header) -msgid "Contributors" -msgstr "" - -#: src/content/docs/en/acknowledgment.mdx:block 4 (paragraph) -msgid "" -"A huge thank-you to everyone who has contributed to this project! Your " -"ideas, bug reports, code improvements, and translations all help make this " -"project better for everyone." -msgstr "" - -#: src/content/docs/en/acknowledgment.mdx:block 5 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 1 (header) -msgid "" -"title: DNS Protocol\n" -"description: What is DNS? Understand the Domain Name System, how it translates domain names into IP addresses, and its role in modern internet navigation." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 2 (paragraph) -msgid "import {LinkCard} from \"@astrojs/starlight/components\";" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 3 (paragraph) -msgid "" -"**DNS (Domain Name System)** is the decentralized naming system for " -"computers, services, or any resources connected to the internet or a private" -" network. It acts as the \"phonebook of the internet\", translating human-" -"readable domain names into machine-readable infos." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 4 (header) -msgid "The Hierarchical Architecture" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 5 (paragraph) -msgid "" -"The DNS architecture is a distributed, hierarchical database resembling an " -"inverted tree. This structure, known as the **Domain Name Space**, is " -"processed from right to left:" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 6 (unordered list) -msgid "" -"**Root Level**: The top of the hierarchy, represented by a silent single dot" -" (`.`) at the end of a fully qualified domain name." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 6 (unordered list) -msgid "" -"**Top-Level Domains (TLDs)**: The highest visible level (e.g., `.com`, " -"`.org`, `.fr`)." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 6 (unordered list) -msgid "" -"**Second-Level Domains (SLDs)**: The specific name registered by an entity " -"(e.g., `example` in `example.com`)." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 6 (unordered list) -msgid "" -"**Subdomains**: Further subdivisions for specific services or organizational" -" structures (e.g., `www`, `blog`, or `api`)." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 7 (header) -msgid "Authoritative Servers" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 8 (paragraph) -msgid "" -"Authoritative DNS servers hold the definitive resource records for a " -"specific domain zone. Unlike recursive resolvers that cache answers, " -"authoritative servers provide the original data." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 9 (paragraph) -msgid "When a client requests a domain, the resolution chain queries:" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 10 (ordered list) -msgid "**Root Servers**: Directs to the TLD servers." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 10 (ordered list) -msgid "**TLD Servers**: Directs to the domain's authoritative nameservers." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 10 (ordered list) -msgid "" -"**Authoritative Server**: Returns the final IP address (or other record)." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 11 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 12 (header) -msgid "GLUE Records" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 13 (paragraph) -msgid "" -"A GLUE record is an A (or AAAA) record **provided by the parent zone** to " -"prevent circular dependencies. Normally, the parent zone only delegates, but" -" here it must provide data. They are strictly necessary when a domain's " -"nameserver is a subdomain of the domain itself (e.g., `example.com` uses " -"`ns1.example.com` as its nameserver). Without the GLUE record in the `.com` " -"zone pointing to `ns1`'s IP, the resolver would be stuck in a loop trying to" -" resolve the nameserver's name." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 14 (header) -msgid "Example: `ns.icann.org`" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 15 (paragraph) -msgid "" -"In this example, `icann.org` uses `ns.icann.org` as one of its nameservers." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 16 (paragraph) -msgid "" -"To resolve `icann.org`, you must query `ns.icann.org`, but you cannot find " -"`ns.icann.org` without first resolving `icann.org`." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 17 (paragraph) -msgid "" -"When querying the `.org` TLD server (`A0.ORG.AFILIAS-NST.INFO`), the server " -"returns the Nameserver (NS) records in the **Authority Section**, but " -"crucially, it also provides the IP addresses in the **Additional Section**. " -"These are the GLUE records." -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 18 (code) -msgid "" -"; <<>> DiG 9.20.15 <<>> ns.icann.org @A0.ORG.AFILIAS-NST.INFO\n" -";; global options: +cmd\n" -";; Got answer:\n" -";; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52458\n" -";; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 3\n" -"\n" -";; QUESTION SECTION:\n" -";ns.icann.org. IN A\n" -"\n" -";; AUTHORITY SECTION:\n" -"icann.org. 3600 IN NS ns.icann.org.\n" -"icann.org. 3600 IN NS a.icann-servers.net.\n" -"icann.org. 3600 IN NS c.icann-servers.net.\n" -"icann.org. 3600 IN NS b.icann-servers.net.\n" -"\n" -";; ADDITIONAL SECTION:\n" -"ns.icann.org. 3600 IN A 199.4.138.53\n" -"ns.icann.org. 3600 IN AAAA 2001:500:89::53\n" -"\n" -";; Query time: 241 msec\n" -";; SERVER: 199.19.56.1#53(A0.ORG.AFILIAS-NST.INFO) (UDP)\n" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 19 (header) -msgid "See also" -msgstr "" - -#: src/content/docs/en/definitions/dns.mdx:block 20 (unordered list) -msgid "" -"[Domain Name System](https://en.wikipedia.org/wiki/Domain_Name_System) on " -"Wikipedia" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 1 (header) -msgid "" -"title: DNSSEC description: Secure your domain resolution. Learn about DNSSEC" -" (Domain Name System Security Extensions) and how it protects users from " -"forged DNS data." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 3 (paragraph) -msgid "" -"**DNSSEC (Domain Name System Security Extensions)** adds a layer of " -"cryptographic security to the DNS protocol. It defends against specific " -"attacks, such as **DNS cache poisoning** and **man-in-the-middle attacks**, " -"by ensuring that the DNS data received is identical to what the zone owner " -"published." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 4 (header) -msgid "What DNSSEC does" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 5 (paragraph) -msgid "" -"DNSSEC employs public-key cryptography to establish a **Chain of Trust**." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 6 (unordered list) -msgid "" -"**Origin Authentication**: Verifies that the data comes from the correct " -"authoritative server." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 6 (unordered list) -msgid "**Data Integrity**: Ensures the data has not been modified in transit." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 6 (unordered list) -msgid "" -"**Authenticated Denial of Existence**: Proves securely that a domain or " -"record does *not* exist (using NSEC/NSEC3)." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 7 (paragraph) -msgid "New resource records enable this validation:" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 8 (unordered list) -msgid "`RRSIG`: The digital signature associated with a record set." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 8 (unordered list) -msgid "`DNSKEY`: The public key used to verify the RRSIG." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 8 (unordered list) -msgid "" -"`DS` (Delegation Signer): A hash of the child zone's key, stored in the " -"parent zone to link the trust chain." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 9 (header) -msgid "What DNSSEC does not do" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 10 (unordered list) -msgid "" -"**No Encryption**: DNS queries and responses remain in plain text (unlike " -"DoH or DoT)." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 10 (unordered list) -msgid "" -"**No Identity Validation**: It does not validate the legitimacy of the " -"domain owner (e.g., it doesn't prevent phishing domains, it just proves the " -"phishing domain's IP is correct)." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 11 (header) -msgid "Configure DNSSEC on your Domain Name" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 12 (paragraph) -msgid "Implementing DNSSEC involves two main stages:" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 13 (ordered list) -msgid "" -"**Signing the Zone**: The authoritative nameserver generates keys (`ZSK` and" -" `KSK`) and signs the zone data, creating `RRSIG` and `DNSKEY` records." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 13 (ordered list) -msgid "" -"**Establishing Trust**: The domain owner must send the `DS` record (hash of " -"the KSK) to the Registrar. The Registrar forwards this to the Registry for " -"publication in the parent TLD zone." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 14 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 15 (header) -msgid "The Adoption of DNSSEC" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 16 (paragraph) -msgid "" -"Adoption is a top-down process starting from the Root Zone. While the Root " -"and most TLDs are signed, adoption at the end-user level (Second-Level " -"Domains) relies on registrar support and registrant awareness." -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 17 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/dnssec.mdx:block 19 (unordered list) -msgid "" -"[DNSSEC World Map](https://stats.labs.apnic.net/dnssec) of the APNIC Labs" -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 1 (header) -msgid "" -"title: Domain Lifecycle description: Explore the domain lifecycle, from " -"registration and renewal to expiration and redemption. Know the critical " -"phases for managing your domain name." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 3 (paragraph) -msgid "" -"The **Domain Lifecycle** defines the statuses a domain name traverses from " -"its creation to its deletion. Understanding these phases is critical to " -"prevent unintentional loss of a domain." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 4 (header) -msgid "The Generic Life Cycle" -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 5 (paragraph) -msgid "" -"![Generic Domain Name Life Cycle](https://www.icann.org/en/registrars/gtld-" -"lifecycle.jpg)" -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 6 (paragraph) -msgid "" -"For most Generic Top-Level Domains (gTLDs) regulated by ICANN, the cycle " -"follows this path:" -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 7 (ordered list) -msgid "**Available**: The domain is open for registration." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 7 (ordered list) -msgid "" -"**Registered (Active)**: The domain is owned and functional. It can be " -"updated, transferred, or renewed (typically 1–10 years)." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 7 (ordered list) -msgid "" -"**Auto-Renew Grace Period**: (0–45 days) The domain expires. The owner can " -"usually renew it at the standard rate. The domain may stop resolving " -"(ServerHold)." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 7 (ordered list) -msgid "" -"**Redemption Grace Period**: (30 days) The domain is deleted from the " -"registrar but held by the registry. Recovery is possible but requires a " -"higher **restoration fee**." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 7 (ordered list) -msgid "" -"**Pending Delete**: (5 days) The domain is scheduled for permanent deletion." -" It cannot be recovered or renewed." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 7 (ordered list) -msgid "" -"**Released**: The domain becomes **Available** again for public " -"registration." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 9 (header) -msgid "Special Cases of some ccTLDs" -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 10 (paragraph) -msgid "" -"Country Code Top-Level Domains (ccTLDs) operate under local regulations, " -"leading to diverse lifecycles:" -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 11 (unordered -#: list) -msgid "" -"**No Grace Periods**: Some ccTLDs enter \"Pending Delete\" immediately upon " -"expiration." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 11 (unordered -#: list) -msgid "" -"**Pre-Expiration Renewal**: Some registries require renewal fees to be paid " -"weeks before the actual expiration date." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 11 (unordered -#: list) -msgid "" -"**Manual Processes**: Restoration in some ccTLDs may require manual " -"intervention and paperwork." -msgstr "" - -#: src/content/docs/en/definitions/domain-lifecycle.mdx:block 14 (unordered -#: list) -msgid "" -"[Life Cycle of a Typical gTLD Domain " -"Name](https://www.icann.org/en/contracted-parties/accredited-" -"registrars/resources/gtld-lifecycle) on the ICANN website" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 1 (header) -msgid "" -"title: Domain name description: Define your identity online. An explanation " -"of what a domain name is and its structure." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 2 (paragraph) -msgid "" -"A **Domain Name** is a human-readable identification string used to locate " -"resources on the Internet. It maps complex numerical IP addresses to " -"memorable names." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 3 (header) -msgid "The Structure of a Domain Name" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 4 (paragraph) -msgid "A domain name is read hierarchically from right to left:" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 5 (ordered list) -msgid "**Top-Level Domain (TLD)**: The suffix (e.g., `.com`, `.fr`)." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 5 (ordered list) -msgid "" -"**Second-Level Domain (SLD)**: The unique name chosen by the registrant " -"(e.g., `example`)." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 5 (ordered list) -msgid "**Subdomain**: prefixes for specific services (e.g., `www`, `api`)." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 6 (paragraph) -msgid "" -"A **Fully Qualified Domain Name (FQDN)** includes all labels up to the root " -"(e.g., `www.example.com.`)." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 7 (header) -msgid "The EPP Statuses" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 8 (paragraph) -msgid "" -"The Extensible Provisioning Protocol (EPP) assigns status codes to domains " -"to indicate their state or restrictions. These are visible in WHOIS/RDAP " -"lookups." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 9 (header) -msgid "Server Statuses (Set by Registry)" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 10 (paragraph) -msgid "" -"The registry can apply EPP codes to modify the state of a domain name. These" -" are all codes except those beginning with `client`, which are reserved for " -"registrars. Generic codes are listed in the ICANN documentation." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 11 (paragraph) -msgid "" -"Some registries have developed additional codes to describe non-standard " -"cases. For example, AFNIC added the code `server trade prohibited` to " -"describe the prohibition of the `trade` operation on a domain name. This " -"operation is part of AFNIC's EPP extension and is not a standard operation " -"for a domain name." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 12 (header) -msgid "Client Statuses (Set by Registrar)" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 13 (paragraph) -msgid "" -"Registrars can also apply EPP codes to a domain name. These codes always " -"begin with `client` to distinguish them from the codes applied by the " -"registry." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 14 (paragraph) -msgid "Some codes have the same effect as those applied by the registry." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 15 (paragraph) -msgid "" -"For example, the `client hold` and `server hold` codes block the resolution " -"of a domain name's DNS zone. This means that the top-level domain name's DNS" -" zone no longer contains the `NS` records necessary for delegating the " -"domain name's zone. This results in the complete shutdown of services for " -"the domain name. This code is often used by the registrar to strongly " -"encourage the registrant to pay renewal fees (when the domain name is not in" -" its redemption period)." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 16 (header) -msgid "Internationalized Domain Name (IDN)" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 17 (paragraph) -msgid "" -"An IDN is a domain name that contains characters other than the standard " -"ASCII format (a-z, 0-9, and hyphens). This includes characters with " -"diacritics (accents) or characters from non-Latin scripts (Arabic, Chinese, " -"Cyrillic, etc.)." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 18 (paragraph) -msgid "" -"To function in the legacy DNS system, IDNs are converted into an ASCII-" -"compatible format called **Punycode**, which always begins with `xn--`." -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 19 (table) -msgid "Display" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 19 (table) -msgid "Punycode" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 19 (table) -msgid "`maëlgangloff.fr`" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 19 (table) -msgid "`xn--malgangloff-0bb.fr`" -msgstr "" - -#: src/content/docs/en/definitions/domain-name.mdx:block 21 (unordered list) -msgid "[EPP Status Codes](https://icann.org/epp) on the ICANN website" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 1 (header) -msgid "" -"title: EPP Protocol description: What is a Domain Name Registrar? Learn " -"their role in managing the registration and transfer of domain names for the" -" public." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 3 (paragraph) -msgid "" -"The **Extensible Provisioning Protocol (EPP)** is the standard application-" -"layer protocol for allocating objects within registries over the Internet. " -"While primarily used for domain names, it can also manage contacts and host " -"objects." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 4 (header) -msgid "The Actors" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 5 (header) -msgid "Client (Registrar)" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 6 (paragraph) -msgid "" -"The Registrar acts as the EPP Client. They send XML commands to create, " -"update, renew, or delete domain names based on customer requests." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 7 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 8 (header) -msgid "Server (Registry)" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 9 (paragraph) -msgid "" -"The Registry acts as the EPP Server. It processes the commands, validates " -"logic (e.g., \"is this domain available?\"), updates the central database, " -"and returns success or error responses." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 10 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 11 (header) -msgid "The Protocol Mechanism" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 12 (paragraph) -msgid "" -"EPP uses **XML** messages transported over **TCP**, secured by **TLS**. It " -"is a stateful protocol, meaning a session is established (Login) before " -"commands are executed." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 13 (paragraph) -msgid "Common EPP commands include:" -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 14 (unordered list) -msgid "``: Verify availability." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 14 (unordered list) -msgid "``: Register a new object." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 14 (unordered list) -msgid "``: Retrieve object details." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 14 (unordered list) -msgid "``: Initiate a registrar transfer." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 14 (unordered list) -msgid "``: Retrieve asynchronous notifications from the Registry." -msgstr "" - -#: src/content/docs/en/definitions/epp.mdx:block 16 (unordered list) -msgid "" -"[RFC 5730 - Extensible Provisioning Protocol " -"(EPP)](https://datatracker.ietf.org/doc/html/rfc5730)" -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 1 (header) -msgid "" -"title: ICANN description: Learn about ICANN (Internet Corporation for " -"Assigned Names and Numbers), the non-profit organization coordinating the " -"global internet's unique identifiers." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 3 (paragraph) -msgid "" -"**ICANN (Internet Corporation for Assigned Names and Numbers)** is the non-" -"profit organization responsible for coordinating the maintenance and " -"security of the global Internet's unique identifiers." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 4 (paragraph) -msgid "" -"ICANN acts as the primary governance body for the technical infrastructure " -"of the DNS. Its responsibilities include:" -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 5 (unordered list) -msgid "" -"**IANA Functions**: Managing the allocation of IP address space and the Root" -" Zone of the DNS." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 5 (unordered list) -msgid "" -"**Policy Development**: Facilitating the creation of global policies for the" -" domain name system via a multi-stakeholder model." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 6 (header) -msgid "Managing Top-Level Domains" -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 7 (paragraph) -msgid "" -"ICANN decides which new Top-Level Domains (TLDs) are added to the Root Zone." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 8 (unordered list) -msgid "" -"It oversees the **New gTLD Program**, which expanded the internet from a few" -" dozen extensions (like `.com`) to over 1,000 (like `.app`, `.shop`)." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 8 (unordered list) -msgid "" -"It delegates **ccTLDs** (like `.uk`, `.fr`) to specific country managers, " -"although it has less direct control over their local policies." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 10 (header) -msgid "Accrediting Registrars" -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 11 (paragraph) -msgid "" -"ICANN manages the accreditation system for Registrars wishing to sell " -"generic TLDs. Accreditation ensures that companies handling domain " -"registrations adhere to security, stability, and data retention standards." -msgstr "" - -#: src/content/docs/en/definitions/icann.mdx:block 14 (unordered list) -msgid "[Official website](https://www.icann.org/)" -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 1 (header) -msgid "" -"title: RDAP Protocol description: The modern data access protocol. " -"Understand RDAP (Registration Data Access Protocol) for reliable and " -"structured access to domain registration and ownership data." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 3 (paragraph) -msgid "" -"The **Registration Data Access Protocol (RDAP)** is the modern standard for " -"accessing registration data. It was designed to replace the legacy WHOIS " -"protocol by addressing its lack of standardization and security." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 4 (header) -msgid "Key Improvements over WHOIS" -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 5 (unordered list) -msgid "" -"**Structured Data (JSON)**: Unlike WHOIS, which returns unstructured free " -"text, RDAP returns data in JSON format. This allows for easy automated " -"parsing and consistent display by clients." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 5 (unordered list) -msgid "**Standardized Queries**: RDAP uses RESTful web services (HTTP/HTTPS)." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 5 (unordered list) -msgid "" -"**Internationalization**: Native support for non-Latin characters (IDNs)." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 5 (unordered list) -msgid "" -"**Differentiated Access**: RDAP supports authentication, allowing registries" -" to show limited data to the public (GDPR compliance) while providing full " -"data to accredited authorities." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 6 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 7 (header) -msgid "Deployment Status" -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 8 (paragraph) -msgid "" -"ICANN mandates RDAP implementation for all accredited Registrars and gTLD " -"Registries. While WHOIS is still widely used by legacy systems, RDAP is the " -"authoritative source for gTLD registration data. Adoption among ccTLDs is " -"voluntary and ongoing." -msgstr "" - -#: src/content/docs/en/definitions/rdap.mdx:block 10 (unordered list) -msgid "[RDAP Deployment Dashboard](https://deployment.rdap.org)" -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 1 (header) -msgid "" -"title: Registrar description: What is a Domain Name Registrar? Learn their " -"role in managing the registration and transfer of domain names for the " -"public." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 3 (paragraph) -msgid "" -"A **Registrar** is an accredited commercial entity that sells domain name " -"registrations to the public. They act as the intermediary between the " -"Registrant (the domain owner) and the Registry (the database operator)." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 5 (header) -msgid "Core Responsibilities" -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 6 (header) -msgid "Administrative Management" -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 7 (unordered list) -msgid "" -"**Registration & Renewal**: Handling the purchase and periodic renewal of " -"domains." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 7 (unordered list) -msgid "" -"**Lifecycle Management**: Managing grace periods, redemption fees, and " -"transfers." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 7 (unordered list) -msgid "" -"**Data Accuracy**: Collecting and maintaining accurate contact information " -"for WHOIS/RDAP directories." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 8 (header) -msgid "Technical Services" -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 9 (unordered list) -msgid "" -"**EPP Interface**: Translating user actions into EPP commands sent to the " -"Registry." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 9 (unordered list) -msgid "" -"**DNS Hosting**: Most registrars provide default nameservers, allowing users" -" to manage their DNS records (A, MX, CNAME) via a user-friendly dashboard." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 9 (unordered list) -msgid "**DNSSEC**: Facilitating the rotation and publication of DS records." -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 10 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/registrar.mdx:block 12 (unordered list) -msgid "" -"[Domain name registrar](https://en.wikipedia.org/wiki/Domain_name_registrar)" -" on Wikipedia" -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 1 (header) -msgid "" -"title: Registry description: Understand the Domain Name Registry? Learn how " -"these organizations manage the central database for all domain names under a" -" specific TLD." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 3 (paragraph) -msgid "" -"A **Registry** (or Registry Operator) is the organization responsible for " -"maintaining the master database of all domain names registered under a " -"specific Top-Level Domain (TLD)." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 4 (header) -msgid "Technical Roles" -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 5 (paragraph) -msgid "" -"The Registry is the authoritative source for its TLD. Its duties include:" -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 6 (unordered list) -msgid "" -"**Zone File Generation**: Publishing the zone file that directs global DNS " -"traffic to the correct nameservers for every domain in the extension." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 6 (unordered list) -msgid "" -"**IDN & DNSSEC Management**: Enforcing policies for special characters and " -"managing the cryptographic signing of the TLD zone." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 6 (unordered list) -msgid "" -"**WHOIS/RDAP Server**: Operating the directory service that provides public " -"information about registered domains." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 7 (header) -msgid "Operational Roles" -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 8 (paragraph) -msgid "" -"Registries generally do not sell directly to the public. Instead, they:" -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 9 (unordered list) -msgid "Define the **Acceptable Use Policies** for the TLD." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 9 (unordered list) -msgid "Set the wholesale price for domains." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 9 (unordered list) -msgid "Accredit and connect with **Registrars** via EPP." -msgstr "" - -#: src/content/docs/en/definitions/registry.mdx:block 12 (unordered list) -msgid "" -"[Domain name registry](https://en.wikipedia.org/wiki/Domain_name_registry) " -"on Wikipedia" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 1 (header) -msgid "" -"title: Top-Level Domain (TLD) description: An overview of Top-Level Domains " -"(TLDs), their classification (gTLD, ccTLD, etc.), and the structure of the " -"DNS root zone." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 2 (paragraph) -msgid "" -"A **Top-Level Domain (TLD)** is the rightmost segment of a domain name " -"(after the last dot). TLDs are the highest level of the DNS hierarchy below " -"the root." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 3 (header) -msgid "TLD Classifications" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 4 (header) -msgid "Generic TLD (gTLD)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 5 (paragraph) -msgid "" -"Originally intended for specific use cases, most gTLDs are now open to " -"everyone." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 6 (unordered -#: list) -msgid "" -"**Legacy**: `.com` (commercial), `.net` (network), `.org` (organization)." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 6 (unordered -#: list) -msgid "" -"**New gTLDs**: Thousands of niche extensions like `.app`, `.blog`, `.guru`." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 6 (unordered -#: list) -msgid "" -"**Restricted**: Domains like `.bank` or `.pharmacy` require verification of " -"eligibility." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 6 (unordered -#: list) -msgid "**Brand**: Closed TLDs for corporations, e.g., `.google` or `.bmw`." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 7 (header) -msgid "Country Code TLD (ccTLD)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 8 (paragraph) -msgid "" -"Reserved for countries and territories (two letters, based on ISO 3166)." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 9 (unordered -#: list) -msgid "" -"**Examples**: `.uk` (United Kingdom), `.de` (Germany), `.io` (British Indian" -" Ocean Territory)." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 9 (unordered -#: list) -msgid "" -"**Rules**: Policies vary strictly by country. Some require local residency " -"(e.g., `.no`, `.ca`), while others are marketed globally (e.g., `.tv`, " -"`.ai`)." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 10 (header) -msgid "Sponsored TLD (sTLD)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 11 (paragraph) -msgid "Managed by private organizations representing a specific community." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 12 (unordered -#: list) -msgid "`.gov` (US Government)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 12 (unordered -#: list) -msgid "`.edu` (Accredited US institutions)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 12 (unordered -#: list) -msgid "`.aero` (Aviation industry)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 13 (header) -msgid "Infrastructure TLD" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 14 (unordered -#: list) -msgid "" -"`.arpa`: Managed by IANA, used exclusively for technical infrastructure " -"(e.g., reverse DNS lookups)." -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 15 (header) -msgid "Reserved TLDs" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 16 (paragraph) -msgid "" -"Per [RFC 2606](https://tools.ietf.org/html/rfc2606), four TLDs are " -"permanently reserved for testing and documentation to avoid confusion in " -"production environments:" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 17 (unordered -#: list) -msgid "`.test`" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 17 (unordered -#: list) -msgid "`.example`" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 17 (unordered -#: list) -msgid "`.invalid`" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 17 (unordered -#: list) -msgid "`.localhost`" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 19 (unordered -#: list) -msgid "" -"[Top-level domain (Wikipedia)](https://en.wikipedia.org/wiki/Top-" -"level_domain)" -msgstr "" - -#: src/content/docs/en/definitions/top-level-domain.mdx:block 19 (unordered -#: list) -msgid "[IANA Root Zone Database](https://www.iana.org/domains/root/db)" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 1 (header) -msgid "" -"title: WHOIS Protocol description: Get an overview of WHOIS. Learn how this " -"protocol is used to query databases for information about the registered " -"user or assignees of a domain name." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 3 (paragraph) -msgid "" -"WHOIS is a text-based query/response protocol (listening on **TCP Port 43**)" -" widely used for querying databases that store the registered users or " -"assignees of an Internet resource, such as a domain name or an IP address " -"block." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 4 (header) -msgid "Core Use Cases" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 5 (unordered list) -msgid "" -"**Availability Check**: Verifying if a specific domain name is available for" -" registration." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 5 (unordered list) -msgid "" -"**Ownership Identification**: Identifying the Registrant or the Registrar " -"managing the domain." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 5 (unordered list) -msgid "" -"**Technical Troubleshooting**: Finding the authoritative nameservers or the " -"technical contacts to resolve network issues." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 5 (unordered list) -msgid "" -"**Legal & Abuse**: Providing a record for law enforcement, intellectual " -"property protection, and abuse reporting." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 6 (header) -msgid "Thick vs. Thin Registries" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 7 (paragraph) -msgid "" -"Understanding WHOIS responses requires understanding how the TLD Registry " -"stores data." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 8 (header) -msgid "Thin Registry (e.g., .com, .net)" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 9 (paragraph) -msgid "" -"The Registry only stores technical data (DNSSEC, Nameservers) and a pointer " -"to the Registrar." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 10 (paragraph) -msgid "" -"To get the full contact details, a second WHOIS query must be sent to the " -"**Registrar's WHOIS server**." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 11 (header) -msgid "Thick Registry (e.g., .org, .info, most ccTLDs)" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 12 (paragraph) -msgid "" -"The Registry stores *all* information, including the Registrant's contact " -"details and administrative data." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 13 (paragraph) -msgid "A single query to the Registry provides the full record." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 14 (header) -msgid "Example: Recursive WHOIS Query" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 15 (paragraph) -msgid "" -"The standard `whois` command line tool often handles the \"Thin Registry\" " -"redirect automatically. However, seeing the raw steps helps understand the " -"protocol." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 16 (paragraph) -msgid "" -"In the example below for a **Thin TLD** (`.com`), we first query the " -"Registry, which points us to the Registrar." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 17 (header) -msgid "Request to the Registry (Verisign)" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 18 (paragraph) -msgid "Note the `Registrar WHOIS Server` field in the response." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 19 (code) -msgid "" -"$ whois --verbose example.com -h whois.verisign-grs.com.\n" -"Using server whois.verisign-grs.com..\n" -"Query string: \"example.com\"\n" -"\n" -" Domain Name: EXAMPLE.COM\n" -" Registry Domain ID: 2336799_DOMAIN_COM-VRSN\n" -" Registrar WHOIS Server: whois.iana.org\n" -" Registrar URL: http://res-dom.iana.org\n" -" Updated Date: 2025-08-14T07:01:39Z\n" -" Creation Date: 1995-08-14T04:00:00Z\n" -" Registry Expiry Date: 2026-08-13T04:00:00Z\n" -" Registrar: RESERVED-Internet Assigned Numbers Authority\n" -" Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited\n" -" Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited\n" -" Name Server: A.IANA-SERVERS.NET\n" -" Name Server: B.IANA-SERVERS.NET\n" -" DNSSEC: signedDelegation\n" -">>> Last update of whois database: 2025-11-20T08:05:54Z <<<\n" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 20 (header) -msgid "Request to the Registrar (IANA)" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 21 (paragraph) -msgid "" -"Following the referral, we query the specific Registrar to get the ownership" -" details." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 22 (code) -msgid "" -"$ whois --verbose example.com -h whois.iana.org\n" -"Using server whois.iana.org..\n" -"Query string: \"example.com\"\n" -"\n" -"% IANA WHOIS server\n" -"% for more information on IANA, visit http://www.iana.org\n" -"% This query returned 1 object\n" -"\n" -"domain: EXAMPLE.COM\n" -"organisation: Internet Assigned Numbers Authority\n" -"created: 1992-01-01\n" -"source: IANA\n" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 23 (header) -msgid "Privacy Considerations" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 24 (paragraph) -msgid "" -"Since the implementation of the **GDPR** (General Data Protection " -"Regulation) and similar global privacy laws, the WHOIS output has changed " -"significantly." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 25 (unordered list) -msgid "" -"**Data Redaction**: Most personal fields (Name, Email, Phone) are now " -"replaced with placeholders like `DATA REDACTED` or `Redacted for Privacy`." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 25 (unordered list) -msgid "" -"**Privacy Proxies**: Registrars often provide services that replace the " -"registrant's details with the registrar's generic contact information to " -"prevent spam and harassment." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 25 (unordered list) -msgid "" -"**Tiered Access**: Full, unredacted data is often no longer publicly " -"available anonymously and requires a legitimate legal request or " -"accreditation." -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 26 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/definitions/whois.mdx:block 28 (unordered list) -msgid "" -"[RFC 3912 - WHOIS Protocol " -"Specification](https://datatracker.ietf.org/doc/html/rfc3912)" -msgstr "" - -#: src/content/docs/en/developing/contributing/code-of-conduct.md:block 1 -#: (header) -msgid "" -"title: Code of Conduct description: Code of conduct outlining community " -"standards and guidelines for respectful collaboration within the project." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 1 -#: (header) -msgid "" -"title: Pull Requests description: Instructions for submitting pull requests." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 2 -#: (paragraph) -msgid "" -"When you want to propose a change to the source code, you will need to " -"create a Pull Request on this project's GitHub repository." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 3 -#: (paragraph) -msgid "" -"Note that if you are modifying several different parts, you should split it " -"into multiple Pull Requests. This will make it easier to review and merge " -"your proposals." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 4 -#: (paragraph) -msgid "You will then be asked to fill in a few fields:" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 5 -#: (header) -msgid "Title" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 6 -#: (paragraph) -msgid "" -"The Pull Request title should briefly describe the proposed changes. Please " -"be concise and precise. For example, to add support for a new, fictitious " -"provider called \"FakeRegistrar,\" you could write something like \"Add " -"support for FakeRegistrar provider\"." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 7 -#: (header) -msgid "Description" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 8 -#: (paragraph) -msgid "" -"For complex changes, please provide as much detail as possible. If your " -"changes modify an existing API, you must mention this in the description, as" -" it may have repercussions on projects related to Domain Watchdog." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 9 -#: (paragraph) -msgid "" -"If the proposal modifies the frontend, it would be best to include " -"screenshots (desktop and mobile versions) to better visualize the proposal." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 10 -#: (header) -msgid "Change Type" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 11 -#: (paragraph) -msgid "A checklist allows you to choose the type of change proposed:" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 12 -#: (code) -msgid "" -"- [ ] Bug fix (non-breaking change which fixes an issue)\n" -"- [ ] New feature (non-breaking change which adds functionality)\n" -"- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)\n" -"- [ ] This change requires a documentation update\n" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 13 -#: (paragraph) -msgid "" -"This checklist helps to better identify the project's impact on the PR." -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 14 -#: (header) -msgid "Compliance Checklist" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 15 -#: (paragraph) -msgid "" -"The checklist below allows you to self-assess the conformity of your " -"proposal before submitting it for review:" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 16 -#: (code) -msgid "" -"- [x] Commit names follow the Conventional Commits convention\n" -"- [x] I have checked the entire code before submitting it\n" -"- [x] I have updated the documentation related to my commits\n" -"- [x] My code does not generate errors\n" -msgstr "" - -#: src/content/docs/en/developing/contributing/pull-requests.mdx:block 17 -#: (paragraph) -msgid "" -"In any case, if you experience any difficulties creating a PR, feel free to " -"open one; we will help you ensure it complies with these requirements." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 1 -#: (header) -msgid "" -"title: Implementing a new provider description: Step-by-step guide to adding" -" a new Provider, with backend, frontend, and testing instructions to " -"integrate a registrar into the project." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 2 -#: (paragraph) -msgid "" -"import {FileTree, Steps, Code, LinkCard} from " -"\"@astrojs/starlight/components\";" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 3 -#: (paragraph) -msgid "" -"This project aims to be compatible with as many registrars as possible, " -"giving users a choice when creating a Connector." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 4 -#: (paragraph) -msgid "" -"::::caution Only registrars with a public and documented API can be offered." -" Using a registrar's private API is strictly prohibited. ::::" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 5 -#: (paragraph) -msgid "" -"Adding a new Provider is straightforward. Simply follow the steps below." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 6 -#: (paragraph) -msgid "" -"This guide explains how to add support for a new domain registrar. You’ll " -"implement both the Backend (Provider logic) and the Frontend (configuration " -"form)." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 7 -#: (header) -msgid "Prerequisites" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 9 -#: (header) -msgid "Backend" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 10 -#: (paragraph) -msgid "" -"In this section, you’ll implement the logic required to interact with the " -"new Provider’s API." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 12 -#: (code) -msgid "" -"1. Add the necessary class properties and assertions.\n" -" The DTO class must extend `DefaultProviderDto`.\n" -"\n" -" Only include properties required for user authentication, domain name registration, and any legally required consents.\n" -" \n" -"\n" -"1. Create a new Provider class.\n" -" \n" -" - src\n" -" - Service\n" -" - Provider\n" -" - AbstractProvider.php defines the signature of methods\n" -" - **MySuperRegistrarProvider.php** your new Provider\n" -" \n" -"\n" -"1. The class must extend `AbstractProvider`.\n" -" Refer to the existing Providers for implementation examples.\n" -" \n" -" ::::note\n" -" You now need to implement the methods defined in `AbstractProvider`.\n" -"\n" -" Refer to the official Provider API documentation as needed.\n" -" ::::\n" -"\n" -"1. Implement the `assertAuthentication` method.\n" -"\n" -" This method validates user authentication data.\n" -" Make a request to the Provider’s API to verify that the user’s credentials are valid.\n" -"\n" -" The method must return `void` when authentication succeeds.\n" -" ::::tip\n" -" If an issue occurs, throw an appropriate exception from the `App\\Exception\\Provider` namespace.\n" -" ::::\n" -" \n" -"\n" -"1. Implement the `getCachedTldList` method.\n" -" cacheItemPool->getItem('app.provider.my-super-registrar.supported-tld');\n" -" }`} lang=\"php\" title='MySuperRegistrarProvider.php' mark={['my-super-registrar']} />\n" -"\n" -" This method returns the cache entry holding the list of TLDs supported by this Provider.\n" -" Even if the API does not currently provide this information, implement the method for future compatibility.\n" -"\n" -"1. Implement the `getSupportedTldList` method.\n" -"\n" -" If the Provider API does not offer a way to retrieve supported TLDs, return an empty array `[]`.\n" -" Otherwise, call the API and return the list of supported TLDs.\n" -" \n" -"\n" -"1. Implement the `isSupported` method (if necessary).\n" -" Override `isSupported` **only if** the Provider API cannot list supported TLDs. In that case, return `true` to indicate that all TLDs are potentially valid.\n" -"\n" -"1. Implement the `orderDomain` method.\n" -"\n" -" Follow the Provider's API documentation to implement domain ordering using the required properties.\n" -" ::::tip\n" -" As with authentication, you may throw generic Provider exceptions in case of an error.\n" -" ::::\n" -" \n" -"\n" -"1. Add your Provider to the `ConnectorProvider` enumeration.\n" -" MySuperRegistrarProvider::class,\n" -" };\n" -" }`} lang=\"php\" title='src/Config/ConnectorProvider.php' />\n" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 14 -#: (paragraph) -msgid "" -"**Well done!** 🎉 You have now completed the Backend implementation. Let’s " -"continue with the Frontend! 🚀" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 15 -#: (header) -msgid "Frontend" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 17 -#: (code) -msgid "" -"1. Add the fields corresponding to the DTO you created earlier.\n" -" Check existing forms for reference.\n" -" If the Provider API does not allow retrieving supported TLDs, display this information as in the other forms.\n" -"\n" -"1. Add your Provider to the `ConnectorProvider` enumeration.\n" -" The value must exactly match the one defined in PHP.\n" -"\n" -" \n" -"\n" -"1. Add the API terms of service link and the reference to your new form in the `index.ts` configuration file.\n" -" = {\n" -" // ...\n" -" [ConnectorProvider.MY_SUPER_REGISTRAR]: {\n" -" tosLink: 'https://...',\n" -" form: MySuperRegistrarConnectorForm\n" -" }\n" -" }`} lang=\"ts\" title='assets/utils/providers/index.ts' />\n" -"\n" -"1. Ensure the interface renders correctly and fix any display issues.\n" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 19 -#: (paragraph) -msgid "**Great job!** 🎉 Your Frontend implementation is now complete." -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 20 -#: (header) -msgid "Testing" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 22 -#: (code) -msgid "" -" $this->testGenericProvider(ConnectorProvider::MY_SUPER_REGISTRAR, [\n" -" 'waiveRetractationPeriod' => true,\n" -" 'acceptConditions' => true,\n" -" 'ownerLegalAge' => true,\n" -" 'token' => $token,\n" -" ]);\n" -" }`} lang=\"php\" title='tests/Service/Provider/AbstractProviderTest.php' />\n" -"\n" -"1. Create a Symfony configuration parameter connecting the environment variable to the credentials.\n" -"\n" -"1. Run the tests with PHPUnit:\n" -" ```shell\n" -" php vendor/bin/phpunit\n" -" ```\n" -"1. Ensure the test passes.\n" -"If it fails, fix the implementation accordingly.\n" -"Consider enabling code coverage to identify executed sections.\n" -msgstr "" - -#: src/content/docs/en/developing/implementing-new-provider.mdx:block 24 -#: (paragraph) -msgid "That's it! You’ve now finished implementing a new Provider. ✨" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 1 (header) -msgid "" -"title: Technical stack description: Overview of the project's technical " -"stack, including frameworks, languages, and architecture used throughout the" -" system." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 2 (paragraph) -msgid "" -"This page lists the main technologies used in the project, with links to " -"their documentation. Specific version information can be found in the " -"project’s dependency files (`composer.lock`, `package.json`, etc.). The " -"architecture diagram below summarizes how these services interact." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 3 (paragraph) -msgid "" -"![Technical stack diagram](../../../../assets/images/dw-stack-diagram.png)" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 5 (header) -msgid "Framework" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 6 (paragraph) -msgid "The programming language is **PHP**." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 7 (paragraph) -msgid "" -"The backend is developed using the **Symfony** framework " -"([documentation](https://symfony.com/doc))." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 8 (paragraph) -msgid "" -"The API is made possible by the **API Platform** project " -"([documentation](https://api-platform.com/docs/symfony/))." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 9 (header) -msgid "SQL database" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 10 (paragraph) -msgid "" -"This project requires a **PostgreSQL** database " -"([documentation](https://www.postgresql.org/docs/current/))." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 11 (paragraph) -msgid "" -"Other database types cannot be used because some migrations were " -"specifically written to leverage the performance of this database management" -" system." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 12 (header) -msgid "Key-value database" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 13 (paragraph) -msgid "A **Redis-compatible** key-value database is required to:" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 14 (unordered -#: list) -msgid "Cache certain values" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 14 (unordered -#: list) -msgid "Implement locks to limit the possibility of conditional raises" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 14 (unordered -#: list) -msgid "" -"Store messages to be distributed to workers to process asynchronous actions." -" For example: updating domain names in a Watchlist on a high-priority RDAP " -"client queue." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 15 (header) -msgid "Time Series database" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 16 (paragraph) -msgid "" -"The **InfluxDB** database is optional. A data point is added for the " -"following events:" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 17 (unordered -#: list) -msgid "" -"RDAP requests from your instance: response time, requested domain name, HTTP" -" status code, IP address of the RDAP server, etc." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 17 (unordered -#: list) -msgid "" -"User notifications: adding events to a domain name, changing EPP statuses, " -"etc." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 18 (header) -msgid "SSO authentication" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 19 (paragraph) -msgid "An **OAuth 2.0** server is not required to authenticate users." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 20 (paragraph) -msgid "" -"Using Single Sign-On (SSO) allows you to delegate user authentication to a " -"third party. This can be useful if you only want people within your " -"organization to be able to use this project instance. Furthermore, you can " -"then configure advanced security policies such as passwordless login, " -"passkeys, multifactor authentication, and more." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 23 (paragraph) -msgid "The language for frontend development is **TypeScript**." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 24 (paragraph) -msgid "" -"The framework used for the frontend is **React** " -"([documentation](https://react.dev/reference/react))." -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 25 (header) -msgid "Component Library" -msgstr "" - -#: src/content/docs/en/developing/technical-stack.mdx:block 26 (paragraph) -msgid "" -"The component library used is **Ant Design** " -"([documentation](https://ant.design/components/overview/))." -msgstr "" - -#: src/content/docs/en/developing/translation.mdx:block 1 (header) -msgid "" -"title: Translation description: This project is available in several " -"languages, the current translation status is available here." -msgstr "" - -#: src/content/docs/en/developing/translation.mdx:block 2 (paragraph) -msgid "" -"The project is translated into several languages to allow as many people as " -"possible to easily understand the interface. Feel free to contribute and add" -" a translation!" -msgstr "" - -#: src/content/docs/en/developing/translation.mdx:block 3 (paragraph) -msgid "The current status of the translation is given below." -msgstr "" - -#: src/content/docs/en/developing/translation.mdx:block 4 (paragraph) -msgid "" -"[![Translation status](https://weblate.vinceh121.me/widget/domain-" -"watchdog/domain-watchdog-dashboard/open-" -"graph.png)](https://weblate.vinceh121.me/engage/domain-watchdog/)" -msgstr "" - -#: src/content/docs/en/developing/translation.mdx:block 5 (paragraph) -msgid "" -"If you don't find your language in the list above, feel free to open an " -"issue on the project repository and request that a new language be added." -msgstr "" - -#: src/content/docs/en/developing/translation.mdx:block 6 (paragraph) -msgid "" -"Once the language is added, you can start suggesting translations in the " -"translation space. This project uses Weblate for community translation." -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 1 (header) -msgid "" -"title: Connector description: Learn how the Backorder Connector works, its " -"flow, requirements, and how it integrates with registrar APIs for domain " -"backordering." -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 2 (paragraph) -msgid "import {LinkCard, Steps} from '@astrojs/starlight/components';" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 3 (paragraph) -msgid "" -"A Connector allows Domain Watchdog to communicate with an external domain " -"registrar’s API to perform actions such as domain registration." -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 4 (header) -msgid "Create a Connector" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 6 (ordered list) -msgid "" -"Enter the required information using the credentials obtained from your " -"provider’s customer area :::tip{icon=\"heart\"} A link allows you to " -"directly access the Provider's page to retrieve this authentication " -"information :::" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 6 (ordered list) -msgid "" -"Review and consent to the required terms. As a reminder, you can delete a " -"Connector at any time from your personal space." -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 6 (ordered list) -msgid "" -"Click the button to create your Connector. **Congratulations 🎉** " -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 7 (header) -msgid "Legal considerations" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 8 (paragraph) -msgid "" -"These legal requirements ensure that all domain operations comply with " -"registrar policies and applicable regulations." -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 9 (paragraph) -msgid "" -"Domain Watchdog acts only as a technical interface and does not serve as a " -"payment intermediary. Your credentials are transmitted directly to the " -"provider’s API for domain operations. By creating a Connector, you consent " -"to the provider’s terms and the use of your credentials for authorized " -"operations." -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 10 (paragraph) -msgid "In particular, you must consent to:" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 11 (unordered -#: list) -msgid "Accept the provider’s API Terms of Use" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 11 (unordered -#: list) -msgid "Confirm that you are of legal age to accept these terms" -msgstr "" - -#: src/content/docs/en/features/backorder/connector.mdx:block 12 (paragraph) -msgid "" -"Since the terms of use may change at any time, the link to these terms is " -"always accessible on the page listing the Connectors." -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 1 -#: (header) -msgid "" -"title: Supported registrar list description: List of registrars supported " -"for domain backorders, with details on compatibility." -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 2 -#: (paragraph) -msgid "import {LinkButton} from '@astrojs/starlight/components';" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 3 -#: (paragraph) -msgid ":::caution[Reminder]" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 4 -#: (unordered list) -msgid "" -"Please note that this project is NOT affiliated IN ANY WAY with the API " -"Providers used to order domain names." -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 4 -#: (unordered list) -msgid "" -"The project installers are responsible for the use of their own instance." -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 4 -#: (unordered list) -msgid "" -"Under no circumstances will the owner of this project be held responsible " -"for other cases over which he has no control. :::" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 5 -#: (header) -msgid "OVH" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "Field" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "Required" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "App key" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "the key that allows OVH to identify your application" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "App secret key" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "the secret key associated with your application" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "Consumer key" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "the secret key that links the application to your account" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "Endpoint" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "" -"allows you to choose which server to use (Europe, United States or Canada)" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "Subsidiary" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "the country linked to the OVH subsidiary associated with your account" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "Pricing mode" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 6 -#: (table) -msgid "" -"choose whether you want to pay for a Premium domain name or only standard " -"prices" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 7 -#: (paragraph) -msgid "" -"" -" Retrieve my token from the OVH website " -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 8 -#: (header) -msgid "Gandi" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 9 -#: (table) -msgid "Token" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 9 -#: (table) -msgid "your account authentication token" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 9 -#: (table) -msgid "Sharing ID" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 9 -#: (table) -msgid "indicates the organization that will pay for the ordered product" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 9 -#: (table) -msgid "Optional" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 10 -#: (paragraph) -msgid "" -" Retrieve my " -"token from the Gandi website " -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 11 -#: (header) -msgid "Namecheap" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 12 -#: (paragraph) -msgid "" -":::caution This provider requires that the IPv4 address of your instance be " -"entered on its web interface when creating the API connection. This " -"information must also be entered in the configuration. :::" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 13 -#: (table) -msgid "API user" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 13 -#: (table) -msgid "the API user as given by the Provider" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 13 -#: (table) -msgid "API key" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 13 -#: (table) -msgid "the API key as given by the Provider" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 14 -#: (paragraph) -msgid "" -" Retrieve my" -" token from the Namecheap website " -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 15 -#: (header) -msgid "AutoDNS" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 16 -#: (paragraph) -msgid "" -":::caution This provider does not provide a list of supported TLD. Please " -"double-check if the domain you want to register is supported. :::" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "Username" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "the account username" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "Password" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "the account password" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "Owner consent" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "purchase consent" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "Context" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "the \"context\" as given by the Provider" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "Contact ID" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 17 -#: (table) -msgid "Contact ID of the domain name holder of the purchased domains" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 18 -#: (paragraph) -msgid "" -" Retrieve my token from " -"the AutoDNS website " -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 19 -#: (header) -msgid "Name.com" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 22 -#: (paragraph) -msgid "" -" Retrieve my token from " -"the Name.com website " -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 23 -#: (header) -msgid "Custom EPP server" -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 24 -#: (paragraph) -msgid "" -"This type of connector allows you to directly link your instance to a " -"registry via the EPP protocol. This requires that you have signed a contract" -" with a registry; you are then considered a registry in your own right." -msgstr "" - -#: src/content/docs/en/features/backorder/supported-registrar.mdx:block 25 -#: (paragraph) -msgid "" -"Currently, the implementation of this feature has not been tested; your " -"feedback is important!" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 1 (header) -msgid "" -"title: Getting started description: Step-by-step guide to creating an " -"account, searching domains, tracking changes, and enabling auto-purchase " -"with Connectors." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 3 (paragraph) -msgid "" -"On this page, you'll find a step-by-step guide to getting started with " -"**Domain Watchdog** and exploring its main features. The sidebar menu on the" -" left allows you to quickly navigate between all documentation sections." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 4 (paragraph) -msgid "" -":::note Depending on the configuration of the instance on which you're " -"performing these actions, some options may be limited or hidden. :::" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 5 (header) -msgid "Create an account" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 6 (paragraph) -msgid "" -"If your instance allows user registration, you can create an account " -"directly from the interface." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 7 (paragraph) -msgid "![User registration](../../../../assets/images/user-register.png)" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 9 (paragraph) -msgid "" -"After confirming your email, you can log in and start using all available " -"features." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 10 (header) -msgid "Search for a domain name" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 11 (paragraph) -msgid "" -"Domain Watchdog uses the **RDAP protocol**, the modern replacement for " -"WHOIS, to retrieve accurate information about domain names." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 12 (paragraph) -msgid "" -"![Search for a domain name](../../../../assets/images/search-domain.png)" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 13 (paragraph) -msgid "" -":::tip[Read more] To read the documentation related to domain name search, " -"please click on the link below." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 14 (paragraph) -msgid "" -" :::" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 15 (header) -msgid "Create a Watchlist" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 16 (paragraph) -msgid "" -"A **Watchlist** is a collection of domain names, triggers, and optionally an" -" API Connector. It allows you to:" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 17 (unordered list) -msgid "monitor domain status changes" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 17 (unordered list) -msgid "" -"receive notifications (email or webhook: Slack, Mattermost, Discord, etc.)" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 17 (unordered list) -msgid "optionally auto-purchase a domain when it expires" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 18 (paragraph) -msgid "![Create a Watchlist](../../../../assets/images/create-watchlist.png)" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 19 (paragraph) -msgid "" -":::tip[Read more] To read the documentation related to the Watchlist, please" -" click on the link below." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 20 (paragraph) -msgid "" -" :::" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 21 (header) -msgid "Watchlist notifications" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 22 (paragraph) -msgid "" -"When a domain changes state, you’ll automatically receive a notification. " -"You can also export domain events as **iCalendar** feeds." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 24 (paragraph) -msgid "" -"A **Connector** is used to automatically order (backorder) a domain name " -"using its provider’s API." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 25 (paragraph) -msgid "![Create a Connector](../../../../assets/images/create-connector.png)" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 26 (paragraph) -msgid "" -":::tip[Read more] To read the documentation related to Connector, please " -"click on the link below." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 27 (paragraph) -msgid "" -" :::" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 28 (header) -msgid "Supported registrar list" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 29 (paragraph) -msgid "" -"" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 30 (header) -msgid "Tracking table" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 31 (paragraph) -msgid "" -"The Tracking table page displays a list of all the domain names you monitor " -"via your Watchlists. This list is ordered, meaning the domain names are " -"arranged according to their estimated deletion date." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 32 (paragraph) -msgid "![Tracking table](../../../../assets/images/tracking-table.png)" -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 33 (paragraph) -msgid "" -":::tip[Read more] To read the documentation related to the Tracking table, " -"please click on the link below." -msgstr "" - -#: src/content/docs/en/features/index.mdx:block 34 (paragraph) -msgid "" -" :::" -msgstr "" - -#: src/content/docs/en/features/infrastructure/icann-registrar-list.mdx:block -#: 1 (header) -msgid "title: ICANN Registrar list" -msgstr "" - -#: src/content/docs/en/features/infrastructure/tld-list.mdx:block 1 (header) -msgid "title: TLD list" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 1 (header) -msgid "title: Domain search description: Domain search feature overview" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 2 (paragraph) -msgid "" -"import {Steps} from \"@astrojs/starlight/components\" import {Kbd} from " -"\"starlight-kbd/components\"" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 3 (paragraph) -msgid "" -":::tip[Did you know?] In this project, everything is done to minimize the " -"number of requests to RDAP servers. Limitations imposed on end users help " -"control the flow of RDAP requests. These limitations can be configured for " -"each instance, in the environment variables. :::" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 4 (paragraph) -msgid "" -"The domain search feature allows users to look up information about a domain" -" name through the user interface." -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 5 (paragraph) -msgid "To search for a domain name:" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 7 (paragraph) -msgid "" -"![Search for a domain name](../../../../../assets/images/search-domain.png)" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 8 (paragraph) -msgid "" -"If the extension you are searching for does **not** have an official RDAP " -"server, an error message will inform you that no RDAP server is available." -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 9 (header) -msgid "Force Update" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 10 (paragraph) -msgid "" -"By default, if the domain information stored in the database is still " -"considered valid, the system returns the existing record without performing " -"a new RDAP query." -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 11 (paragraph) -msgid "If you need to force an RDAP update for a given domain:" -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 12 (unordered -#: list) -msgid "" -"Press when submitting " -"the search." -msgstr "" - -#: src/content/docs/en/features/search/domain-search.mdx:block 13 (paragraph) -msgid "This triggers a fresh lookup against the RDAP server." -msgstr "" - -#: src/content/docs/en/features/tracking/tracking-table.mdx:block 1 (header) -msgid "title: Tracking table" -msgstr "" - -#: src/content/docs/en/features/tracking/tracking-table.mdx:block 2 -#: (paragraph) -msgid "![Tracking table](../../../../../assets/images/tracking-table.png)" -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 1 (header) -msgid "" -"title: Watchlist description: Learn how the domain watchlist works, enabling" -" users to monitor domains and receive updates on changes." -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 2 (paragraph) -msgid "import {Steps} from '@astrojs/starlight/components';" -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 3 (paragraph) -msgid "" -"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." -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 4 (paragraph) -msgid "" -"If a domain has expired and a connector is linked to the Watchlist, then an " -"order attempt will be made though the Connector provider's API." -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 5 (paragraph) -msgid "" -":::note If the same domain name is present on several Watchlists, on the " -"same principle as the race condition, it is not possible to predict in " -"advance which user will win the domain name. The choice is left to chance..." -" :::" -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 7 (paragraph) -msgid "" -"![Create a Watchlist](../../../..//../assets/images/create-watchlist.png)" -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 9 (paragraph) -msgid "Now, it's your turn to create a Watchlist!" -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 10 (header) -msgid "Limitations" -msgstr "" - -#: src/content/docs/en/features/tracking/watchlist.mdx:block 11 (paragraph) -msgid "" -"Depending on the instance configuration, there are several limitations to " -"frame user behavior." -msgstr "" - -#: src/content/docs/en/index.mdx:block 1 (header) -msgid "" -"title: Domain Watchdog description: An app that uses RDAP to collect " -"publicly available info about domains, track their history, and purchase " -"then when they expire template: splash hero: tagline: Your companion in the " -"quest for domain names 🔍 image: file: ../../../assets/logo.png actions: - " -"text: Get started link: /en/features icon: right-arrow - text: Demo link: " -"https://demo.domainwatchdog.eu icon: external variant: minimal" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 1 (header) -msgid "" -"title: Configuration description: Configuration guide explaining environment" -" variables and settings required to run and customize the project." -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 2 (paragraph) -msgid "import {LinkCard} from '@astrojs/starlight/components';" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 4 (header) -msgid "Environment variables" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Variable" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Default" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`DATABASE_URL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Please check Symfony config" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OUTGOING_IP`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Outgoing IPv4, needed for some providers" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`INFLUXDB_ENABLED`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Enable the connection with InfluxDB" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`false`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`INFLUXDB_URL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "InfluxDB URL" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`http://localhost:8086`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`INFLUXDB_TOKEN`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "InfluxDB token" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`INFLUXDB_BUCKET`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "InfluxDB bucket name" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`domainwatchdog`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`INFLUXDB_ORG`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "InfluxDB organization" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`LIMITED_FEATURES`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Limit certain features for users" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`LIMIT_MAX_WATCHLIST`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Maximum number of Watchlists per user" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`0`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`LIMIT_MAX_WATCHLIST_DOMAINS`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Maximum number of domains per Watchlist" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`LIMIT_MAX_WATCHLIST_WEBHOOKS`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Maximum number of webhooks per Watchlist" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`MAILER_SENDER_NAME`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Name of the sender of emails" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`Domain Watchdog`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`MAILER_SENDER_EMAIL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Sender's email address" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`notifications@example.com`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`REGISTRATION_ENABLED`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Enable user registration" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`true`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`REGISTRATION_VERIFY_EMAIL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Verify email addresses during registration" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`MAILER_DSN`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`null://null`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OAUTH_CLIENT_ID`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Client ID (OAuth 2.0) for using external SSO" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OAUTH_CLIENT_SECRET`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Client secret (OAuth 2.0)" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OAUTH_AUTHORIZATION_URL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Authorization URL (OAuth 2.0)" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OAUTH_TOKEN_URL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Token URL (OAuth 2.0)" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OAUTH_USERINFO_URL`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "User Info URL (OAuth 2.0)" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "`OAUTH_SCOPE`" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 5 (table) -msgid "Scope (OAuth 2.0)" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 6 (header) -msgid "Authentication" -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 7 (paragraph) -msgid "" -"Currently, there is no way to delete your account, reset your password, or " -"enable multifactor authentication." -msgstr "" - -#: src/content/docs/en/install-config/configuration.mdx:block 8 (paragraph) -msgid "" -"Registering users directly in the interface is recommended for individual " -"instances. For multi-user environments, the recommended method is to use " -"external SSO via the OAuth 2.0 protocol." -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 1 -#: (header) -msgid "" -"title: Docker Compose installation description: Guide to installing the " -"project using Docker Compose, with setup steps, and deployment notes." -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 3 -#: (ordered list) -msgid "" -"Download the [docker-compose.yml](https://github.com/maelgangloff/domain-" -"watchdog/blob/develop/docker-compose.yml) and modify it as needed" -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 3 -#: (ordered list) -msgid "" -"Download the [.env](https://github.com/maelgangloff/domain-" -"watchdog/blob/develop/.env) and modify it as needed " -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 3 -#: (ordered list) -msgid "Add static files to customize your instance (under `public/content`)" -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 3 -#: (ordered list) -msgid "Pull the latest version of the Domain Watchdog image from Docker Hub" -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 4 -#: (code) -msgid "docker compose pull\n" -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 5 -#: (ordered list) -msgid "Start the project in production environment" -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 6 -#: (code) -msgid "docker compose up\n" -msgstr "" - -#: src/content/docs/en/install-config/install/docker-compose.mdx:block 7 -#: (paragraph) -msgid "" -"By default, the container listens on http://localhost:8080, but you can " -"configure this in environment variables." -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 1 -#: (header) -msgid "" -"title: Manual installation description: Manual installation guide with " -"system requirements, dependencies, and step-by-step instructions to install " -"the project from source." -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 2 -#: (paragraph) -msgid "" -"import {FileTree, LinkCard, Steps} from '@astrojs/starlight/components';" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 3 -#: (paragraph) -msgid "" -"To deploy a Domain Watchdog instance, please refer to the Symfony " -"documentation on [How to deploy a Symfony " -"application](https://symfony.com/doc/current/deployment.html)." -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 5 -#: (unordered list) -msgid "PHP 8.4 or higher" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 5 -#: (unordered list) -msgid "PostgreSQL 16 or higher" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 6 -#: (paragraph) -msgid "" -"In order to retrieve information about domain names, Domain Watchdog will " -"query the RDAP server responsible for the TLD. It is crucial that the Domain" -" Watchdog instance is placed in a clean environment from which these servers" -" can be queried. In particular, the DNS servers and root certificates of the" -" system must be trusted." -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 7 -#: (header) -msgid "Steps" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 8 -#: (paragraph) -msgid "Clone the repository:" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 9 -#: (code) -msgid "git clone https://github.com/maelgangloff/domain-watchdog.git\n" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 12 -#: (ordered list) -msgid "" -"Generate the cryptographic key pair for the JWT signaturephp bin/console " -"lexik:jwt:generate-keypair\n" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 12 -#: (ordered list) -msgid "Run database migrationsphp bin/console doctrine:migrations:migrate\n" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 12 -#: (ordered list) -msgid "Start the Symfony serversymfony server:start\n" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 12 -#: (ordered list) -msgid "Build assetsphp bin/console assets:install\n" -msgstr "" - -#: src/content/docs/en/install-config/install/manual-install.mdx:block 12 -#: (ordered list) -msgid "" -"Don't forget to set up workers to process the [message " -"queue](https://symfony.com/doc/current/messenger.html) " -msgstr "" - -#: src/content/docs/en/install-config/upgrade.mdx:block 1 (header) -msgid "" -"title: Manual Upgrade description: Upgrade guide explaining how to safely " -"update the project, including migrations, and versioning details." -msgstr "" - -#: src/content/docs/en/install-config/upgrade.mdx:block 2 (paragraph) -msgid "import {Steps} from \"@astrojs/starlight/components\";" -msgstr "" - -#: src/content/docs/en/install-config/upgrade.mdx:block 3 (paragraph) -msgid "" -"**Any updates are your responsibility. Make a backup of the data if " -"necessary.**" -msgstr "" - -#: src/content/docs/en/install-config/upgrade.mdx:block 4 (paragraph) -msgid "Fetch updates from the remote repository:" -msgstr "" - -#: src/content/docs/en/install-config/upgrade.mdx:block 5 (code) -msgid "git pull origin master\n" -msgstr "" - -#: src/content/docs/en/legal/faq.md:block 1 (header) -msgid "title: FAQ" -msgstr "" - -#: src/content/docs/en/legal/license.md:block 1 (header) -msgid "" -"title: License description: Licensing information detailing usage rights, " -"redistribution terms, and legal conditions for contributing and using the " -"project." -msgstr "" - -#: src/content/docs/en/legal/license.md:block 2 (paragraph) -msgid "" -"This entire project is licensed under [*GNU Affero General Public License " -"v3.0 or later*](https://www.gnu.org/licenses/agpl-3.0.txt). Contributions " -"are welcome as long as they do not contravene the Code of Conduct." -msgstr "" - -#: src/content/docs/en/legal/security.md:block 1 (header) -msgid "" -"title: Security policy description: Security policy describing vulnerability" -" reporting, and guidelines to keep the project secure." -msgstr "" - -#: src/content/docs/en/legal/security.md:block 2 (header) -msgid "Reporting a Vulnerability" -msgstr "" - -#: src/content/docs/en/legal/security.md:block 3 (paragraph) -msgid "" -"If you want to report a vulnerability, please contact the maintainer of this" -" repository. Thanks!" -msgstr ""