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.

Preface

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 domainsbyproxy.com. 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.

Instructions

Overview

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:”.

Notes

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:
   privacy-selected-div
   • 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:

     element.style {
         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.

Screenshot showing how to display the privacy-selected-div using Chrome's Developer Tools.

7. 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 Go Daddy My Renewals page showing the Domains By Proxy customer number (highlighted at the lower left).

8. 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.

Disclaimers

• 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

• How to Remove Domains by Proxy at eHow
• Escaping GoDaddy and Domains by Proxy by Aaron James Young

A rant on time zone code usage

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

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?

Exactly.

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.

Afterword

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.

On a Journey

I have begun a new phase of my journey. I am beginning an internship at the International House of Prayer in Kansas City (IHOP-KC). During the internship I will have the opportunity to learn more about God and grow closer to Him in an environment of 24/7 prayer and worship.

I first visited IHOP-KC in December 2008 while visiting friends in Kansas City. I was in a dry season spiritually and was more interested in visiting my friends than the prayer room. But I did go and God greatly ministered to me. I got set free from some of my struggles and shame. And I fell in love with Jesus again.

God has continued to work in me since then. I visited IHOP-KC multiple times and went to a couple events and God continued to minister to me. After praying, I felt led to spend a longer season pursuing God in Kansas City through an internship.

Would you consider partnering with me through a special gift during this journey? Any amount you can give will be appreciated. Thank you!

Note: Gifts are not tax-deductible.

Time for a transition

I'm moving to Kansas City.

For the past six years I've worked at the Every Nation Ministries office in Nashville and Los Angeles. It's been amazing and I will miss my coworkers who made working there a joy. But for the past couple years I have been feeling that it's time for a transition.

And that time is now. Well, next week, actually.

I plan to spend this next season at the International House of Prayer in Kansas City. Over the past couple years I visited a few times and God has used IHOP-KC to breathe new life into my relationship with Him. I am excited to spend this next season there.

I feel like I have already learned and grown so much this year. I'm going to miss Nashville and all my friends there, but I am in love with God and full of faith. My eyes are on Him and I know He's got me in His hands.

I’m heading to Baja (not any more)

Update: I am no longer going to be going to Baja, Mexico this June.

In less than two months, I will be heading south of the border! I’m going to Baja, Mexico June 2-7 to share the love of Jesus with the people there.

I’m excited for the opportunity to help build a couple houses, build a church, host a fiesta and share the Good News of Jesus Christ. I am going with Ten Days Mission Experiences and several young people from my church’s youth group that I’m involved with will be participating.

It has been nine years since my last mission trip. And Ten Days is a part of the ministry I’ve worked for the past several years. I’m excited for this trip and look forward to seeing all that God will do.

I’m currently looking for people who would be willing to partner with me through prayer or giving financially. Would you partner with me to share the love of Jesus with the people of Baja, Mexico?

If you would like to pray, please leave a comment on this blog or e-mail me at mhenry07 on gmail.

If you would like to give you may do so online at giving.everynation.org/tendays.

Tips for giving online: First, select a frequency and click Next. Then, select “the ministry of a particular Ten Days missionary,” select the “Baja, Mexico” trip, select my name, enter an amount then continue to enter your personal info and payment info.

Thank you, and may God bless you!

But you will receive power when the Holy Spirit comes upon you. And you will be my witnesses, telling people about me everywhere—in Jerusalem, throughout Judea, in Samaria, and to the ends of the earth. – Acts 2:8

Growing up in a superhero family

Have you ever wondered what it would be like to discover you’re a superhero? What if your whole family were superheroes?

On Thursday I watched The Incredibles with friends to finish off a great Thanksgiving. I was intrigued by the way Helen and her kids (Violet and Dash) reacted to danger as a family.

(Helen, Violet  and Dash safely land in the ocean after escaping from their plane.)

Violet: What are we gonna do?

Dash: We're dead! We're dead!

Violet: It blew up!

Dash: We survived but we're dead!

Helen: Stop it! We are not gonna die! Now both of you will get a grip. Or so help me I will ground you for a month! Understand?

…

Dash: You want to go toward the people that tried to kill us?

Helen: If it means land, yes.

Violet: You expect us to swim there?

Helen: I expect you to trust me.

Helen knows who she is. She is Elastigirl and she confronts danger with confidence. Violet and Dash, on the other hand, panic.

Why do they freak out? I think it’s because they don’t know their true identities. They’re aware they have superpowers, but they’ve grown up hearing they should never use them and they should act “normal”.

Helen later tells the kids, “Your identity is your most valuable possession. Protect it.”

I think many who’ve been adopted as God’s children face a similar identity crisis to Violet and Dash. We’ve heard we can do all things through Christ. But we constantly feel pressure to fit in and rely on what we see. And when our faith is tested we tend to get anxious and allow doubt to creep in.

Violet is particularly doubtful and insecure. She’s been told all her life to forget about her powers. Then all of a sudden she is asked to use them in an emergency, but she fails. She must feel frustrated and confused.

Ever feel like that? I have.

But even after her failure her mom doesn’t doubt Violet’s identity. She lovingly forgives her and tells her to be true to herself (finally):

Helen: If anything goes wrong, use your powers… Vi, I’m counting on you. Be strong.

…

Violet: Mom! Mom, what happened on the plane. I'm… I'm sorry. I wanted to help. I mean, when you asked me to… sorry.

Helen: Shhh. It isn't your fault… But things are different now. And doubt is a luxury we can’t afford anymore, sweetie. You have more power than you realize. Don’t think. And don’t worry. If the time comes, you’ll know what to do. It’s in your blood.

I think God believes in us more than we do. And when we fail, He doesn’t love us any less. He lovingly encourages us to get back up and try again. We need to hear and believe what He says about us so we can have the confidence to walk in His will.

Superheroes are a bit like royalty, who… “already know who they are inside, which enables them to become selfless and give out more than they receive” (p. 77, The Supernatural Ways of Royalty by Kris Vallotton and Bill Johnson).

After Violet and Dash understand and experience their true identities as superheroes, they gain confidence, defeat bad guys and help save a city.

Who does God say you are? What can happen once you believe it?

Some things I’ve been learning lately

I’m using ASP.NET MVC in my current project at work and have been learning a lot in the process. I’ve read a lot of articles and watched some videos. I recently went through the NerdDinner Tutorial which was quite helpful and read most of Professional ASP.NET MVC 1.0. But there’s a lot more to writing a production app than can be learned from reading or even working through a tutorial – so it’s been a slow process, but I feel like I’m learning a lot.

The past few years I’ve been working mostly in classic ASP. I’ve done some C# on the side and a couple basic ASP.NET projects. There are a few reasons I chose to do this project on a new platform. I want to stop developing new features in an outdated platform. I want to make use of some functionality built-in to the .NET Framework. And I want to learn and use some better development practices.

Actually developing a real project in ASP.NET MVC has been a bit of a leap though. I feel like I’m biting off a big chunk. Here are some of the things I’ve been learning:

• I’m trying to be test-driven (well, except for database access, file access and HTML output – but at least they’re isolated so the other parts are easier to test). It seems to be going better than my previous attempts.
• I’ve been learning Rhino Mocks for mocking and stubbing.
• I’m using an object-relational mapper (Fluent NHibernate) for the first time to hopefully reduce redundant database-access code. There’s still a fair amount of raw SQL, but the surrounding code is simpler. (I didn’t use LINQ to SQL because Visual Web Developer Express doesn’t support connecting to an external SQL server.)
• I just added StructureMap for dependency injection (DI) so that my classes can be more loosely coupled. I started out with poor man’s DI, but just switched to rich man’s… er, using a container.
• I’m trying to minimize the use of “magic strings” by making use of the strongly-typed HTML helpers in the MVC futures library. I also found the TestControllerBuilder from MVC Contrib helpful for testing HttpContext.
• I feel like I’m learning OO better. Living in VBScript for so long didn’t help much. I’m also learning the MVC pattern and framework, ASP.NET, C# 3 and LINQ better. I’m currently working on a custom role provider to take advantage of roles from the existing app.
• On that note, I’ve been realizing how much infrastructure is in the existing app that I took for granted that I will have to port, convert to a web service or use COM interop for.
• I can sort of deploy it to IIS6 but it’s not one step. Still trying to figure out the best solution.

I was a little scared about all the different things I might have to learn for this project, and looking at this list I can see why. I didn’t absolutely have to learn all of this, but I like to do things “right” and I want to grow as a developer. I believe I’m past the hardest new challenges. I’ve got basic usable functionality. There’s still work to do, but hopefully that will progress more quickly.

There are still several things I would like to learn and do in the future, including:

• Finish this project
• Test-driven JavaScript
• Acceptance/integration testing
• Continuous integration
• Scripting database setup and changes
• Switch from Subversion to Git at work
• Do all new development in a more modern platform than classic ASP and eventually convert most or all of the older code

That’s it for now. If you found any of it interesting then cool beans ;-). Feel free to comment if you’d like.