www.nom.gd

nom.gd

nom.gd is a public DNS server (like xip.io or in-addr.arpa) that responds to DNS queries based on the DNS name. What is special about nom.gd is that it is present on the PSL, so every subdomain is a different “site”.

Usage

A records

$ dig prfx--1-2-3-4-a.nom.gd @ns1.nom.gd

; <<>> DiG 9.16.15-Debian <<>> prfx--1-2-3-4-a.nom.gd @ns1.nom.gd
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10680
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;prfx--1-2-3-4-a.nom.gd.		IN	A

;; ANSWER SECTION:
prfx--1-2-3-4-a.nom.gd.	2147483647 IN	A	1.2.3.4

;; Query time: 56 msec

Prefix must be 4 chars or less. If it’s 2 chars long, it might be an invalid idn.

Note: you can build up subdomains under the prefix, but then the total length of the full domain can’t be longer than the prefix. So, www--1-1-1-1-a.nom.gd will work, so will ww.w--1-1-1-1-a.nom.gd but www.a--1-1-1-1-a.nom.gd will not because www.a is longer than 4 characters. This applies to sub-subdomains too (w.w.w--1-1-1-1-a.nom.gd won’t work because it’s too long). This restriction exists to limit the risk of abuse by phishing.

NS records

$ dig prfx--1-2-3-4-ns.nom.gd @ns1.nom.gd

; <<>> DiG 9.16.15-Debian <<>> prfx--1-2-3-4-ns.nom.gd @ns1.nom.gd
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38858
;; flags: qr aa rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; QUESTION SECTION:
;prfx--1-2-3-4-ns.nom.gd.	IN	A

;; AUTHORITY SECTION:
prfx--1-2-3-4-ns.nom.gd. 2147483647 IN	NS	ns1--1-2-3-4-a.nom.gd.

;; ADDITIONAL SECTION:
ns1--1-2-3-4-a.nom.gd.	2147483647 IN	A	1.2.3.4

;; Query time: 48 msec

Prefix must be 5 chars or less. If it’s 2 chars long, it might be an invalid idn.

Note: you can build up subdomains under the prefix, but then the total length of the full domain can’t be longer than the prefix. So, www.a--1-1-1-1-ns.nom.gd will work, so will xyz.a--1-1-1-1-ns.nom.gd but mail.a--1-1-1-1-ns.nom.gd will not because mail.a is longer than 5 characters. This applies to sub-subdomains too (a.a.a--1-1-1-1-ns.nom.gd will work, but xx.y.z--1-1-1-1-ns.nom.gd won’t because xx.y.z is too long). This restriction exists to limit the risk of abuse by phishing.

Abuse

It is possible that a specific domain might be hosting dubious content. Unfortunately, since nom.gd does not actually host the content, it can’t take it down (the hosting provider is the only one that can). Follow the instructions below on how to report it to the hosting provider and other sites.

https://docs.google.com/forms/d/e/1FAIpQLSfseaTDMQMoDRADuArYkVVP8vMjjX4BlZgVvR8kNELzPOs5ig/viewform