Enter Denmark market with a .CO.DK Domain

A private operator, not the official Danish registry. co.dk is a domain name registered inside .dk on 31 January 1997; the third-level names beneath it are sold by a company trading as Dansk.Net, which presents itself on its contact page as Digital Solutions 365 AB, based in Sweden. The same operator also offers .biz.dk, .firm.dk, .store.dk and .reg.dk. The distinction is not cosmetic: your rules come from the operator's own business terms rather than from an act of parliament, and your counterparty is the company those terms call the Administrator.

They point at the same country but are entirely separate regimes. .dk is Denmark's official country extension: a registry appointed by public tender administers it, a statute frames the rules, registrant identity is verified and registration data is published. .co.dk is a namespace at the third level opened by a private operator: there is no identity check, no data is published, and the rules come from a private contract. Technically both resolve and behave normally; the difference is concentrated in the legal framework and in who you are dealing with.

No. The operator's terms impose no requirement of nationality, residence or commercial status on the registrant, and the site describes its audience simply as companies and private individuals. You need no Danish address, local representative or trustee service. Unlike the official country extension, no identity check is asked of you either: there is no step after checkout where documents or an electronic ID are demanded. In exchange, the contract places full responsibility for the choice and the spelling of the name, including the extension you pick, on you.

No, and the contract says so in as many words. Holding a name under .com or directly under .dk gives you no priority at all when acquiring the same name from this operator; registrations follow the first-come, first-served principle. The same clause explains why the namespace exists: the names were created to give a fresh opportunity to the several parties who may hold rights in one and the same name under the class system of trademark law. The practical consequence is that owning your brand in .dk does not reserve the .co.dk equivalent, so register it separately and early.

No. There is no published public lookup for third-level .co.dk names; the Danish registry's whois server knows only the co.dk domain name itself and does not recognise the names beneath it. The operator's terms mention that it keeps a database but do not publish an access route. That cuts both ways: your data is not published by law as it is in the official country extension, but in a dispute the other side equally cannot identify you from a public record. You can try a name's technical status on the whois search page.

In court. The business terms state it plainly: the Administrator does not intend to act as judge in domain name disputes and refers the user to the ordinary courts and to national and international arbitration bodies. The same text says the Administrator has no authority to take a domain name away from a user, so an objection must be directed at the person who registered the name. Disputes are decided under Danish law, with the Maritime and Commercial Court in Copenhagen as the first-instance venue. The terms do list bad-faith and legitimate-interest criteria in detail, but no panel exists to apply them.

No. The business terms record it directly: acquiring a domain name is treated as a commercial acquisition and investment rather than a consumer purchase. The practical consequence is that the right of withdrawal you might expect from consumer legislation does not arise here. The text also keeps refunds narrow: the Administrator is not answerable for a name you misspelled or ordered under the wrong extension, and any decision on a refund rests with the Administrator alone. Fees are refunded only where the Administrator itself cancels a registration made in error. Checking the name letter by letter before you confirm really does matter.