A .si RDAP 404 does not guarantee that you can register the name. It means the registry did not find the domain as entered. Real availability requires a policy check, a current registrar result and a completed registration.
A 404 is not a purchase invitation
A .si RDAP 404 means the registry did not find the domain name as entered. Register.si says this usually means the name is not registered, but it explicitly warns that a 404 does not always mean the name can be registered. Treat it as a registry signal, not a reservation or shopping-cart hold.
Register.si’s RDAP service is the structured successor to WHOIS. A domain query follows the documented format, such as the registry’s `/domain/` endpoint, and can be made with GET. A HEAD request is useful when you need the HTTP status without the registration-data body, but neither request registers the name.
Why might an absent record still be blocked? The name may fail syntax rules, appear on a reserved list or be rejected under the registry’s terms. That is why “not found” and “registerable” are different conclusions.
What 200, 400 and 429 mean
A 200 response is not the positive mirror image of a 404. Register.si defines 200 OK as meaning that the domain is registered and/or cannot be registered at that time. In other words, it is evidence against treating the name as freely available, but the returned object and the registrar’s result still matter.
A 400 means the request is invalid—for example, because of prohibited characters or the wrong top-level domain. A 401 concerns incorrect username or password in the relevant authenticated request, while Register.si says the domain itself is registered and anonymous-level data may still be returned. A 429 means access has been temporarily restricted because too many requests were made.
The practical rule is simple: do not turn an error into an availability label. Validate the spelling and suffix after a 400, check credentials after a 401, and wait before retrying a 429. An automated checker should report these as request or access outcomes, not as “free” or “taken.”
No DNS does not mean no owner
DNS and registration answer different questions. DNS asks whether the name is delegated and resolving. RDAP and WHOIS concern registry records. A registered .si domain can be inactive because no name servers have been associated with it, so it will not resolve.
The same applies to a domain on client hold or server hold: Register.si says those statuses keep the name out of DNS. A failed DNS query, blank browser page or missing website may therefore describe configuration or status—not availability. Use RDAP or WHOIS to investigate registration, then use a registrar for the purchase decision.
The route from idea to registration
Start by checking the name’s construction. Current .si registry guidance and the General Terms say a name must contain allowed characters, run from two to 63 characters with the IDN minimum measured in displayed characters and maximum in its ACE representation, and not begin or end with a hyphen. Consecutive hyphens in the third and fourth positions are also restricted, subject to the IDN exception in the General Terms.
Then check the current reserved-name material. The published list includes 112.si, 113.si, rs.si, si.si and three Xerox-related names. These are concrete reminders that a technically valid string can still be unavailable under registry policy.
Next, use RDAP as a registry signal and search the name with a current .si registrar. Register.si describes registrars as agents between end users and the registry and publishes an official directory. A registrar may also apply provider-specific account, payment, tax, pricing or eligibility conditions, so a public 404 is not the same thing as an orderable result.
Finally, separate checkout from confirmation. A payment receipt or pending order is not proof that the registry completed registration. Check the registrar’s explicit completed-registration status and the resulting domain record. Availability can change between a lookup and completion.
One final distinction matters for founders and creators: a registry or registrar check is not trademark clearance. The .si General Terms require applications to be made in good faith and not to encroach on third-party rights, but a domain lookup cannot decide whether your proposed name conflicts with a trademark, company name or other protected right.
The honest answer for DomainBite suggestions
DomainBite generates naming suggestions locally and checks registry status only when you request a live check. It does not reserve names, take registration payments or operate a Hostinger account integration. An unchecked suggestion is only an idea. Even a not-found result needs registrar and policy checks before purchase.
The shortest useful rule is this: RDAP can tell you that a name is registered or not found; the registrar tells you whether it can currently be ordered; and the registrar’s completed-registration status tells you whether the transaction actually succeeded.
What each check actually tells you
| Check | Question answered | What it cannot prove |
|---|---|---|
| DNS | Does the name have delegation or records that resolve? | Whether the domain is available to register |
| WHOIS or RDAP | What registration status does the registry return? | Whether a registrar will accept your order |
| Registrar search | Does this provider currently offer the name? | That it will remain available until registration completes |
| Checkout and account status | Did the registrar accept and complete the transaction? | That a payment page or pending order created a registration |
A few good questions.
Does a 404 from .si RDAP mean I can register the name?
No. It means the entered name was not found and usually indicates that it is not registered. Register.si expressly says that a 404 does not always mean the name can be registered. Check syntax, reserved names, registry policy and a current registrar result.
What does a 200 response tell me?
For .si, Register.si defines 200 as meaning the domain is registered and/or cannot be registered at that time. It is not a simple availability tick; inspect the response and confirm the position with a registrar.
Why can a domain have no DNS records but still be registered?
Registration and DNS are separate systems. A domain may be inactive, lack name-server delegation or be on client or server hold, so it does not resolve even though the registry records it.
What should I do after a 400, 401 or 429 response?
After a 400, check the query format, characters and TLD. After a 401, review authentication. After a 429, wait before retrying. None of these responses proves that the name is available.
Does reaching checkout guarantee the domain is mine?
No. A payment page, receipt or pending order may not mean registration completed. Look for the registrar’s explicit successful-registration response and the domain’s registered status in your account.
Sources, not assumptions.
Evidence cutoff: 2026-10-06. Prices, policies and domain status can change.
- Register.si — RDAP response meanings ↗
- Register.si — Domain statuses ↗
- Register.si — General Terms (effective 15 November 2024) ↗
- Register.si — Reserved names ↗
What would change this?
- Changes to Register.si RDAP response meanings or access restrictions.
- New reserved names or a changed registrar registration-confirmation process.
Independent information, not legal or investment advice. Domain status and prices can change; confirm registry rules and registrar checkout terms before buying.