-
-
Notifications
You must be signed in to change notification settings - Fork 155
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
[FALSE-POSITIVE] Amazon.in #687
Labels
false positive
all false positive review requests
Comments
If you don't have the time to provide the minimal info, we don't have the time to help you investigating the issue. $ nslookup amazon.in 88.198.70.38
Server: 88.198.70.38
Address: 88.198.70.38#53
Non-authoritative answer:
Name: amazon.in
Address: 52.95.116.115
Name: amazon.in
Address: 54.239.33.92
Name: amazon.in
Address: 52.95.120.67 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Help us, report at the right place!
All the issue posted here which relates to the whitelisting process will be moved into our backend.
Therefore, please submit your issue into our backend: https://github.com/Ultimate-Hosts-Blacklist/whitelist/issues
Thanks for your time and understanding.
The Ultimate-Hosts-Blacklist team.
Describe the subjects (domains)
Please list any domains listed here which you believe are a false positive.
More Information
How did you discover your web site or domain was listed here?
Have you requested removal from other sources?
Please include all relevant links to your existing removals / whitelisting.
WARNING: Please search in our infrastructure before submitting it.
Additional context
Add any other context about the problem here.
❗
We understand that this can be frustrating and embarrassing for many web site owners. The first step is to remain calm. The second step is to rest assured one of our team members will address your issue as soon as possible. Please make sure you have provided as much information as possible to help speed up the process.
The text was updated successfully, but these errors were encountered: