ds

.lacaixa

Generic top-level domain

RDAP + WHOIS

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.lacaixa

Check a name

One command, straight against the registry — no account, no page to load.

Fills the command and the registrar links below in with your own name. The page is static — nothing is looked up here, and nothing you type leaves the browser.

ds mybrand --tld lacaixa

Add --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 .lacaixa, 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 .lacaixa, 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. .lacaixa has both, so RDAP answers and WHOIS is the fallback if it does not.

RDAP
https://rdap.nic.lacaixaFrom IANA's bootstrap, refreshed when this page was built. The lookup is https://rdap.nic.lacaixa/domain/mybrand.lacaixa — a 404 means the name is free.
WHOIS
whois.nic.lacaixaQueried on port 43, from the bundled whois.json. The name is called free when the reply contains the queried object does not exist — text matching, which is why RDAP is preferred where it exists.

ds mybrand --tld lacaixa --registry prints whichever of these answered. If a bundled WHOIS host has gone stale, IANA is asked who serves .lacaixa today. See Accuracy notes.

The registry

From IANA's delegation record for .lacaixa. .lacaixa is a generic TLD.

Run by
Fundación Bancaria Caixa d'Estalvis i Pensions de Barcelona, "la Caixa"Based in Spain. ICANN records the contracted registry operator as Fundación Bancaria Caixa d’Estalvis i Pensions de Barcelona, “la Caixa”. Delegated 2014-07-10, record last updated 2026-05-11.
Registry site
www.lacaixa.comWhere the registry documents .lacaixa — its rules, its accredited registrars, and any launch phases. Not a shop: registries sell wholesale to registrars, not to you.
Published services
rdap.nic.lacaixa · whois.nic.lacaixaWhat the registry itself tells IANA it runs. They agree with what ds asks.
Name servers
anycast10.irondns.netanycast23.irondns.netanycast24.irondns.netanycast9.irondns.netThe 4 authoritative servers for the .lacaixa zone — what the root delegates to. Nothing ds queries 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.

  • generic IANA Root Zone Database types it "generic"
  • new-gtld ICANN delegated it on or after 2013-10-23, when the 2013 round opened — see delegated

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 .lacaixa was delegated to; this is what the root actually answers with when a resolver asks it where .lacaixa lives.

Delegated to
  • anycast9.irondns.net195.253.64.112a01:5b0:4::b
  • anycast10.irondns.net195.253.64.122a01:5b0:4::c
  • anycast23.irondns.net195.253.65.112a01:5b0:5::b
  • anycast24.irondns.net195.253.65.122a01:5b0:5::c
The 4 name servers the root hands out for .lacaixa, with the glue addresses that come with them — every one of them answers over IPv6. None of this is what ds queries: these servers know which names exist, not who registered them.
DNSSEC
Signed — 1 DS record in the root
  • key 36309RSA/SHA-512 · SHA-2561472BAB3DDF6CA893B478BB871E9C9A21C0E01D468C9A9117771E29BCC93D1B9
Each one is a fingerprint of .lacaixa's own signing key, published by the root and signed with the root's key — which is how a resolver that trusts only one key can prove an answer under .lacaixa came from its registry and was not tampered with in transit. It says nothing about who owns a name or whether one is free.

Ask the root yourself — no registry involved, and the same records this section was built from: dig +norec @a.root-servers.net lacaixa. NS and dig +norec @a.root-servers.net lacaixa. DS.