.net.sg
Country-code top-level domain for Singapore — names are registered at the third level, under .sg
- Register
- —first year
- Renew
- —a year
- Transfer
- —to move it
- Registrars
- —quoting it
- Lookup
- WHOISanswers for it
- DNSSEC
- Signed1 DS record in the root
- Level
- Thirdmybrand.net.sg
Check a name
One command, straight against the registry — no account, no page to load.
ds mybrand --tld net.sgAdd --where for the registrars and the registry's rules, --registry for the server that answered, or --all-info for everything at once.
What it costs
No registrar in the price table bundled with ds quotes .net.sg, so the CLI prints no figure beside it — one of 927 such TLDs. That is a gap in the table as often as it is a TLD nobody sells. See Prices for supplying your own table with --pricing-file.
Who can register
No eligibility rule is on file for .net.sg, which is not the same as a promise that it is open: the list is hand-maintained and covers the restricted TLDs a registrar is likely to offer you. Check the registry's own page before counting on a name. 81 TLDs do carry a rule — see Who can register.
How ds answers for it
RDAP first, WHOIS second — the same order for every TLD. .net.sg has no RDAP service, so the answer comes from WHOIS text on port 43.
- WHOIS
whois.sgnic.sgQueried on port 43, from the bundled whois.json. The name is called free when the reply contains---Not found— text matching, which is why RDAP is preferred where it exists.
ds mybrand --tld net.sg --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .net.sg today. See Accuracy notes.
The registry
From IANA's delegation record for .sg — .net.sg is a zone under it, so the registry, the servers and the dates below are .sg's. .net.sg is a country-code TLD.
- Run by
- Singapore Network Information Centre (SGNIC) Pte LtdBased in Singapore. Delegated 1988-10-19, record last updated 2026-02-04.
- Registry site
- www.sgnic.sgWhere the registry documents .sg — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
- Published services
rdap.sgnic.sg · whois.sgnic.sgWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
dsany2.sgnic.sgdsany3.sgnic.sgdsany4.sgnic.sgns4.apnic.netpch.sgzones.sgThe 5 authoritative servers for the .sg zone — what the root delegates to. Nothingdsqueries directly; they are what makes a registered name resolve.
What it is
Derived from the root zone and ICANN's registry list — each one is a fact with a source.
country-codeIANA Root Zone Database types it "country-code"
In the root zone
The delegation itself, read out of the root zone — serial 2026090900, on 2026-09-09. The registry section above is IANA's record of what .sg was delegated to; this is what the root actually answers with when a resolver asks it where .sg lives. .net.sg is not in the root zone — nothing below the top level is. It resolves because .sg does, on .sg's servers.
- Delegated to
ns4.apnic.net202.12.31.532001:dd8:12::53pch.sgzones.sg204.61.216.572001:500:14:6057:ad::1dsany2.sgnic.sg185.159.197.1702620:10a:80aa::170dsany3.sgnic.sg185.159.198.1702620:10a:80ab::170dsany4.sgnic.sg45.142.220.652a0e:dbc0:1::65
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 26329RSA/SHA-256 · SHA-256
404A15E6CA2F4CE259D8B2BD13894C7823A9513973103C962FF52BFC57A380AF
- key 26329RSA/SHA-256 · SHA-256
Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net sg. NS and dig +norec @a.root-servers.net sg. DS.