Enable or Disable Designated Agent (DA) for the COR Process

The Designated Agent (DA) setting controls whether OpenSRS sends ICANN-required confirmation emails to the prior and new registrants during a Change of Registrant (COR), or whether you, the reseller, consent on their behalf. This article walks you through enabling or disabling DA for your reseller account. For background on what DA is and why it matters, see Designated Agent (DA).

What this setting controls

This is an account-level toggle. When enabled, every COR you submit completes without registrant email confirmation. When disabled, both the prior and new registrant receive confirmation emails and must approve before the change takes effect.

Warning: Before you enable DA, confirm your reseller terms of service authorize you to act as your customers' Designated Agent. By enabling this setting you take on contractual responsibility for confirming both parties consent.

Before you begin

• Master Account permission. Only users with reseller administrator-level access can change this setting.
• Reviewed your terms of service. Your customer agreement should include language authorizing you to act as their Designated Agent.
• Understand the impact. All future CORs on your account will follow the new setting until you change it again.

Step 1: Open the reseller preferences

1. Sign in to the Reseller Control Panel.
2. Navigate to Account Settings > Preferences.
3. Locate the Designated Agent section.

Note: Menu labels can vary slightly between RCP versions. If you cannot find the setting, check under Profile or Reseller Profile.

Step 2: Enable Designated Agent

Enable DA to skip ICANN confirmation emails on future CORs.

1. Toggle Designated Agent to On.
2. Read the on-screen confirmation that explains the responsibilities you are accepting.
3. Click Confirm or Save. The change takes effect immediately.

Step 3: Disable Designated Agent

Disable DA to restore standard ICANN email confirmation on every COR.

1. In the same Designated Agent section, toggle the setting to Off.
2. Click Save.
3. From the next COR onward, OpenSRS will send confirmation emails to both the prior and new registrant.

Step 4: Verify the change

Confirm the setting reflects your choice and inform your team.

1. Refresh the preferences page and confirm the Designated Agent toggle shows the expected state.
2. Notify other staff who manage CORs so they understand whether email confirmations are now expected.
3. For your next COR, monitor the order to confirm it completes (DA on) or that the confirmation emails go out (DA off).

What it affects

• Only gTLD domains. ccTLDs follow registry-specific procedures and are not affected by this setting.
• Only future CORs. Changes already in flight continue under the setting active when the order was submitted.
• The 60-day transfer lock still applies. Material registrant changes lock the domain against inter-registrar transfer for 60 days unless the registrant opts out at the time of change.

Next steps

• Review the DA concept. See Designated Agent (DA) for background and responsibilities.
• Update your customer terms. If you enabled DA, ensure your terms of service authorize you to consent on behalf of registrants.
• Document your COR process. Review the full Change of Registrant (COR) for gTLD domains process and decide internally when your staff initiates CORs.

Questions? Contact OpenSRS Support.