We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

How do I remove an attack site warning from my domain?

  • 3 antwurd
  • 1 hat dit probleem
  • 7 werjeftes
  • Lêste antwurd fan cor-el

more options

Registered a domain in December. Even before going live with website the domain was flagged as attack site. Was reviewed and cleared by StopBadware, but still being flagged by Firefox. Please remove this and allow visitors to the site! 'Disguised" url: http:?// www. u s a n a 2 0 1 3 .co .za

Registered a domain in December. Even before going live with website the domain was flagged as attack site. Was reviewed and cleared by StopBadware, but still being flagged by Firefox. Please remove this and allow visitors to the site! 'Disguised" url: http:?// www. u s a n a 2 0 1 3 .co .za

Alle antwurden (3)

more options

I get a status 200 with a message from the site that it is under construction. If I am using the correct URL (www.usana2013.co.za) maybe you need to clear your Firefox cache.

The database of attack & phishing sites is not directly maintained by Firefox.

See also

more options

Thank you John99 I cleared my cache before posting my question. And verified the site with Google and had a review done by StopBadware (which came out 'clean'). You have the correct url; and yes; the site is still under construction. That is the whole problem; the url is being flagged regardless of not having a live site! On my pc I don't get any warnings now; but some of my colleagues still get it on theirs; when using Firefox (and even after clearing their cache). IE and Google chrome don't give the warning; that is why I'm asking Firefox to tell me what's going on please?

more options

You can set the urlclassifier.max-complete-age pref to 0 on the about:config page to let entries in the phishing protection database expire more easily.