Author Topic: freedns.afraid website  (Read 2641 times)

0 Members and 1 Guest are viewing this topic.

REDACTED

  • Guest
freedns.afraid website
« on: March 10, 2017, 11:07:10 PM »
Hi, a while time ago I had my website (lafus.com.ar) on freedns.afraid.org. I have saw a while ago that my site is under your blacklist cause it using DNS of afraid, that's why I changed DNS and use a really DNS server (about 2014) but lafus.com.ar still under your blacklist.
I tried accessing whit alternative url and no avast warning appear.
What can I do?

Thank you very much and apologies for my poor english!


REDACTED

  • Guest
Re: freedns.afraid website
« Reply #2 on: March 11, 2017, 12:56:17 AM »
Thanks!
I'll review these links.

REDACTED

  • Guest
Re: freedns.afraid website
« Reply #3 on: March 26, 2017, 09:17:41 PM »
Hi again Eddy.
I cleaned my website, the host server was confirmed me than all the DNS are ok.
The ESET's team recently added my website in his whitelist in last update.
How do I do to get on your whitelist?

Thank you very much again!

Offline jefferson sant

  • Starting Graphoman
  • *
  • Posts: 6677
  • volunteer
Re: freedns.afraid website
« Reply #4 on: March 27, 2017, 01:54:06 AM »


Hello.

You should contact through the link.

https://www.avast.com/en-us/report-a-url.php

There was no reply there 2 weeks in this topic ,I believe you do not want to waiting any longer for response.

I will report this to Virus analyst.
« Last Edit: March 27, 2017, 03:21:47 AM by jefferson sant »

Offline HonzaZ

  • Avast team
  • Advanced Poster
  • *
  • Posts: 1038
Re: freedns.afraid website
« Reply #5 on: March 27, 2017, 08:36:24 AM »
lafus.com.ar unblocked ;)!

REDACTED

  • Guest
Re: freedns.afraid website
« Reply #6 on: March 27, 2017, 03:20:09 PM »
Thank you very much!!  :D

Offline Eddy

  • Avast Evangelist
  • Maybe Bot
  • ***
  • Posts: 31079
  • Watching (over?) you
    • Malware removal, Biljart and other things.
Re: freedns.afraid website
« Reply #7 on: March 28, 2017, 01:52:27 AM »
I hope you also took care of that vulnerable library.

It will not cause a new blacklisting, but when it comes to security (and with that to prevent problems) you better be safe than sorry right ;)