Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

I am not able to visit any Autozone websites??

  • 2 replies
  • 1 has this problem
  • 76 views
  • Last reply by zlloyd1

more options

Hello all, my name is Zack Lloyd. and I use a Macbook Pro laptop, using Firefox 64, and I am not allowed to visit any AutoZone websites for some reason.... Every time I click on any Google search results that are from AutoZone, or if I type autozone into the search bar, I am taken to the attached error page?? Has my IP been blocked by AutoZone, for some reason?? Am I never allowed to even visit one of their websites again, or is something wrong Please?? I have already gone into the browser setting menu, and disabled Proxy, but I am still banned from AutoZone websites, and am hoping someone can explain this to me.... Thanks in advance!!

Hello all, my name is Zack Lloyd. and I use a Macbook Pro laptop, using Firefox 64, and I am not allowed to visit any AutoZone websites for some reason.... Every time I click on any Google search results that are from AutoZone, or if I type autozone into the search bar, I am taken to the attached error page?? Has my IP been blocked by AutoZone, for some reason?? Am I never allowed to even visit one of their websites again, or is something wrong Please?? I have already gone into the browser setting menu, and disabled Proxy, but I am still banned from AutoZone websites, and am hoping someone can explain this to me.... Thanks in advance!!
Attached screenshots

Chosen solution

I seem to have fixed the issue by turning off the Proxy, but it did not kick in until after rebooting the machine....

Read this answer in context 👍 0

All Replies (2)

more options

What is the actual link your going to when this happens? I have not issue going to my autozone site.

more options

Chosen Solution

I seem to have fixed the issue by turning off the Proxy, but it did not kick in until after rebooting the machine....