.comsec
Generic top-level domain
- Register
- —first year
- Renew
- —a year
- Transfer
- —to move it
- Registrars
- —quoting it
- Lookup
- RDAP + WHOISanswers for it
- DNSSEC
- Signed1 DS record in the root
- Level
- Secondmybrand.comsec
Check a name
One command, straight against the registry — no account, no page to load.
ds mybrand --tld comsecAdd --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 .comsec, 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 .comsec, 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. .comsec has both, so RDAP answers and WHOIS is the fallback if it does not.
- RDAP
https://tld-rdap.verisign.com/comsec/v1From IANA's bootstrap, refreshed when this page was built. The lookup ishttps://tld-rdap.verisign.com/comsec/v1/domain/mybrand.comsec— a 404 means the name is free.- WHOIS
whois.nic.comsecQueried on port 43, from the bundled whois.json. The name is called free when the reply containsno match for— text matching, which is why RDAP is preferred where it exists.
ds mybrand --tld comsec --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .comsec today. See Accuracy notes.
The registry
From IANA's delegation record for .comsec. .comsec is a generic TLD.
- Run by
- VeriSign, Inc.Based in United States of America. Delegated 2015-10-08, record last updated 2026-03-11.
- Published services
tld-rdap.verisign.com · whois.nic.comsecWhat the registry itself tells IANA it runs. They agree with whatdsasks.- Name servers
ac1.nstld.comac2.nstld.comac3.nstld.comac4.nstld.comThe 4 authoritative servers for the .comsec 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"new-gtldICANN delegated it on or after 2013-10-23, when the 2013 round opened — seedelegated
What it is for
Our reading, not a fact — nothing in the root zone says what a TLD means. Hand-maintained in tld-categories.json.
- Internet & Technology Software, hosting, data, devices, and the web itself.
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 .comsec was delegated to; this is what the root actually answers with when a resolver asks it where .comsec lives.
- Delegated to
ac1.nstld.com192.42.173.302001:500:120::30ac2.nstld.com192.42.174.302001:500:121::30ac3.nstld.com192.42.175.302001:500:122::30ac4.nstld.com192.42.176.302001:500:123::30
dsqueries: these servers know which names exist, not who registered them.- DNSSEC
- Signed — 1 DS record in the root
- key 49881ECDSA P-256/SHA-256 · SHA-256
BF4347FB6BB9C988295F26FADAD5D8A07D6E2DAE7248A99DB78E77247A6305DB
- key 49881ECDSA 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 comsec. NS and dig +norec @a.root-servers.net comsec. DS.