Domains - Bulk Edit - check status

Modified on Wed, 12 Jul, 2017 at 9:16 AM

Answer ID 131

I entered a bulk edit request, but the domains did not update. The bulk edit status still says processing, how long does it take?

A Bulk Edit request is submitted when you complete the process, however, it will go into a queue and be processed in the order received.  In most cases, your request will be finished within four hours.  You will receive an email notification which will show the number of domains on which the changes were applied successfully and any that may have failed.  

If there are larger requests ahead of you (for example, someone with 75,000 domains making a DNS change) it could take up to 48 hours to complete. 


To check the status of your bulk edit:

  • Login to your account
  • Go to "My Account - My Reports" in the top menu
  • Click on "Bulk Edit Report"

This screen will let you know if your request is still processing or has completed.  You will also receive an email when the edit is complete, advising you of any errors that may have occurred during the edit update.

If you are turning off the auto-renew for domains, and the edit has not completed, domains may still renew if their date is less than 30 days prior to expiration.  You may want to turn off the auto-renew specifically for those domains to avoid unintentional renewals.


Note:  When changing the Registrant Contact information for domains in bulk, the change will need to be verified via a verification email sent to the new registrant email address. When changing the contact information for multiple domains at one time, we must send a verification email for each. So, if you updated 3 domains, you would receive 3 contact verification emails. However, if identical contact information is supplied for the domains, verifying a single domain will verify all domains with the same contact details.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article