Skip to content
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

DNSimple #16

Open
indianajson opened this issue Jun 9, 2021 · 5 comments
Open

DNSimple #16

indianajson opened this issue Jun 9, 2021 · 5 comments
Labels
Vulnerable This service is vulnerable to takeover.

Comments

@indianajson
Copy link
Owner

indianajson commented Jun 9, 2021

Service DNSimple

Status Vulnerable

Nameserver

ns1.dnsimple.com
ns2.dnsimple.com
ns3.dnsimple.com
ns4.dnsimple.com

Explanation

You can sign up for a free account on DNSimple. After creating your account go to Domains and click Add Domains. If you are able to create a zone for the vulnerable domain then takeover is possible. REMEMBER, the zone will not function until you start a 30-day trial with DNSimple, which requires a credit card on file.

False Positives

DNSimple can produce false positives because a domain can be in an account where the account owner's payment method has expired, thus the domain will not resolve (i.e. shows a DNS SERVFAIL error), but cannot be added to your account.

@indianajson indianajson added the Vulnerable This service is vulnerable to takeover. label Jun 9, 2021
@indianajson indianajson changed the title DNSimple - Vulnerable DNSimple Jun 12, 2021
@jleuth
Copy link

jleuth commented Nov 9, 2023

I'm getting "*.example.com matches a reserved subdomain"

Repository owner deleted a comment from marcelo321 Nov 11, 2023
@indianajson
Copy link
Owner Author

@dadsgone0 Please see the updated "False Positives" section of this issue. :)

@jleuth
Copy link

jleuth commented Nov 11, 2023

So their domain will not resolve because their payment method is bad, but it cannot be taken over? How is it a false positive then if it can't be taken over? Am i just having a total brain-fart?

@indianajson
Copy link
Owner Author

@dadsgone0 It's a false positive because the way to identify vulnerable domains is if they return a SERVFAIL error. In this case, even though the domain returned the proper error code (indicating it was vulnerable) the domain is actually not vulnerable because it's already in someone's account, (i.e. we thought it was vulnerable but it was a "false positive").

@jleuth
Copy link

jleuth commented Nov 11, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Vulnerable This service is vulnerable to takeover.
Projects
None yet
Development

No branches or pull requests

2 participants