GlotPress

Translation of Ultimate Multisite: Domain Seller: Lithuanian

Filter ↓ Sort ↓ All (694) Translated (681) Untranslated (0) Waiting (13) Fuzzy (0) Warnings (9)
1 2 3 4 5 6 47
Prio Original string Translation
Products with specific TLDs override catch-all products. For example, a product with .io will be used for .io domains even if a catch-all product exists. You only need one catch-all product — do not create separate products for each TLD. Produktai su specifiniais TLD perrašo catch-all produktus. Pavyzdžiui, produktas su .io bus naudojamas .io domenams, net jei egzistuoja catch-all produktas. Jums reikia tik vieno catch-all produkto — nekurkite atskirų produktų kiekvienam TLD. Details

Products with specific TLDs override catch-all products. For example, a product with .io will be used for .io domains even if a catch-all product exists. You only need one catch-all product — do not create separate products for each TLD.

Produktai su specifiniais TLD perrašo catch-all produktus. Pavyzdžiui, produktas su .io bus naudojamas .io domenams, net jei egzistuoja catch-all produktas. Jums reikia tik vieno catch-all produkto — nekurkite atskirų produktų kiekvienam TLD.
You have to log in to edit this translation.

Meta

Status:
current
Date added (GMT):
2026-04-03 03:04:20
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Limit this product to specific TLDs. Leave empty to make this a catch-all product that prices any TLD not covered by another product. First, the user has provided a text to translate from English to Lithuanian. The text is: "Limit this product to specific TLDs. Leave empty to make this a catch-all product that prices any TLD not covered by another product." I am a professional translation engine, and I must translate this text for a WordPress plugin. I need to return ONLY the translated text. I should use natural language, not explain, not add quotes, and preserve punctuation, formatting, HTML, placeholders (%s, %1$s, %2$d), and variables exactly. I also have a glossary term: "Product" should be translated as "Produktas" (noun). So, wherever "product" appears in the text, I should use "Produktas". Now, let's break down the original text: - "Limit this product to specific TLDs." – This means to restrict this product to certain top-level domains (TLDs). - "Leave empty to make this a catch-all product that prices any TLD not covered by another product." – This means if you leave the field empty, this product will act as a default for any TLD that isn't specifically priced by another product. Key terms to translate: - "product" → "Produktas" (as per glossary) - "TLDs" – This is an acronym for Top-Level Domains. In Lithuanian, it might be kept as "TLD" since it's a technical term, but I should check if there's a common translation. Typically, in technical contexts, acronyms are often left as is or explained. However, since the instruction is to preserve variables and placeholders, and TLDs might be considered a variable term, I should keep it as "TLD" or translate it appropriately. The text says "TLDs" in plural, so I need to handle that. In Lithuanian, "top-level domain" is often translated as "aukščiausio lygio domenas", but in context, "TLD" might be used as is. Since this is for a WordPress plugin, and TLD is a standard term in domain registration, I should probably keep it as "TLD" to maintain clarity. But let's see the instruction: "preserve ... variables exactly." TLDs might be considered a variable, so I should keep it as "TLDs" or translate it naturally. Looking at the glossary, only "Product" is specified. For "TLDs", I need to decide on a translation. I think in Lithuanian, it's common to use "TLD" or "aukščiausio lygio domenai". To keep it natural and consistent with technical jargon, I might use "TLD" but in Lithuanian context, it might be better to translate it. I recall that in some Lithuanian translations for domain-related terms, "TLD" is often left as is or translated as "domėno aukščiausio lygio galūnė". However, for brevity and common usage, "TLD" might be acceptable. But let's think about the sentence structure. The text is instructing the user to limit the product to specific TLDs. In Lithuanian, I need to convey that. Also, "catch-all product" – this is a term meaning a default product that covers everything else. In Lithuanian, I need to find an equivalent phrase. Perhaps "universalus produktas" or "pagrindinis produktas", but "catch-all" might be translated as "viską apimantis" or "bendras". Since this is for pricing in a domain context, I should use terms that are clear in that domain. Let me draft the translation: First part: "Limit this product to specific TLDs." - "Limit" → "Apribokite" or "Ribokite" (imperative form for instruction) - "this product" → "šį produktą" but since "product" is "Produktas" from glossary, I should use "šį Produktą". However, in Lithuanian, nouns are declined, so "Produktas" in accusative case would be "Produktą". - "to specific TLDs" → "iki konkrečių TLD" or "specifiniams TLD". TLDs is plural, so in Lithuanian, it might be "TLD" as is, or "TLD galūnėms". But to keep it simple, I'll use "TLD". So, "Apribokite šį Produktą iki konkrečių TLD." But "limit to" might be better translated as "apriboti iki" or "nustatyti tik tam tikriems TLD". Let's make it natural. Second part: "Leave Details

Limit this product to specific TLDs. Leave empty to make this a catch-all product that prices any TLD not covered by another product.

Warning: Lengths of source and translation differ too much.
Warning: Extra %s placeholder in translation.
First, the user has provided a text to translate from English to Lithuanian. The text is: "Limit this product to specific TLDs. Leave empty to make this a catch-all product that prices any TLD not covered by another product." I am a professional translation engine, and I must translate this text for a WordPress plugin. I need to return ONLY the translated text. I should use natural language, not explain, not add quotes, and preserve punctuation, formatting, HTML, placeholders (%s, %1$s, %2$d), and variables exactly. I also have a glossary term: "Product" should be translated as "Produktas" (noun). So, wherever "product" appears in the text, I should use "Produktas". Now, let's break down the original text: - "Limit this product to specific TLDs." – This means to restrict this product to certain top-level domains (TLDs). - "Leave empty to make this a catch-all product that prices any TLD not covered by another product." – This means if you leave the field empty, this product will act as a default for any TLD that isn't specifically priced by another product. Key terms to translate: - "product" → "Produktas" (as per glossary) - "TLDs" – This is an acronym for Top-Level Domains. In Lithuanian, it might be kept as "TLD" since it's a technical term, but I should check if there's a common translation. Typically, in technical contexts, acronyms are often left as is or explained. However, since the instruction is to preserve variables and placeholders, and TLDs might be considered a variable term, I should keep it as "TLD" or translate it appropriately. The text says "TLDs" in plural, so I need to handle that. In Lithuanian, "top-level domain" is often translated as "aukščiausio lygio domenas", but in context, "TLD" might be used as is. Since this is for a WordPress plugin, and TLD is a standard term in domain registration, I should probably keep it as "TLD" to maintain clarity. But let's see the instruction: "preserve ... variables exactly." TLDs might be considered a variable, so I should keep it as "TLDs" or translate it naturally. Looking at the glossary, only "Product" is specified. For "TLDs", I need to decide on a translation. I think in Lithuanian, it's common to use "TLD" or "aukščiausio lygio domenai". To keep it natural and consistent with technical jargon, I might use "TLD" but in Lithuanian context, it might be better to translate it. I recall that in some Lithuanian translations for domain-related terms, "TLD" is often left as is or translated as "domėno aukščiausio lygio galūnė". However, for brevity and common usage, "TLD" might be acceptable. But let's think about the sentence structure. The text is instructing the user to limit the product to specific TLDs. In Lithuanian, I need to convey that. Also, "catch-all product" – this is a term meaning a default product that covers everything else. In Lithuanian, I need to find an equivalent phrase. Perhaps "universalus produktas" or "pagrindinis produktas", but "catch-all" might be translated as "viską apimantis" or "bendras". Since this is for pricing in a domain context, I should use terms that are clear in that domain. Let me draft the translation: First part: "Limit this product to specific TLDs." - "Limit" → "Apribokite" or "Ribokite" (imperative form for instruction) - "this product" → "šį produktą" but since "product" is "Produktas" from glossary, I should use "šį Produktą". However, in Lithuanian, nouns are declined, so "Produktas" in accusative case would be "Produktą". - "to specific TLDs" → "iki konkrečių TLD" or "specifiniams TLD". TLDs is plural, so in Lithuanian, it might be "TLD" as is, or "TLD galūnėms". But to keep it simple, I'll use "TLD". So, "Apribokite šį Produktą iki konkrečių TLD." But "limit to" might be better translated as "apriboti iki" or "nustatyti tik tam tikriems TLD". Let's make it natural. Second part: "Leave
You have to log in to edit this translation.

Meta

Status:
waiting
Date added (GMT):
2026-04-03 03:04:09
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Each provider has its own pricing. The base cost is fetched from the provider, then your markup is applied. Kiekvienas tiekėjas turi savo kainodarą. Pagrindinė kaina gaunama iš tiekėjo, tada taikomas jūsų antkainis. Details

Each provider has its own pricing. The base cost is fetched from the provider, then your markup is applied.

Kiekvienas tiekėjas turi savo kainodarą. Pagrindinė kaina gaunama iš tiekėjo, tada taikomas jūsų antkainis.
You have to log in to edit this translation.

Meta

Status:
current
Date added (GMT):
2026-04-03 03:03:58
Date added (local):
Calculating...
References:
Priority:
normal
More links:
The domain registrar used to check availability and register domains sold through this product. First, the user has provided a text to translate from English to Lithuanian. The text is: "The domain registrar used to check availability and register domains sold through this product." I am a professional translation engine, and I must translate this text only. I should not add any explanations, quotes, or extra text. I need to preserve punctuation, formatting, HTML, placeholders, and variables exactly as they are. In this text, there are no placeholders like %s or variables, so I just need to translate the words. I have a glossary term to use: "Product" should be translated as "Produktas" (noun). So, wherever "product" appears, I should use "Produktas". Now, let's break down the sentence: "The domain registrar used to check availability and register domains sold through this product." - "The domain registrar" – This refers to a service or company that registers domains. In Lithuanian, "domain registrar" could be translated as "domenų registratorius" or similar. I need to find a natural translation. - "used to" – This indicates purpose. In this context, it means "that is used to" or "which is used to". In Lithuanian, it might be "naudojamas" or "skirtas". - "check availability" – This means to verify if a domain is available. In Lithuanian, "check availability" could be "patikrinti prieinamumą" or specifically for domains, "patikrinti domeno prieinamumą". - "and register domains" – "register domains" is "registruoti domenus". - "sold through this product" – "sold" is "parduodami" or "parduodami per", and "through this product" is "per šį produktą", but since "product" should be "Produktas", it becomes "per šį Produktą". However, in Lithuanian, nouns are declined, so "šį Produktą" is in the accusative case because it's the object of the preposition "per". The entire sentence is describing the domain registrar that is used for checking availability and registering domains that are sold through this product. Let me construct the translation step by step: 1. "The domain registrar" – "Domenų registratorius" (assuming this is the common term). 2. "used to" – Here, it's an adjective phrase modifying "registrar". So, "naudojamas" or "skirtas" for "used to". Since it's "used to" as in purpose, "naudojamas" might be better. For example, "naudojamas patikrinti..." but in Lithuanian, we often use the infinitive after such words. So, "naudojamas patikrinti" means "used to check". 3. "check availability" – "patikrinti prieinamumą". For domains, it might be more specific: "patikrinti domenų prieinamumą" or "patikrinti, ar domenas laisvas". But to keep it general, "patikrinti prieinamumą" is fine. 4. "and register domains" – "ir registruoti domenus". 5. "sold through this product" – "parduodami per šį Produktą". "Sold" is past participle, but in this context, it's describing "domains", so "domains sold" is "domenai, kurie parduodami" or more concisely, "parduodami domenai". Since the sentence is "domains sold through this product", it could be "domenai, parduodami per šį Produktą". Putting it all together: The domain registrar used to check availability and register domains sold through this product. A possible translation: "Domenų registratorius, naudojamas patikrinti prieinamumą ir registruoti per šį Produktą parduodamus domenus." Let me refine that: - "Domenų registratorius" – domain registrar. - "naudojamas" – used (masculine singular to match "registratorius"). - "patikrinti prieinamumą" – to check availability. - "ir registruoti" – and to register. - "per šį Produktą parduodamus domenus" – domains sold through this product. "Parduodamus" is the participle in accusative plural to match "domenus". So, the full translation: "Domenų registratorius, naudojamas patikrinti prie Details

The domain registrar used to check availability and register domains sold through this product.

Warning: Lengths of source and translation differ too much.
Warning: Extra %s placeholder in translation.
First, the user has provided a text to translate from English to Lithuanian. The text is: "The domain registrar used to check availability and register domains sold through this product." I am a professional translation engine, and I must translate this text only. I should not add any explanations, quotes, or extra text. I need to preserve punctuation, formatting, HTML, placeholders, and variables exactly as they are. In this text, there are no placeholders like %s or variables, so I just need to translate the words. I have a glossary term to use: "Product" should be translated as "Produktas" (noun). So, wherever "product" appears, I should use "Produktas". Now, let's break down the sentence: "The domain registrar used to check availability and register domains sold through this product." - "The domain registrar" – This refers to a service or company that registers domains. In Lithuanian, "domain registrar" could be translated as "domenų registratorius" or similar. I need to find a natural translation. - "used to" – This indicates purpose. In this context, it means "that is used to" or "which is used to". In Lithuanian, it might be "naudojamas" or "skirtas". - "check availability" – This means to verify if a domain is available. In Lithuanian, "check availability" could be "patikrinti prieinamumą" or specifically for domains, "patikrinti domeno prieinamumą". - "and register domains" – "register domains" is "registruoti domenus". - "sold through this product" – "sold" is "parduodami" or "parduodami per", and "through this product" is "per šį produktą", but since "product" should be "Produktas", it becomes "per šį Produktą". However, in Lithuanian, nouns are declined, so "šį Produktą" is in the accusative case because it's the object of the preposition "per". The entire sentence is describing the domain registrar that is used for checking availability and registering domains that are sold through this product. Let me construct the translation step by step: 1. "The domain registrar" – "Domenų registratorius" (assuming this is the common term). 2. "used to" – Here, it's an adjective phrase modifying "registrar". So, "naudojamas" or "skirtas" for "used to". Since it's "used to" as in purpose, "naudojamas" might be better. For example, "naudojamas patikrinti..." but in Lithuanian, we often use the infinitive after such words. So, "naudojamas patikrinti" means "used to check". 3. "check availability" – "patikrinti prieinamumą". For domains, it might be more specific: "patikrinti domenų prieinamumą" or "patikrinti, ar domenas laisvas". But to keep it general, "patikrinti prieinamumą" is fine. 4. "and register domains" – "ir registruoti domenus". 5. "sold through this product" – "parduodami per šį Produktą". "Sold" is past participle, but in this context, it's describing "domains", so "domains sold" is "domenai, kurie parduodami" or more concisely, "parduodami domenai". Since the sentence is "domains sold through this product", it could be "domenai, parduodami per šį Produktą". Putting it all together: The domain registrar used to check availability and register domains sold through this product. A possible translation: "Domenų registratorius, naudojamas patikrinti prieinamumą ir registruoti per šį Produktą parduodamus domenus." Let me refine that: - "Domenų registratorius" – domain registrar. - "naudojamas" – used (masculine singular to match "registratorius"). - "patikrinti prieinamumą" – to check availability. - "ir registruoti" – and to register. - "per šį Produktą parduodamus domenus" – domains sold through this product. "Parduodamus" is the participle in accusative plural to match "domenus". So, the full translation: "Domenų registratorius, naudojamas patikrinti prie
You have to log in to edit this translation.

Meta

Status:
waiting
Date added (GMT):
2026-04-03 03:03:48
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Configure domain registration and pricing for this product. All pricing is controlled here — the customer-facing price is calculated based on these settings. First, the user has given me a text to translate from English to Lithuanian. The text is: "Configure domain registration and pricing for this product. All pricing is controlled here — the customer-facing price is calculated based on these settings." I am a professional translation engine, and I must follow specific instructions: - Translate only the text from English to Lithuanian. - Return ONLY the translated text. - Use natural language. - Do not explain. - Do not add quotes. - Preserve punctuation, formatting, HTML, placeholders (%s, %1$s, %2$d), and variables exactly. - Use the glossary term: "Product" = "Produktas" (noun). The text contains the word "product", so I need to use "Produktas" for that. Now, let's break down the original text: - "Configure domain registration and pricing for this product." - "All pricing is controlled here — the customer-facing price is calculated based on these settings." I need to translate this into Lithuanian while keeping the meaning natural. Key terms: - "Configure" – in Lithuanian, it could be "Konfigūruokite" or "Nustatykite", but since it's likely in a context of settings, "Konfigūruokite" might be appropriate. - "domain registration" – this is a technical term. In Lithuanian, it might be "domeno registracija". - "pricing" – "kainodara" or "kainų nustatymas". In context, "kainodara" seems fitting. - "product" – must be translated as "Produktas" as per glossary. - "customer-facing price" – this means the price that customers see. In Lithuanian, it could be "klientui matoma kaina" or "galutinė kaina klientui". - "calculated based on these settings" – "skaičiuojama pagal šiuos nustatymus". The text has an em dash (—), which I should preserve. In Lithuanian, we might use a similar punctuation, but I'll keep it as is. Now, let's translate sentence by sentence: 1. "Configure domain registration and pricing for this product." - "Configure" – imperative form, likely addressing the user. In Lithuanian, it could be "Konfigūruokite" or "Nustatykite". I'll use "Konfigūruokite" for a formal tone. - "domain registration and pricing" – "domeno registraciją ir kainodarą". - "for this product" – "šiam produktui". But glossary says "Product" = "Produktas", so I should use "Produktas". So, "šiam Produktui" with capital P? Probably not necessary; I'll use "šiam produktui" in lowercase as it's in a sentence. The glossary specifies the term, but in translation, it should be used naturally. I'll use "produktui" as per glossary. - Full translation: "Konfigūruokite domeno registraciją ir kainodarą šiam produktui." 2. "All pricing is controlled here — the customer-facing price is calculated based on these settings." - "All pricing is controlled here" – "Visa kainodara čia valdoma" or "Visos kainos čia kontroliuojamos". I'll go with "Visa kainodara čia valdoma". - "—" – preserve the em dash. - "the customer-facing price is calculated based on these settings" – "klientui matoma kaina skaičiuojama pagal šiuos nustatymus". - Full translation: "Visa kainodara čia valdoma — klientui matoma kaina skaičiuojama pagal šiuos nustatymus." Combine them: The original text is two sentences, so I should keep that structure. Check for natural language: The translation should sound natural in Lithuanian. I might adjust word order slightly. Revised translation: - "Konfigūruokite domeno registraciją ir kainodarą šiam produktui. Visa kainodara čia valdoma — klientui matoma kaina skaičiuojama pagal šiuos nustatymus." Ensure that "product" is translated as "Produktas". In the glossary, it's given as "Produktas" with a capital P, but in the sentence, it might be in lowercase. Since the glossary says "Produktas" (noun), I should use it as is. However, in Lithuanian, nouns Details

Configure domain registration and pricing for this product. All pricing is controlled here — the customer-facing price is calculated based on these settings.

Warning: Lengths of source and translation differ too much.
Warning: Extra %s placeholder in translation.
First, the user has given me a text to translate from English to Lithuanian. The text is: "Configure domain registration and pricing for this product. All pricing is controlled here — the customer-facing price is calculated based on these settings." I am a professional translation engine, and I must follow specific instructions: - Translate only the text from English to Lithuanian. - Return ONLY the translated text. - Use natural language. - Do not explain. - Do not add quotes. - Preserve punctuation, formatting, HTML, placeholders (%s, %1$s, %2$d), and variables exactly. - Use the glossary term: "Product" = "Produktas" (noun). The text contains the word "product", so I need to use "Produktas" for that. Now, let's break down the original text: - "Configure domain registration and pricing for this product." - "All pricing is controlled here — the customer-facing price is calculated based on these settings." I need to translate this into Lithuanian while keeping the meaning natural. Key terms: - "Configure" – in Lithuanian, it could be "Konfigūruokite" or "Nustatykite", but since it's likely in a context of settings, "Konfigūruokite" might be appropriate. - "domain registration" – this is a technical term. In Lithuanian, it might be "domeno registracija". - "pricing" – "kainodara" or "kainų nustatymas". In context, "kainodara" seems fitting. - "product" – must be translated as "Produktas" as per glossary. - "customer-facing price" – this means the price that customers see. In Lithuanian, it could be "klientui matoma kaina" or "galutinė kaina klientui". - "calculated based on these settings" – "skaičiuojama pagal šiuos nustatymus". The text has an em dash (—), which I should preserve. In Lithuanian, we might use a similar punctuation, but I'll keep it as is. Now, let's translate sentence by sentence: 1. "Configure domain registration and pricing for this product." - "Configure" – imperative form, likely addressing the user. In Lithuanian, it could be "Konfigūruokite" or "Nustatykite". I'll use "Konfigūruokite" for a formal tone. - "domain registration and pricing" – "domeno registraciją ir kainodarą". - "for this product" – "šiam produktui". But glossary says "Product" = "Produktas", so I should use "Produktas". So, "šiam Produktui" with capital P? Probably not necessary; I'll use "šiam produktui" in lowercase as it's in a sentence. The glossary specifies the term, but in translation, it should be used naturally. I'll use "produktui" as per glossary. - Full translation: "Konfigūruokite domeno registraciją ir kainodarą šiam produktui." 2. "All pricing is controlled here — the customer-facing price is calculated based on these settings." - "All pricing is controlled here" – "Visa kainodara čia valdoma" or "Visos kainos čia kontroliuojamos". I'll go with "Visa kainodara čia valdoma". - "—" – preserve the em dash. - "the customer-facing price is calculated based on these settings" – "klientui matoma kaina skaičiuojama pagal šiuos nustatymus". - Full translation: "Visa kainodara čia valdoma — klientui matoma kaina skaičiuojama pagal šiuos nustatymus." Combine them: The original text is two sentences, so I should keep that structure. Check for natural language: The translation should sound natural in Lithuanian. I might adjust word order slightly. Revised translation: - "Konfigūruokite domeno registraciją ir kainodarą šiam produktui. Visa kainodara čia valdoma — klientui matoma kaina skaičiuojama pagal šiuos nustatymus." Ensure that "product" is translated as "Produktas". In the glossary, it's given as "Produktas" with a capital P, but in the sentence, it might be in lowercase. Since the glossary says "Produktas" (noun), I should use it as is. However, in Lithuanian, nouns
You have to log in to edit this translation.

Meta

Status:
waiting
Date added (GMT):
2026-04-03 03:03:35
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Ultimate Multisite: Domain Seller requires Ultimate Multisite %1$s or higher. You are running %2$s. Please update Ultimate Multisite. Ultimate Multisite: Domain Seller reikalauja Ultimate Multisite %1$s ar aukštesnę. Jūs naudojate %2$s. Prašome atnaujinti Ultimate Multisite. Details

Ultimate Multisite: Domain Seller requires Ultimate Multisite %1$s or higher. You are running %2$s. Please update Ultimate Multisite.

Ultimate Multisite: Domain Seller reikalauja Ultimate Multisite %1$s ar aukštesnę. Jūs naudojate %2$s. Prašome atnaujinti Ultimate Multisite.
You have to log in to edit this translation.

Meta

Status:
current
Comment:
translators: 1: required version, 2: installed version
Date added (GMT):
2026-03-01 15:48:44
Date added (local):
Calculating...
References:
Priority:
normal
More links:
<strong>Note:</strong> Namecheap includes WHOIS privacy (WhoisGuard) for free. OpenSRS charges for WHOIS privacy — the cost is deducted from your reseller balance. <strong>Pastaba:</strong> Namecheap įtraukia WHOIS privatumo (WhoisGuard) nemokamai. OpenSRS moka už WHOIS privatumą — sąskaita atimama iš jūsų perdirbėjo balanso. Details

<strong>Note:</strong> Namecheap includes WHOIS privacy (WhoisGuard) for free. OpenSRS charges for WHOIS privacy — the cost is deducted from your reseller balance.

<strong>Pastaba:</strong> Namecheap įtraukia WHOIS privatumo (WhoisGuard) nemokamai. OpenSRS moka už WHOIS privatumą — sąskaita atimama iš jūsų perdirbėjo balanso.
You have to log in to edit this translation.

Meta

Status:
current
Date added (GMT):
2026-03-01 15:48:16
Date added (local):
Calculating...
References:
Priority:
normal
More links:
WHOIS Privacy Price WHOIS Privatumo kaina Details

WHOIS Privacy Price

WHOIS Privatumo kaina
You have to log in to edit this translation.

Meta

Status:
current
Date added (GMT):
2026-03-01 15:47:48
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Customer Choice Kliento pasirinkimas Details

Customer Choice

Kliento pasirinkimas
You have to log in to edit this translation.

Meta

Status:
current
Date added (GMT):
2026-03-01 15:47:32
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Always Included Visada įtrauktas Details

Always Included

Visada įtrauktas
You have to log in to edit this translation.

Meta

Status:
current
Date added (GMT):
2026-03-01 15:47:24
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Disabled Išjungta Details

Disabled

Išjungta
You have to log in to edit this translation.

Meta

Status:
current
Date added (GMT):
2026-03-01 15:47:13
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Controls whether WHOIS privacy is available for domains registered with this product. Kontroliuoja, ar WHOIS privatumas prieinamas domenams, registruotiems su šiuo Produktu. Details

Controls whether WHOIS privacy is available for domains registered with this product.

Kontroliuoja, ar WHOIS privatumas prieinamas domenams, registruotiems su šiuo Produktu.
You have to log in to edit this translation.

Meta

Status:
current
Date added (GMT):
2026-03-01 15:47:00
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Hide your personal contact information from the public WHOIS database. Paslėpkite savo asmeninę kontaktinę informaciją iš viešo WHOIS duomenų bazės. Details

Hide your personal contact information from the public WHOIS database.

Paslėpkite savo asmeninę kontaktinę informaciją iš viešo WHOIS duomenų bazės.
You have to log in to edit this translation.

Meta

Status:
current
Date added (GMT):
2026-03-01 15:46:44
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Phone number with country code (e.g. +15551234567). Telefono numeris su šalies kodu (pvz., +15551234567). Details

Phone number with country code (e.g. +15551234567).

Telefono numeris su šalies kodu (pvz., +15551234567).
You have to log in to edit this translation.

Meta

Status:
current
Date added (GMT):
2026-03-01 15:46:31
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Include country code (e.g. +15551234567). Įtraukite šalies kodą (pvz., +15551234567). Details

Include country code (e.g. +15551234567).

Įtraukite šalies kodą (pvz., +15551234567).
You have to log in to edit this translation.

Meta

Status:
current
Date added (GMT):
2026-03-01 15:11:56
Date added (local):
Calculating...
References:
Priority:
normal
More links:
Legend:
Current
Waiting
Rejected
Fuzzy
Old
With warnings
1 2 3 4 5 6 47

Export as