Security Technology

Please contact” – wtf?

please contact"

I came into work today, and was met with some people telling me that our site had been blacklisted. It took a lot of runaround, and everyone denying involvement, but it sorta worked itself out. So what exactly happened?

Our Internet is hosted through XO Communications. Our domain is registered through, and hosted through Yahoo Small Business. We have an internal DNS that we run on a Windows 2003 SBS Server, and our Active Directory is “hitrunscore.local”.

First I called Yahoo support to confirm whether or not it was them. They said that any mention of an official email from Yahoo would include “” on the end of it. They said they’d look into it, but that it wasn’t anything this guy had heard of, nor could he duplicate it on his end.

Strange. I guess that means it’s localized between every PC in my company up to some point before Yahoo’s servers get involved.

So we do a Trace Route on the domain.


Comes up with the IP – but it doesn’t deviate from the direct path between XO’s servers (algx, xo) to the backbone in my area (DTX-Dallas), to Yahoo’s servers. And it ends up on a server.

So I ping – which was also giving me the same issue…


That gives me the same address: My initial inclination was that “OK, this is an ISP related thing. Maybe the DNS is bad for a record related to this IP address.” In reality, DNS handles name resolution – not IP resolution.

So, to make sure it wasn’t an in-house issue, I disconnected the WiFi Router, cleared the cache on the DNS server, Scavenged for old records, and restarted the service. That didn’t solve it, so I restarted the actual server. That too didn’t solve it.

Then I gave XO a call, and after I talked with 3 XO support groups, none of them gave me a real answer except that they didn’t know, and didn’t know anyone that could help.

The Unlikely Solution

While on the phone with them, I was trying to visit the IP again, and hit the F5 button several times on the page, out of frustration. And instead of getting the ‘please contact” ‘ message, I noticed that I intermittently got a legitimate webpage error.

2009-12-07_1142This page actually had an error on it, and had some HTML source code. There was also a JavaScript in it being called from Yahoo’s official file servers. This changes things. It’s no longer and ISP or DNS or local issue. It’s a Yahoo issue.

Yahoo’s engineers are reportedly still looking into the issue, and it has happened once more since it was first fixed – but instead of lasting for an hour, it only lasted about 5 minutes.

From my chair, it appears to be a problem with the redirect from ( to ( And because our domain was hosted on the yahoo stores platform, there is some kind of facade-ing going on with the domain in the address bar, vs what’s actually being called. This correlates with our search url…/nsearch?catalog=hitrunscore&… where one search page is being used for multiple “catalogs”. It would not surprise me if one store domain is being used and subsequently masked for multiple catalogs in the same manner. Thus if couldn’t redirect properly, neither could the store.

I’m still baffled as to why it was a localized issue though, that only affected our building. And just as I typed this last part, the site went down again with the same issue. I’ll post an update when Yahoo has a real solution.

An Official Yahoo Update

I spoke with our Yahoo Small Business Representative, and he asked if there was anything that we had done this morning that could have caused a spike in business. The Yahoo systems look for and take appropriate actions to prevent Denial of Service attacks (DOS attack) on their systems. That was the case for us. While, yes, the redirect was broken, it was because we sent out an email campaign with the landing page and images hosted on our store. We sent that out to 40,000 people, all at the same time because of the increased open rate of doing it during the day. Unfortunately Yahoo’s servers detected it as a DOS attack on their system and blacklisted our IP. They have since Whitelisted our IP and recommended we stagger our email releases according to the timezone of the recipient.

So if you’re having the same issue, hopefully this helps pinpoint why you are, and you’ll know to take another look at what you’ve done recently that would have a caused a spike in your pageviews as Yahoo perceives them, and you can solve your issue sooner than we did.


After Christmas came around, it happened again, but we finally determined that it was Yahoo’s fault. They had made some security changes on their server to try and prevent DOS attacks and the like, but the settings were faulty and threw false positives. This blocked our IP again, and it went up and down several times during the day. They put our IP on a Whitelist, and to my knowledge it hasn’t happened in a while…if not since then. If this is happening to you, contact your Yahoo Store Representative and either ask him to have the engineers put your IP on a whitelist, or ask for the Top Tier Tech Support phone number and make the request yourself after they walk you through the troubleshooting stuff.

By [[Neo]]

I am a web programmer, system integrator, and photographer. I have been writing code since high school, when I had only a TI-83 calculator. I enjoy getting different systems to talk to each other, coming up with ways to mimic human processes using technology, and explaining how complicated things work.

Of my many blogs, this one is purely about the technology projects, ideas, and solutions that I have come across in my internet travels. It's also the place for technical updates related to my other sites that are part of The-Spot.Network.

3 replies on “Please contact” – wtf?”

As it turned out, there were some changes Yahoo made on their end for the Holiday season, to prevent site-attacks – which caused their system to trigger false-positives for that IP, and they block it. You should contact the Top-Tier technical support and tell them that is going on so they can look into it.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.