EAN-133348901296632   EAN-13 barcode 3348901296632
Amazon.com12-18-2019 5:10:10am
Kroger04-08-2021 10:47:41pm
UPCChecker.com12-18-2019 5:10:11am
Upcdatabase.org12-18-2019 5:10:10am
Product Name3348901296632
Created12-18-2019 5:10:09am
Modified04-08-2021 10:47:42pm
MD53618511c81b072d07acc032dd3fc4026
SHA25664fc36fd22e731b09b65bb9de518ef27237149ce0c22af2db5ca1b1b732bfee9
Search Googleby EAN or by Title
Query Time0.0059991

This product was recently detected and it could take some time for us to locate more information. You can check back later or you can contribute to the site by entering the additional information to this page.

We do our best to track down as much information as possible about each product but in the end, it takes people like you to help us out by looking at the products and adding information. After all, we can't get our hands on every product in the database.

We have web bots that go out into the wild and try to find additional data but they can only do so much. That is why we rely on the public and manufacturers to provide quality data.

Hopefully, what you are finding here is of value and you will continue to use the site and to help us by adding more data. We really appreciate every bit of help we get.


Article of interest

We are not hosted at GoDaddy, but we are registered there and have our DSN settings stored with them. So when Anonymous attacked GoDaddy, we were impacted too.

It is very sad that hackers don't think about all of the people that will be impacted by their actions. Even though we were not attacked directly, we were impacted and most of our users were also impacted.

Our site was up and running the entire time and because many DNS servers cache the address to our site, we had a steady flow of traffic during the attack. But the number of visiters to the site was clearly lower than normal. We had a significant drop in visitors and even after things were fixed by GoDaddy things weren't quite normal again until quite late in the evening.

If you or your applications were impacted by this attack we are deeply sorry but there was nothing that we could do to prevent or recover from this. Just like you, all we could do is wait for GoDaddy to deal with the situation.

Here are some news links you can read relating to the attack:

Update 9/13/2012 - It appears that this may not have been an attack after all. GoDaddy is saying that this was not an attack but a configuration error that cascaded through their routers taking their services off line for about six hours. Be it an attack or an accidental configuration issue makes no real difference to the end users that couldn't gain access to the web sites hosted on or registered with GoDaddy.

From GoDaddy:

Although this was all very annoying, no personal information seems to have been accessed such as passwords, credit card numbers, addresses, phone numbers or alike. Personally, being a technical person, I feel GoDaddy handled this situation quite well. I am not happy that it happened or that our users were unable to get to the site. But the tech team at GoDaddy did a very good job at correcting the problems.


Close

Search

Close

Share