.barclaycard is a brand namespace; registrations are limited to its registry operator and qualifying affiliates or licensees
| Service | Address | Record state |
|---|---|---|
| rdap | https://rdap.identitydigital.services/rdap/ | current |
| website | http://www.barclaycard.com/ | current |
| whois | whois.nic.barclaycard | current |
| Nameserver | IPv4 | IPv6 | Address evidence |
|---|---|---|---|
| a0.nic.barclaycard | 65.22.120.9 | 2a01:8840:76::9 | Published addresses |
| a2.nic.barclaycard | 65.22.123.9 | 2a01:8840:79::9 | Published addresses |
| b0.nic.barclaycard | 65.22.121.9 | 2a01:8840:77::9 | Published addresses |
| c0.nic.barclaycard | 65.22.122.9 | 2a01:8840:78::9 | Published addresses |
.barclaycard is a brand namespace; registrations are limited to its registry operator and qualifying affiliates or licensees. The comparison may still show observed renewal or transfer information for existing names.
Yes. The root delegation for .barclaycard has a published DS record. That is not evidence that a registrar can submit DS records for an individual domain.
The registry record currently does not establish every policy or syntax field for .barclaycard. Missing evidence is shown as unknown rather than treated as permission, a restriction, or a DNSSEC capability.