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

000Domains #19

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

000Domains #19

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

Comments

@indianajson
Copy link
Owner

indianajson commented Jun 9, 2021

Service 000Domains

Status Vulnerable

Nameserver

ns1.000domains.com
ns2.000domains.com
fwns1.000domains.com
fwns2.000domains.com

Explanation

000Domains is owned by Dotster, powered by Domain.com, which means creating a zone on Domain.com also creates a zone on Dotster and 000Domains (and vice versa). For example, 4orty3.net uses Dotster's DNS, however ns1.domain.com and ns1.000domains.com will resolve all records for 4orty3.net.

Per Domain.com's Knowledge Base you can add external domains if you have an existing account (you can purchase something then cancel to get an account).

To perform a takeover on 000Domains, get an account on Domain.com and add the zones there (which will activate the zone on 000Domains).

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

ns0-1.domaincontrol.com dns can takeover?

@indianajson
Copy link
Owner Author

indianajson commented Feb 1, 2023

ns0-1.domaincontrol.com dns can takeover?

@abusabiha "domaincontrol.com" is GoDaddy and not vulnerable.

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