Monday, September 10, 2012

How to retrieve Domains By Proxy customer number(s) from Go Daddy using Google Chrome

Note: See Escaping GoDaddy and Domains by Proxy by Aaron James Young for a simpler method. My article is more technical and involves more steps.

If you would like, you may skip directly to the instructions.


When I attempted to transfer a domain away from Go Daddy last December, I had trouble retrieving the Domains By Proxy customer number using the Retrieve Customer Number tool at I think it was because the e-mail address on file was disabled the first time I tried using it. I then reactivated the e-mail account, but there were no messages with the customer number. My subsequent attempts to retrieve it also failed.

I was frustrated. But then I discovered the eHow article, How to Remove Domains by Proxy, which gave me hope. It didn't work for me, but it led me in the right direction. The second sentence of Step 1 says, "At the bottom of this page, you will see your Domains by Proxy user name, which is all numbers." I did not see the number the instructions were referring to. But after some investigation I found a way to locate it, which I explain below.



The instructions below describe how to search the DOM for a div with id="privacy-selected-div" and delete or disable the display: none; rule of the div’s style attribute. This will display the section: “Select your Domains By Proxy® account (Private Registration account)”. Your Domains By Proxy customer number(s) should be listed next to one or more radio button labeled “Login:”.


Follow these instructions at your own risk. The steps below involve technical steps such as viewing and updating the Document Object Model (DOM) of a web page you are viewing. Also, I documented these steps several months ago (December 2011) and Go Daddy may have changed things since then. So, it’s possible these steps may now be completely wrong.

The following instructions are for Google Chrome. If you have a different web browser, it may be possible to retrieve your customer number(s) using your browser’s development tools, but the exact instructions will vary and are up to you.

Step-by-step Instructions

  1. Open Google Chrome
  2. Log in to your Go Daddy account
  3. Under My Account click My Renewals
    • You should now be at the Go Daddy My Renewals page
  4. Open Chrome’s Developer Tools window:
    • By right-clicking anywhere on the web page (such as a margin) and selecting Inspect element
    • Or by pressing Ctrl+Shift+I
  5. In the Search Elements box, search for:
    • Make sure Elements is selected at the top of the Developer Tools window.
    • The following element should be located:
      <div id="privacy-selected-div" 
      style="display: none; …">…</div>
    • Click on the located element (e.g. click on the yellow highlighted section)
    • The line should turn blue.
  6. In the right side of the window, locate the “Styles” section.
    • If it is not expanded, click to expand it (the arrow should point down).
    • Place your mouse cursor over the following block under Styles: {
          display: none;
          margin-left: 22px;
    • Click the checkbox that appears to the right of the display: none; rule.
    • The rule should now have a line through it, like display: none; indicating the rule is disabled, and should cause the section to be displayed.
How to display privacy-selected-div using Chrome's Developer Tools
Screenshot showing how to display the privacy-selected-div using Chrome's Developer Tools.
  1. Now, switch back to the Chrome window and tab with the Go Daddy My Renewals web page.
    • You should now see the heading, “Select your Domains By Proxy® account (Private Registration account)” below the table with your domains.
    • Below this, you should see one or more radio buttons with the label “Login:” and a number.
    • The number(s) is/are your Domains By Proxy customer number(s).
Screenshot of the My Renewals page
Screenshot of the Go Daddy My Renewals page showing the Domains By Proxy customer number (highlighted at the lower left).
  1. Log out of your Go Daddy account.
    • Do NOT click Continue on the My Renewals page if you do not wish to renew your domain(s) at this time.


  • Follow these instructions at your own risk.
  • Do NOT click Continue on the My Renewals page if you do not wish to renew your domain(s) at this time. I am not responsible for any charges.
  • Go Daddy may change their site at any time causing these instructions to fail. It worked for me when I drafted this article (December 2011). It may or may not work for you.
  • View source from your browser probably will not work because the relevant section of the page appears to be generated via JavaScript.
  • It is unlikely that I will be able to answer questions you may have. For one reason, I no longer have access to a Go Daddy account.

Other options for DOM/web ninjas

  • Get values from input elements with name="dbpaccts".
    • If you want more info, look at the corresponding label element(s).
  • It might also be possible to obtain your customer number(s) by peeking at JSON or AJAX.

See Also

Monday, April 30, 2012

A rant on time zone code usage

Or, an idea to simplify time zone abbreviations in daily usage

Time zones for North America

Say you’re checking your Twitter account while hanging out at a coffee shop on a hot summer day, and you notice the following update from your favorite musician:

@rockinmusician: Can’t make it to the San Francisco show this weekend? Watch it live online this Saturday at 7 PM PST!

Did you catch that? Does anything about the time look funny to you? Is everything dandy with that PST? Since, you know, standard time is in the summer and daylight saving time is in the winter, right? Or maybe the S stands for summer? Not quite.

I see this error way too often on social media, websites, flyers, etc. Mostly, I’ve held my tongue, but it continually annoys me, so I’m venting here.

Since rockinmusician’s concert is in the summer (Pacific Daylight Time in San Francisco), the actual time should be written 7 PM PDT. Or should it?

Should we even continue to use traditional U.S. time zone codes/abbreviations (i.e. EST/EDT, CST/CDT, MST/MDT, PST/PDT, etc.) when specifying times in day-to-day communication?

Wrong information

Why do we even bother adding the S or D in our time zone codes if we’re going to be wrong about it? I think saying the wrong thing is worse than being too general. And because it’s been communicated incorrectly so often (at least in social media), it has become unreliable. Like the boy who cried “wolf”.

It may even cause clients/fans/etc. to lose a bit of respect when they see the obvious mistake.

Useless information

Furthermore, the vast majority of the time, it adds no meaningful information to specify whether an event happens during standard or daylight saving time, even when it is communicated correctly. In many cases, standard time or daylight saving time are going to be the same between the two parties communicating, even if they are in different time zones. And when it’s not, they will usually be aware of that.

So the middle letter in the time zone code has just become noise.

I think we can simplify a bit.

Who cares?


Who cares if your event is PST or PDT? If I know it’s Pacific Time, then 99.9% of the time I don’t need you to tell me whether it’s standard or daylight saving time. So why bother even adding the S or D? Especially if it’s going to be wrong.

For the rare instances that it really matters, then yes, do use the original codes. But because the codes have been so misused, you may have to add an extra note or something to make sure people take notice.

I remember our old office voicemail menu shared the office hours like “9 AM to 5:30 PM Pacific Daylight Time.” That meant a special update to the voicemail twice each year. Ugh – so pointless. I was glad when it was simplified to “Pacific Time.” The hours listed on the website were similarly simplified, to my delight.

An alternative

For everyday communication, let’s just drop the middle letter and use shorter codes for U.S. times. So Eastern Time would be ET, etc. The original example would become 7 PM PT. Below is a table of my proposed shorter time zone codes.

Time Zone Short Code
Eastern Time Zone ET
Central Time Zone CT
Mountain Time Zone* MT
Pacific Time Zone PT
Alaska Time Zone AKT
Hawaii-Aleutian Time Zone* HAT or HT

The shorter code is slightly simpler, reduces chance for error, and its meaning should still be obvious when used next to a time.

Or, you could always spell it out, like 7 PM Pacific.


Again, I’m not saying original time zone codes should be dropped entirely. They should probably still be used in more formal publications. But if using them, make sure there is a good reason for the added complexity. And make sure it’s correct and verified by an editor (or multiple editors).

Also, some computer programs, etc. must use the full codes. But we’re human, so we can generalize when appropriate.

* Certain parts of the U.S. do not “celebrate” daylight saving time. That is one case where, for example, MST vs. MDT can matter. But people in those areas should already be aware of that. And events originating from those areas (with outside participants) should probably have an additional note making sure others are aware of the difference anyways.

I don’t know if these new codes will cause any confusion when communicating U.S. times internationally, but these are my thoughts from my own experience. It appears some codes already conflict internationally, so I don’t think using shorter codes would cause additional confusion. If you have similar frustrations regarding time zone codes in your region, feel free to adapt this idea.