Max ResingFancy, the authoritative nameservers for the xyz. TLD are as follows:
x.nic.xyz
y.nic.xyz
z.nic.xyz
generationxyz.nic.xyz
How fun. I never thought of the #TLD as being a pun to demographic cohorts.
0ct0pu5Domain name : nibblegap.com
Host name : ns1.nibblegap.com
IP v4 : 5.252.103.62
Domain name : nibblegap.com
Host name : ns2.nibblegap.com
IP v4 : 5.252.100.62
This host can now be used for creating your own #nameservers .....
so free web #hosting for static #websites coming soon?
Host name : ns1.nibblegap.com
IP v4 : 5.252.103.62
Domain name : nibblegap.com
Host name : ns2.nibblegap.com
IP v4 : 5.252.100.62
This host can now be used for creating your own #nameservers .....
so free web #hosting for static #websites coming soon?
Just scraping the #IANA assigned TLDs and the corresponding documented #nameservers. What I don't get is, why so many companies apply for a #TLD. It's not particularly cheap to apply for one of those ngTLDs, yet compared to the company sizes, it's probably pennies. Is it a prestige investment? Is it a digital resource to grab, before someone else does it?
Other than #Microsoft, #Google, and #AWS, I've rarely seen any ngTLD representing a corporation's name to actually be used in practice.
Does anyone in the #infosec community share their view?
sahilisterbgp.tools being served via 13 authoritative name servers (via 3 different providers + in house NS):
```
$ dig +short ns bgp.tools
ns1.exoscale.ch.
ns-721.awsdns-26.net.
ns-1329.awsdns-38.org.
ns4-35.azure-dns.info.
ns3-35.azure-dns.org.
ns1.exoscale.io.
ns-302.awsdns-37.com.
ns-1799.awsdns-32.co.uk.
ns1.exoscale.net.
ns1-35.azure-dns.com.
ns2-35.azure-dns.net.
ns1.exoscale.com.
backup-ns.bgp.tools.
```
Bart KnubbenQua Europese (anycast) nameserver hosters:
- https://cloudns.net/ (Bulgaarse partij levert o.a. aan overheid)
- https://desec.io/ (innovatieve Duitse non-profit)
- https://www.netnod.se/dns (Zweedse operator van een van de root name servers)
- https://www.rcodezero.at (verbonden aan Oostenrijkse TLD operator)
Zie verder nog: https://european-alternatives.eu/category/managed-dns-providers (@european_alternatives).
In January 2023, #Cloudflare replaced #Verisign in providing #DNS #registry services for the .gov #TLD. Besides the registry, they also run the authoritative #nameservers.
Verisign ran it for 12 years, and cost the #US #government apparently just half as much as Cloudflare charges ($7.2M).
Verisign loses prestige .gov contract to Cloudflare - Domain Incite
Cloudflare is to take over registry services for the US government's .gov domain, ending Verisign's 12-year run. It seems .gov manager CISA, the Cybersecurity and Infrastructure Security Agency, opened the contract up for bidding last August and awarded it to Cloudflare in mid-December. The deal is worth $7.2 million, Cloudflare said in a press release
Recently made the transition to self hosting authoritative name servers. Wrote a bit of secondary options available for it and the experience itself https://blog.sahilister.in/2025/07/secondary-authoritative-name-server-options-for-self-hosted-domains/
Didn't found the process too hard TBF, worth a try.
Case of (broken) maharashtra.gov.in Authoritative Name Servers https://blog.sahilister.in/2025/06/case-of-broken-maharashtra.gov.in-authoritative-name-servers/
TLDR they're broken on multiple levels. Sync broken, RFC 1918 address, each NS giving different response - there's too much going on.
Good enough amount of name servers :P
```
$ dig ns sahil.rocks +short
ns2.afraid.org.
marvin.sahilister.net.
ns1.1984.is.
ns0.1984.is.
ns3.jing.rocks.
colin.sahilister.net.
puck.nether.net.
ns2.albony.in.
ns-global.kjsl.com.
ns4.he.net.
ns5.he.net.
```
I found the case of .UA ccTLD secondaries interesting so did a deep dive on it https://blog.sahilister.in/2025/06/a-look-at-.ua-cctld-authoritative-name-servers/