TLD Validation (2–6 Character) Regex for JavaScript
/^[a-zA-Z]{2,6}$/What this pattern does
This page provides a lightweight, single-purpose regular expression for matching tld validation (2–6 character), ported and verified for JavaScript. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your JavaScript project — whether you're validating in an Express middleware, a Next.js API route, or a client-side form.
Javascript Implementation
// TLD Validation (2–6 Character)
// ReDoS-safe | RegexVault — Web & Network > Domain
const tldValidation26CharacterRegex = /^[a-zA-Z]{2,6}$/;
function validateTldValidation26Character(input: string): boolean {
return tldValidation26CharacterRegex.test(input);
}
// Example
console.log(validateTldValidation26Character("com")); // trueTest Cases
Matches (Valid) | Rejects (Invalid) |
|---|---|
com | c |
net | toolongtld |
org | c0m |
io | .com |
co | COM. |
museum | — |
When to use this pattern
This pattern is drawn from the Web & Network > Domain category and carries a ReDoS-safe certification. That matters for JavaScript developers because especially critical in long-running Node.js event loops where a ReDoS vulnerability can block the entire process. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.
Common Pitfalls
TLD validation by regex alone is not authoritative — use the IANA TLD list or a library like publicsuffix-list for production use.
Technical Notes
New gTLDs (e.g., .photography, .construction) can be up to 24 characters. Adjust the upper bound to {2,24} if validating modern TLDs. The IANA TLD list is the authoritative source.
Have a pattern that belongs in the vault?
Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.
Submit a Pattern