Our Help Center has a fresh new feel.

We've made it easier to browse, search, and get to the information you need. Use the left navigation menu to explore by topic, or search for something specific.

Radix EPP and Platform Behavior

This article describes how the Tucows Registry platform handles EPP operations for Radix TLDs. It highlights expected EPP behavior, domain lifecycle handling, lock statuses, auto-renewals, and glue record rules, and outlines what you should test to ensure your systems remain compatible after the transition.

EPP and Platform Behavior

  • No major EPP changes are expected
  • Tucows Registry uses a clean, RFC-aligned EPP implementation
  • Standards-compliant EPP clients should work with minimal or no changes

Registrars should ensure they:

  • Test all EPP commands in OTE
  • Rely on standard EPP status codes
  • Avoid hardcoding registry-specific error messages

Dual EPP Fee Extension Support

Auto-renewals

Transfer Lock

Please see Change to Transfer Lock

  • clientTransferProhibited: registrar-controlled
  • serverTransferProhibited: registry-controlled (used sparingly)

Glue and host objects

  • Domains with active child hosts cannot be deleted
  • All dependencies must be removed before deletion
  • Clear EPP error messages are returned when dependencies exist

This behavior is consistent with most major registry platforms.