Privacy Policy
Effective 6 October 2026
The short version
You type domain names. Our server asks the registry of each name and shows you the answer as it came back.
There are no accounts, no cookies, no advertising, and no analytics or trackers. The pages load nothing from other companies: the fonts and scripts are served by this site.
We do not store who asked about which name. To count the lookup allowance we keep a salted hash of your network address for about 48 hours. Unless you write to us, we keep nothing else about you.
The site is operated by DomainHunter.si.
What we collect
Names you check: the name, the registry’s answer (state, detail, dates, status values, the number of name servers), the time of the check and the registry address that was asked. We store this so the same question is not sent to the registry again too soon. Nothing about you is stored with it.
Lookup allowance: each fresh lookup adds one row with a salted SHA-256 hash of your network address and the time. The address itself is never written to our database. For an IPv6 address only the network part, the first 64 bits, goes into the hash.
Server logs: the web server of the hosting provider may keep its own request logs. We do not control those. Our own error log records what failed and when. It holds no visitor addresses.
Contact form: if you write to us, we store your message, your e-mail address, your name if you gave one, the time, and the same salted hash of your network address. The message is also sent to the operator by e-mail. We ask for the address so we can reply.
The form also carries a hidden time stamp, used only to tell a person from a script. We accept at most 3 messages an hour and 8 a day from one network address, counted with the salted hash.
Nowhere else on the public pages is there a field for a name or an e-mail address, and nowhere at all for payment details.
Where your names go
Each name is sent from our server to the registry of its ending over RDAP, the registries’ public lookup service: Register.si for .si, Verisign for .com and .net, and for other endings the service listed for them in the IANA RDAP bootstrap file.
The registry sees our server, not you. Your network address is not passed on.
The registry does learn that someone asked about the name, and we have no say in what a registry logs. If a name idea is confidential, keep that in mind before you check it anywhere.
The drop radar
The radar follows a fixed list of .si names that we maintain. Checking a name does not add it to the radar.
If a name you check is already on that list, the fresh answer updates its entry on the radar. Nothing about you is attached to it.
Stored answers are shared. A visitor who checks the same name shortly after you gets the stored answer, with the time the registry was asked. That shows that somebody checked the name. It does not show who.
How long we keep it
Allowance rows are deleted once they are older than 48 hours.
A stored answer is reused for between 5 minutes and 24 hours, depending on the state, and for 7 days when the ending cannot be checked at all. The exact times are on the How it works page. Stored answers are deleted after 30 days, unless the name is on the radar’s list.
The radar’s record of state changes is kept for 180 days.
Messages sent through the contact form are deleted after 180 days.
The clean-up runs with the radar’s regular job, so a row can outlive its limit by the time until the next run.
Your rights and choices
There is no account, so there is no profile to export, correct or delete. The allowance rows expire on their own, and we cannot tell which stored answers came from your checks.
A message you sent through the contact form is the one record that carries your e-mail address. It is deleted after 180 days.
If you are in the EU, the GDPR gives you rights to access, correct, delete, restrict and object to the processing of your personal data, and the right to complain to your data-protection authority.
To use these rights, or to raise a concern, write to us through the Get in touch page.
How we protect it
Traffic is encrypted in transit (HTTPS). The database cannot be reached from the web. The pages run scripts from this site only.
No online service can promise perfect security. What we can do is keep little: we store no visitor data beyond what this page lists.
Changes to this policy
This page changes when the site does. When it changes, the effective date at the top moves.