Buy .1.bg Domain Name

It is a real, official zone. Article 1.2 of the Terms and Conditions lists the «Available Zones» and writes out all 36 sub-zones from a.bg to z.bg and 0.bg to 9.bg one by one, stating that all of them are functionally equal; the registry's own order step offers the same 36 zones in a dropdown. One detail can mislead: querying the registry whois for «1.bg» returns «invalid» — because a single-character label is not valid, which is precisely the point. 1.bg is not a domain name, it is a zone.

No. Article 2.3.5 is explicit: in the second level zones no grounds are required to use the label. On the top level, by contrast, the registrant must choose between a protected and an unprotected registration, and a protected one means documenting one of the fourteen grounds in article 5.5.1. The same article grants a further privilege: names registered in the sub-zones cannot be disputed by the registry. For an applicant who cannot produce a rights document, that is a direct advantage.

The eligibility rules apply in the sub-zones exactly as they do at the top level; section 3 makes no distinction between zones. Article 3.1 lists those with a registration in Bulgaria or in an EU member state, and opens a route for companies registered abroad through a registered branch or commercial representative office in Bulgaria. Article 3.3 adds that a legal entity registered abroad may authorise an entity meeting those criteria to register for it; that route needs a notarised power of attorney in original.

Yes — identity documents are mandatory in the sub-zones too. Article 4.1 requires them for «all Available Zones», and the heading of Appendix 1 spells out the scope: «in the .bg zone and the sub-zones». There is a practical shortcut: if you use a qualified digital signature, the signature alone is sufficient. The only thing not asked for is a grounds document for the label — that applies to the top level only, and even there it is optional.

Yes, but indirectly. 1.bg has no DS record of its own because it is not a separate delegation: a measurement on 12 August 2026 found no separate SOA or NS record for the zone, and names are served from inside the .bg zone. Because the parent zone is signed, names beneath it are part of the chain; in the same measurement a sub-zone name resolved with a validated answer. You do not need to set up a separate DNSSEC chain — the protection comes from the parent.

The chain matches the top level, and its first step is harsher than expected. Article 9.3.1 grants 30 calendar days to pay after the support period ends, but article 9.3.1.1 states that support is suspended if payment is not received within 7 days — so your site and email go down after one week. The registration itself only terminates on day 40, when the name becomes available to others. Plan your renewal reminder around that first week, not around the expiry date.