Beep boop, I’m a bot! I dug through the forum to get you started. I sometimes get things wrong though, so do with this what you will until a human has a look.
We can’t remove this warning, because only Google can remove a Safe Browsing listing. It also doesn’t come from InfinityFree’s servers. Google’s scanners judge what a site looks like, and the article below explains how that works and how to get a review.
This article covers the warning, the common causes and the review process:
A “T/A” example URL doesn’t mean nothing is wrong. The article says the examples are only a sample, so it doesn’t narrow down which pages Google flagged. It lists these likely causes:
- A copy of another site’s login page, or another brand’s name or logo.
- A hacked site, for example through outdated software.
- A false positive. This mostly hits sites where the first thing a visitor sees is a login form, and new sites with little history are judged more strictly.
Your hosting account is about a month old, so the false positive is plausible. But I can’t tell from here which of these applies to you.
What does a visitor see when they open https://absensipklulbi.wuaze.com/? Is it a login form straight away, or a page that explains what the site is? And does the site use any name, logo or design from another organisation or service?
If it’s a login form first, the article suggests adding a public homepage. It should say what the site is for and who runs it, with contact details. After that, request a review once in Search Console’s Security Issues report, and explain what the site and its login are used for. Your report through the Safe Browsing form is already sent, so don’t submit a new one while it’s pending.
If you find files you didn’t upload, the article’s advice is to remove them. It also says to update your software and change your hosting account and admin passwords.