-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
api.webtor.buzz blocked by Cloudflare Malware Blocking DNS (1.1.1.2 and 1.1.1.3) #5
Comments
Ok, I've done as you suggested. |
turned off defender and antivirus and still getting the error. Anything else needed to be done to get website working again? |
@metal1one may I ask you to check network panel in Google Chrome developer tools and check network panel? |
@metal1one just visit https://api.webtor.buzz/ directly and make a screen of an error. And also copy your DNS servers ips... |
Yeah, it appears it is being blocked by whatever DNS my ISP is giving me... changing to googles dns servers and it works. |
Yeah, Cloudflare malware-blocking DNS (1.1.1.2) is still blocking api.webtor.buzz. You can test this on the command line by running ❯ dig @1.1.1.2 api.webtor.buzz +short
0.0.0.0 If you're on linux or mac, you can just add the correct IP address to your
You can help by submitting a request to reclassify api.webtor.buzz with the Cloudflare NetOps team:
|
I am thinking about rotating domains for API (they are quite cheap nowadays). But I don't know how fast my domains would get blocked... I am afraid if these blocks are performed automatic, I would not be able to rotate it with appropriate speed... |
webtor.io is not working. I'm getting
net::ERR_NAME_NOT_RESOLVED
errors in the console logs. It seems the problem is because api.webtor.buzz is blocked by my DNS host, 1.1.1.3:I have reported this false positive to Cloudflare's NetOps team (done here: https://report.teams.cloudflare.com/) as categories
P2P
andFile Sharing
:Since this is not guaranteed to get a response, you might consider using an alternate domain or IP addresses directly.
The text was updated successfully, but these errors were encountered: