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.

Sign up for GitHub

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

Jump to bottom

Name.com #8

Open
indianajson opened this issue Jun 1, 2021 · 0 comments
Open

Name.com #8

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

Comments

@indianajson
Copy link
Owner

indianajson commented Jun 1, 2021 •
edited
Loading

Service Name.com

Status Vulnerable w/ purchase

Nameservers

ns1***.name.com
ns2***.name.com
ns3***.name.com
ns4***.name.com

Explanation

Based on this article in the support portal it is possible to add on external domains onto an existing hosting plan. This does require an active Name.com account and a hosting plan.

Additionally, while the naming scheme for their nameservers contains a number and three random letters (e.g. ns1fkl.name.com) this does not seem to affect responses. For example, econfigmrkt.com does not have ns3nrz.name.com as a nameserver, however dig econfigmrkt.com @ns3nrz.name.com will respond NOERROR.

Consequently, despite the paywall, Name.com is vulnerable to takeover.
@indianajson indianajson added the Vulnerable This service is vulnerable to takeover. label Jun 1, 2021
@indianajson indianajson reopened this Jun 1, 2021
@indianajson indianajson added Investigation Needed Further investigation is needed to confirm vulnerability and removed Vulnerable This service is vulnerable to takeover. labels Jun 1, 2021
@indianajson indianajson changed the title Name.com - Vulnerable w/ purchase Name.com Jun 12, 2021
@indianajson indianajson added the Vulnerable This service is vulnerable to takeover. label Jun 13, 2021
@indianajson indianajson removed the Investigation Needed Further investigation is needed to confirm vulnerability label Oct 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Vulnerable This service is vulnerable to takeover.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@indianajson