Author Topic: Our Website is on Blacklist -> Why?  (Read 1003 times)

0 Members and 1 Guest are viewing this topic.

Offline jutta.rinner

  • Newbie
  • *
  • Posts: 1
Our Website is on Blacklist -> Why?
« on: July 02, 2022, 09:51:36 AM »

the website of the support group 'aspergereltern untermain' is on your URL:Blacklist

It is designed on weebly by me voluntarily.

Can you tell me, what is wrong so that I can repair the website?

kind regards

Offline polonus

  • Avast √úberevangelist
  • Probably Bot
  • *****
  • Posts: 33811
  • malware fighter
Re: Our Website is on Blacklist -> Why?
« Reply #1 on: July 02, 2022, 12:26:04 PM »
Hi jutta.rinner,

Wait for a final verdict from avast team, as they are the only ones to come and unblock.

On Jan. 11th this year abuse on the IP of that website has been reported by a honeypot.
AbuseIPDB says was found in their database for pages-custom-24.weebly dot com. However it is possible this IP is no longer being involved in such abusive activities.

Webpage comes up as untitled and the connection qualified insecure, (only later it becomes redirected to the the full https connection. Therefore  avast flags (which seems reasonable).

Access before redirect is denied to chrome and flagged as insecure,
because one has entered code before the actual websites' code in the DOM,
File size: 91.44 KB
File MD5: 3576a6e73c9dccdbbc4a2cf8ff544ad7

- - archive JS-HTML
>-[13406][39be] - Ok
- - Ok
The OK's in the quote are from Dr. Web's scanner,
that gives the page an all-green.

Report to weebly, your CMS service and ask for support to level this problem out.


(volunteer 3rd party cold recon website security analyst and website error-hunter)
Cybersecurity is more of an attitude than anything else. Avast Evangelists.

Use NoScript, a limited user account and a virtual machine and be safe(r)!

Offline JakubS

  • Avast team
  • Newbie
  • *
  • Posts: 5
Re: Our Website is on Blacklist -> Why?
« Reply #2 on: July 03, 2022, 02:09:34 PM »
Hi jutta.rinner,

This was false positive detection and it is fixed now.
We apologize for any inconvenience caused.

Best regards