-
-
Notifications
You must be signed in to change notification settings - Fork 93
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
AWS Route 53 #1
Comments
But can't we match the nameservers on hit and trial basis,deleting and creating zone until one of the ns matches |
@0xpr4bin This was patched for the most part where AWS won't serve the previously assigned NS pairs. It can happen in a very limited number of scenarios but as far as we are aware this is effectively patched. |
Have received a couple of successful NS takeovers over the last week. So I would recommend setting the label back to vulnerable. |
@schniggie can you describe what steps you took? |
Could you please show us proof of your claims? Stating baseless claims without facts or proof is merely a fallacy. |
Service
AWS Route 53Status
Not VulnerableNameservers
ns-****.awsdns-**.org
ns-****.awsdns-**.co.uk
ns-***.awsdns-**.com
ns-***.awsdns-**.net
Explanation
AWS Route 53 is no longer vulnerable to DNS takeovers even when SERVFAIL errors are returned due to changes by the team that stops takeovers via newly created zones. This has been independently verified.
The text was updated successfully, but these errors were encountered: