.gr.com
Generic top-level domain — names are registered at the third level, under .com
- Register
- $14.23first year
- Renew
- $17.73a year
- Transfer
- $14.23to move it
- Registrars
- 2quoting it
- Lookup
- neitherno public service
- DNSSEC
- Signed1 DS record in the root
- Level
- Thirdmybrand.gr.com
Check a name
One command, straight against the registry — no account, no page to load.
ds mybrand --tld gr.comAdd --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
Every published quote in the bundled table, cheapest registration first. The figure ds prints beside .gr.com is the mean of the registration column — $14.23, which undercuts 90% of the 881 priced TLDs.
| Registrar | Register | Renew | Transfer |
|---|---|---|---|
| porkbun.comcheapest | $13.48 | $13.48 | $13.48 |
| namecheap.com | $14.98 | $21.98 | $14.98 |
Mean — what ds prints | $14.23 | $17.73 | $14.23 |
List prices in US dollars, bundled with the binary and last regenerated 2026-09-09. Promotions, ICANN fees, taxes and premium names all move the real number, and a registry may decline to sell you the name at all. See Prices.
Where to register
2 registrars in the bundled table publish a registration price for .gr.com, which is evidence they sell it — nobody prices what they cannot sell. Cheapest first, exactly as ds mybrand --tld gr.com --where prints them.
Put a name in the box above and each link becomes that registrar's search for mybrand.gr.com, where it publishes one. This list is what the price table knows, not the whole market — see Where to register.
Who can register
No eligibility rule is on file for .gr.com, 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
Neither an RDAP endpoint nor a WHOIS server is on file for .gr.com: IANA's bootstrap does not list it and the bundled whois.json has no entry. It is left out of --tld all for that reason, and asking for it by name works only if IANA can name a server for it at the time. Anything ds cannot answer comes back UNKNOWN with the reason attached, never guessed as available.
The registry
From IANA's delegation record for .com — .gr.com is a zone under it, so the registry, the servers and the dates below are .com's. .gr.com is a generic TLD.
- Run by
- VeriSign Global Registry ServicesBased in United States of America. ICANN records the contracted registry operator as VeriSign, Inc. Delegated 1985-01-01, record last updated 2026-03-10.
- Registry site
- www.verisigninc.comWhere the registry documents .com — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
- Published services
rdap.verisign.com · whois.verisign-grs.comWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
a.gtld-servers.netb.gtld-servers.netc.gtld-servers.netd.gtld-servers.nete.gtld-servers.netf.gtld-servers.netg.gtld-servers.neth.gtld-servers.neti.gtld-servers.netj.gtld-servers.netk.gtld-servers.netl.gtld-servers.netm.gtld-servers.netThe 13 authoritative servers for the .com 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.
genericIANA Root Zone Database types it "generic"legacy-gtldICANN delegated it before 2013-10-23 — seedelegated
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 .com was delegated to; this is what the root actually answers with when a resolver asks it where .com lives. .gr.com is not in the root zone — nothing below the top level is. It resolves because .com does, on .com's servers.
- Delegated to
a.gtld-servers.net192.5.6.302001:503:a83e::2:30b.gtld-servers.net192.33.14.302001:503:231d::2:30c.gtld-servers.net192.26.92.302001:503:83eb::30d.gtld-servers.net192.31.80.302001:500:856e::30e.gtld-servers.net192.12.94.302001:502:1ca1::30f.gtld-servers.net192.35.51.302001:503:d414::30g.gtld-servers.net192.42.93.302001:503:eea3::30h.gtld-servers.net192.54.112.302001:502:8cc::30i.gtld-servers.net192.43.172.302001:503:39c1::30j.gtld-servers.net192.48.79.302001:502:7094::30k.gtld-servers.net192.52.178.302001:503:d2d::30l.gtld-servers.net192.41.162.302001:500:d937::30m.gtld-servers.net192.55.83.302001:501:b1f9::30
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 19718ECDSA P-256/SHA-256 · SHA-256
8ACBB0CD28F41250A80A491389424D341522D946B0DA0C0291F2D3D771D7805A
- key 19718ECDSA P-256/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 com. NS and dig +norec @a.root-servers.net com. DS.