Article image
Managing International ccTLDs: Rules, Residency Requirements, and Expiration Risk
Expanding a client's brand into international markets is a major milestone for any web agency. The typical playbook is familiar: localize the site content, build out regional SEO, and register the matching country domains. You lock down the .com, then move to secure the .co.uk, .com.au, .de, and .co.jp.
Most agencies assume domains all behave the same way — you buy it, point the DNS, and get roughly 30 days after expiration to sort out a late renewal. That assumption, built around the familiar .com lifecycle, is one of the more common causes of avoidable client-facing outages and lost domains.
Country-code top-level domains (ccTLDs) aren't governed by one universal rulebook. Each one is run by a national or regional registry with its own eligibility rules, its own expiration timeline, and its own tolerance for mistakes. Some registries give you a comfortable 90-day runway to fix a missed renewal; others take the site down the moment the clock hits zero and give you no second chance at all. Some require government-verified proof of local presence just to register a name.
If your agency manages international domains, you're not just managing DNS records — you're managing a patchwork of national policy. Here's what's actually true about residency requirements, renewal deadlines, and technical quirks across the major ccTLDs, and where a centralized tracking tool like InstaRenewal fits into keeping it all straight.
- The Core Misconception: ICANN vs. Sovereign Registries Generic top-level domains (gTLDs) like .com, .org, and .net operate under ICANN's contractual framework. ICANN's Expired Registration Recovery Policy sets a consistent baseline: registrars must offer a 30-day Auto-Renew Grace Period at the standard renewal price, followed (if the domain isn't renewed) by a roughly 30-day Redemption Grace Period at a much higher recovery fee, and finally a short Pending Delete window of about five days before the name is released to the public.
Country-code domains answer to none of that. Each ccTLD is delegated to a national registry that sets its own rules under its own legal framework:
Australia (.au) — auDA
Germany (.de) — DENIC
Canada (.ca) — CIRA
The UK (.uk) — Nominet
The Netherlands (.nl) — SIDN
Brazil (.com.br) — Registro.br
None of these bodies are bound by ICANN's grace-period standards, and — as the examples below show — some are considerably more forgiving than the .com baseline, while others are far less. Tracking a global portfolio against a single mental model built around .com is how agencies lose assets they didn't realize were at risk.
- Foreign Domain Residency Requirements The first roadblock agencies hit when registering international assets is a local-presence requirement. Many countries restrict their ccTLDs to citizens or locally established businesses to curb squatting and abuse.
Tier 1: Highly Restricted Registries
Australia (.com.au / .au) — auDA requires a verified Australian connection: an Australian Business Number (ABN), Australian Company Number (ACN), or a matching registered Australian trademark. The registrant must continue meeting eligibility criteria for the entire life of the licence, not just at signup — auDA can cancel a licence mid-term if that connection lapses.
Japan (.jp / .co.jp) — A general-use .jp domain requires the registrant (individual or organization) to have a permanent mailing address in Japan. .co.jp is stricter still: it's limited to one domain per corporation legally registered under Japanese law, and every detail — company name, representative, incorporation date — is published in the public JPRS WHOIS with no privacy option. A foreign company can qualify only by first establishing a Japanese-registered entity, including as a "Gaikoku Kaisha" (registered foreign company), and providing incorporation documents to prove it.
Canada (.ca) — CIRA's Canadian Presence Requirement (CPR) requires every registrant to select from a defined list of categories (Canadian citizen, permanent resident, Canadian corporation, and so on) to demonstrate a genuine connection to Canada. CIRA also runs periodic Registrant Information Validation (RIV) audits, requesting supporting documents like a passport or certificate of incorporation. A registrant who can't produce it typically has around two months from the start of the audit before the domain is deleted.
China (.cn / .com.cn / .中国) — Every registration goes through CNNIC's Real-Name Verification (RNV): individuals submit a passport or ID card, organizations submit a business license or certificate of incorporation. Foreign registrants are eligible — RNV is a documentation requirement, not a nationality restriction — but a domain that isn't verified within the registrar's submission window (commonly around ten days) has its DNS resolution suspended, and unverified registrations can be revoked entirely.
Tier 2: Regional Registries
European Union (.eu) — Eligibility is restricted to EU citizens (regardless of where they live), residents of an EU/EEA member state, or organizations legally established in the EU. This is the one agencies most often get wrong today: since Brexit, UK-based organizations without an EU presence, and UK residents who aren't EU citizens, are no longer eligible to hold .eu domains at all. EURid suspended non-compliant UK-held .eu domains in 2021, and any that weren't brought into compliance were eventually released for public re-registration. Any agency still carrying a .eu asset registered under a UK-only entity should treat it as a live compliance risk, not a settled asset.
France (.fr) — Requires presence within the EU/EEA, Switzerland, or a small handful of other approved countries — the same basic geographic logic as .eu, enforced by AFNIC.
Tier 3: Open ccTLDs
Some registries have fully commercialized their namespace with no residency restriction at all: Colombia (.co), Montenegro (.me), Tuvalu (.tv), and India (.in) are commonly used this way. Chile's .cl has also moved in this direction — NIC Chile no longer requires a local representative for foreign registrants, though some registrars still ask for a Chilean tax ID (RUT) as a matter of their own process, so it's worth confirming with the specific registrar rather than assuming.
The Agency Solution: Trustee Services
For a US-based client that wants a .co.jp presence without a Tokyo office, agencies typically use a Trustee (local presence) service. A specialized registrar acts as the nominal, legally liable registrant within the target country for an annual fee, while the agency keeps technical and administrative control of the DNS. Tracking which domains rely on a trustee arrangement — and which client is actually paying for it — is its own ongoing bookkeeping problem for agencies running a large international portfolio.
- The Expiration Minefield: Renewal Rules That Don't Match .com This is where agencies get burned. There is no standardized expiration grace period across ccTLDs — some registries are notably more forgiving than .com, and some are notably less.
Registries that give you less room than .com
Germany (.de) — DENIC gives no grace period at all. The moment a .de domain expires without renewal, it drops straight into a 30-day Redemption Grace Period during which only the existing registrant (or someone they designate) can reclaim it. After that, it's released to the public on a first-come, first-served basis. In practice, this means .de domains must be renewed before the expiration date — there's no post-expiry cushion the way there is with .com.
Spain (.es), Switzerland (.ch), France (.fr), Singapore (.sg) — Registrars typically require these to be renewed at least 12 days before the expiration date; if that window is missed, the domain drops straight into its Redemption Grace Period regardless of how many days were technically left. .es compounds this further: its RGP lasts only about 10 days, has no separate "pending delete" stage, and the name is released to the public the moment the RGP ends.
The Netherlands (.nl) — SIDN doesn't delete an expired domain immediately, but it doesn't offer a .com-style pre-expiry grace period either. A lapsed .nl domain enters a 40-day quarantine, reactivable by the original registrant at a premium price, before it's released.
Registries that give you more room than .com — despite their reputation
United Kingdom (.uk) — This one surprises a lot of agencies. Despite .uk's reputation for strictness, Nominet actually offers a longer recovery window than .com: a standard 30-day grace period, followed by up to another 60 days of suspension during which the domain is still recoverable — a roughly 90-day total runway — before it's finally dropped and released. Nominet also doesn't charge the kind of steep "redemption fee" gTLD registries do; renewal within that window is generally at the standard rate.
Australia (.com.au / .au) — auDA's own policy gives a 30-calendar-day grace period after expiry. The domain and any connected email stop working during that window, but it can still be renewed at the standard price. After 30 days, it's removed from the registry and released first-come, first-served. One added quirk: you cannot renew a .au domain more than 90 days ahead of its expiration date, so agencies that try to renew too early will simply be told to come back later.
Canada (.ca) — CIRA auto-renews an expiring .ca domain and gives the registrar up to a 45-day Auto-Renew Grace Period to either confirm payment or request deletion (whether the site stays live during this window depends on the individual registrar's own policy). If it's deleted, a further 30-day Redemption Grace Period follows before the domain lands on CIRA's "To Be Released" list.
Brazil (.com.br) — Registro.br freezes ("congelado") an unpaid domain immediately on its expiration date — the site, database, and any connected email stop working right away, with no pre-expiry cushion. But the registrant then has a substantial window, commonly cited at around 90 days, to pay and unfreeze it before the name moves into Registro.br's public release process. So the outage happens fast, but the actual loss of the domain doesn't — a distinction that matters when triaging a client emergency.
Small or thinly documented registries
Extremely small ccTLDs — Suriname's .sr is a good example — are frequently resold through third-party registration services rather than administered directly by the sponsoring national body, and published information about grace and redemption periods for these registries is inconsistent from one reseller to the next. .sr itself carries no residency restriction, but agencies shouldn't assume a specific number of grace days applies without confirming directly with the registrar of record. Treat any thinly documented ccTLD as a "renew well before expiry, don't test the grace period" asset by default.
Uruguay (.uy / .com.uy) is a related case worth flagging for a different reason: it requires an in-country presence (most registrars offer a local-address service for non-resident registrants), and — unlike most ccTLDs — a .uy domain generally cannot be moved between registrars through a standard transfer. Changing providers means deleting and re-registering the name, which is a materially different (and riskier) operation than a normal transfer.
Grace Period Comparison at a Glance
ccTLD Registry Deadline to Act Post-Expiry Window What Happens After
.com (gTLD baseline) Verisign / ICANN Expiration date 30-day grace + 30-day redemption ~5-day pending delete, then released
.com.au / .au auDA Expiration date 30-day grace period Released FCFS; can't renew >90 days early
.de DENIC Before expiration None — straight to 30-day RGP Released after RGP
.nl SIDN Expiration date 40-day quarantine Released after quarantine
.uk Nominet Expiration date 30-day grace + 60-day suspension (~90 days total) Released after ~90 days, no redemption fee
.ca CIRA Expiration date 45-day auto-renew grace + 30-day redemption Added to "To Be Released" list
.com.br Registro.br Expiration date Frozen immediately; ~90 days to pay Enters public release process
.es / .ch / .fr / .sg Various 12 days before expiration Short RGP (e.g., ~10 days for .es), no pending-delete stage Released immediately after RGP
- Technical Quirks: DNS Checks and Transfer Behavior
Pre-delegation DNS checks (
.de,.fr) — Updating nameservers on a .com is simple: the registrar passes the change to the registry, and propagation begins. DENIC and AFNIC don't work that way. Both run an automated pre-delegation check (AFNIC's tool is called Zonemaster) that confirms the proposed nameservers are live, correctly configured, and already answering authoritatively for the domain before the change is accepted. If the new hosting environment isn't fully configured and responding at the moment the change is submitted, the registry will reject the update outright. Agencies need the destination DNS live and correct before requesting the change — not after, as is normal practice with gTLDs.
Transfer behavior varies widely — Under ICANN policy, transferring a gTLD to a new registrar reliably adds a year to the registration term. ccTLDs don't follow one consistent rule here: some registries extend the term on transfer, some don't, and a few — .uy is the clearest example — don't support a standard registrar-to-registrar transfer at all, requiring the domain to be deleted and re-registered instead. Never promise a client a routine, risk-free transfer on an unfamiliar ccTLD without checking that specific registry's policy first.
- Building a More Reliable SOP Given how inconsistent these rules are, tracking a global portfolio in a generic spreadsheet built around .com assumptions is a losing strategy. At its core, this is an asset-visibility problem: agencies need one place that records which domain belongs to which client, which registrar it sits with, who's actually responsible for the renewal, and when it's due — with room to note registry-specific quirks (a .de domain's hard no-grace-period rule, a .uy domain's local-presence and no-transfer restrictions) so that knowledge doesn't live only in one project manager's head.
This is the kind of centralized tracking a tool like InstaRenewal is built for: pulling every domain an agency manages — along with the associated SSL certificates, hosting accounts, and plugin licenses — into a single dashboard with ownership and renewal dates visible at a glance, instead of requiring someone to check into twenty different registrar accounts on a schedule. It won't interpret a specific country's residency law or DENIC's redemption process for you — that's still a job for the registry's own documentation and whoever owns the account — but it removes the far more common failure mode behind most of these horror stories: a renewal date that nobody was actually watching.
- Conclusion As client bases go global, the agencies that get hurt aren't the ones without international domains — they're the ones who assume every domain behaves like .com. Understanding where residency requirements actually bite (Australia, Japan, Canada, China, and now .eu for UK-only entities), knowing which registries are stricter than .com and which are actually more forgiving, and getting DNS and transfer mechanics right for registries like .de and .fr are all table stakes for agencies operating internationally. Centralizing that tracking — rather than relying on a spreadsheet built for a simpler, .com-only world — is what keeps a missed renewal from becoming a client crisis.
Sources
ICANN — Expired Registration Recovery Policy / FAQs for Registrants: Domain Name Renewals and Expiration
Namecheap Knowledge Base — "TLDs' Grace Periods"
DENIC eG — "Redemption Grace Period" (official policy page)
SIDN — General Terms and Conditions for Registrants; Technical Requirements for .nl Domain Names
auDA — "How to Renew Your .au Domain Name"; .au Domain Administration Rules: Licensing; Synergy Wholesale ".au Domain Name Life Cycle"
CIRA — "The Domain Name Life Cycle"; "Your Domain Name Expired. What Now?"; Canadian Presence Requirements for Registrants; General Registration Rules
Nominet — Domain Lifecycle (Registrar Resources); Data Quality Lock policy; third-party registrar summaries (Mix.co.uk, 20i, SCAN UK)
Registro.br policy summaries via Locaweb and HostGator Brazil support documentation
Japan Registry Services (JPRS) — ".JP Q&A"; "Guide to JP Domain Name"
CNNIC / GoDaddy / Dynadot / Alibaba Cloud — .CN Real-Name Verification requirements
EURid — Brexit Notice and related legal summaries (CMS Law, Lexology, Womble Bond Dickinson, GoDaddy, 20i)
AFNIC — Zonemaster / pre-delegation check documentation; Afnic FAQ
NIC Chile — Regulations for the Operation of the .CL Top Level Domain; General Terms and Conditions for the Registration of .CL Domain Names
Namebeta, TLD-List, Nominate.com, BB Online, Entorno Digital, Netim — registry factsheets for .sr, .uy, and .com.uy
Top comments (0)