HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
indianajson
can-i-take-over-dns
Networking2024–2024
indianajson / can-i-take-over-dns

can-i-take-over-dns

"Can I take over DNS?" — a list of DNS providers and how to claim vulnerable domains.

2Distinct people
3Mentions
0Explicit recommenders
1.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

"Can I take over DNS?" — a list of DNS providers and how to claim vulnerable domains.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 2:19:09 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour3 dated mentions

Observed mentions: 2024-08-01 06:05:27 UTC to 2024-08-01 20:38:58 UTC.

012024-08-01 06:00:00 UTC to 2024-08-01 07:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 1, 06:002024-08-01 07:00:00 UTC to 2024-08-01 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 08:00:00 UTC to 2024-08-01 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 09:00:00 UTC to 2024-08-01 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 10:00:00 UTC to 2024-08-01 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 11:00:00 UTC to 2024-08-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 12:00:00 UTC to 2024-08-01 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 13:00:00 UTC to 2024-08-01 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 1, 13:002024-08-01 14:00:00 UTC to 2024-08-01 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 15:00:00 UTC to 2024-08-01 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 16:00:00 UTC to 2024-08-01 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 17:00:00 UTC to 2024-08-01 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-08-01 18:00:00 UTC to 2024-08-01 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 19:00:00 UTC to 2024-08-01 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 20:00:00 UTC to 2024-08-01 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 1, 20:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 1, 06:002024-08-01 06:00:00 UTC2024-08-01 07:00:00 UTC101
Aug 1, 07:002024-08-01 07:00:00 UTC2024-08-01 08:00:00 UTC000
Aug 1, 08:002024-08-01 08:00:00 UTC2024-08-01 09:00:00 UTC000
Aug 1, 09:002024-08-01 09:00:00 UTC2024-08-01 10:00:00 UTC000
Aug 1, 10:002024-08-01 10:00:00 UTC2024-08-01 11:00:00 UTC000
Aug 1, 11:002024-08-01 11:00:00 UTC2024-08-01 12:00:00 UTC000
Aug 1, 12:002024-08-01 12:00:00 UTC2024-08-01 13:00:00 UTC000
Aug 1, 13:002024-08-01 13:00:00 UTC2024-08-01 14:00:00 UTC000
Aug 1, 14:002024-08-01 14:00:00 UTC2024-08-01 15:00:00 UTC000
Aug 1, 15:002024-08-01 15:00:00 UTC2024-08-01 16:00:00 UTC000
Aug 1, 16:002024-08-01 16:00:00 UTC2024-08-01 17:00:00 UTC000
Aug 1, 17:002024-08-01 17:00:00 UTC2024-08-01 18:00:00 UTC101
Aug 1, 18:002024-08-01 18:00:00 UTC2024-08-01 19:00:00 UTC000
Aug 1, 19:002024-08-01 19:00:00 UTC2024-08-01 20:00:00 UTC000
Aug 1, 20:002024-08-01 20:00:00 UTC2024-08-01 21:00:00 UTC101

What Hacker News says

1 sources
I had something similar happen to a client using Cloudflare. The attacker somehow was able to establish a new account(s) at CF that used the same free nameservers as my client. When my client's domain expired the attackers added the domain in their CF account, and were then able to control DNS. I reported it to CF security but I'm not sure if the loophole was closed. What I don't know is how the attacker was able to get an account with the same nameservers which are seemingly assigned at random (maybe not?). Maybe they just own/operate thousands of CF accounts? Update: CF claims to have closed this loophole: https://github.com/indianajson/can-i-take-over-dns/issues/10
In Don’t let your domain name become a sitting duck

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.