domain resolving to 0.0.0.0 protected?

I was using a relative's computer, and I noticed that under SafeOnline protection list was a domain that my relative didn't add to SOL. That domain is being blocked access by resolving it to 0.0.0.0.

During a search, my relative entered the website in question, but it failed because it was resolving to 0.0.0.0.

No, it wasn't SOL doing it. It was me. But, I'm wondering why SOL added it to its protection? Odd.

 

Could you send me a PM with the website name? I suspect it is to be expected when redirected to an address like 0.0.0.0 (or 127.0.0.1 in the case of someone serving a website locally) but I can double check on our back-end.

Thanks!

 

Do you know what happened?

 

It looks like this is just caused because of 0.0.0.0 being resolved to a local address which is considered to be protected. You shouldn't have any negative side effects from it.