Radix EPP and Platform Behavior

This article describes how the Tucows Registry Services 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 Services 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

• Please see the EPP Fee Extension Guide for details.

Auto-renewals

• Please see the Domain Autorenew Lifecycle Guide for comprehensive details on the domain lifecycle.

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.

Was this article helpful? If not please submit a request here