dns.vm.bd

The free names this cloud hands out, the browser that opens them, and the resolver that answers them.

What the free names are

Route 53 Domains in this cloud registers names under the 413 top-level domains Route 53 itself sells -- .com, .net, .org and the rest of its list -- for nothing. They are not in the public DNS. They resolve only for a browser that asks dns.vm.bd, and for every other they do not exist, or belong to whoever really owns them. If a name is registered for real elsewhere, the real owner's answer wins here too, within about half a minute.

The browser for the free names

The free names open in one browser made for them: Mozilla's own Firefox, as Mozilla makes it, run apart from any browser you already have, on a profile of its own. Everything for the free names is inside it and nowhere else:

Linuxfree-names-browser.deb (9 KB). SHA-256 51e2453c8bbea3235fd8f7b39032349d621a24e7f7c0bbb5e8cff82b4f798109.
Install: double-click the file and press Install in your software installer, or run sudo apt install ./free-names-browser.deb. It asks for your password, as any package does, and your system may say the package is from outside its repositories; that is expected. Then open Free names browser from your menu. The first time you open it, it takes Firefox from Mozilla for you, which takes about a minute.
Remove: remove Free names browser in your software installer, or run sudo apt remove free-names-browser. That takes every user's Firefox and profile for it away too.
macOSfree-names-browser.pkg (9 KB). SHA-256 7f3d9b4eafb5bebb0d6667038076570f77109d38935c51cc2a82ac1d0a29b06c.
Install: double-click the file. macOS says it cannot check it for malicious software, because it is not signed; press Done. Open System Settings, then Privacy & Security, scroll to the message about free-names-browser.pkg and press Open Anyway, then Open, and enter your password. This is needed once. The installer puts Firefox and its profile in your home folder, and Free names browser in the Applications folder inside it.
Remove: open Uninstall free names browser in the same Applications folder in your home folder.
Windowsfree-names-browser.msi (20 KB). SHA-256 68606197b4e607be0950e58c90aa0eaf45e824e86389dd835fb6c1f82ac17dae.
Install: double-click the file. Windows says Windows protected your PC, because the package is not signed; press More info, then Run anyway. This is needed once. It installs for your account only and needs no administrator. Then open Free names browser from the Start menu.
Remove: Settings, Apps, Installed apps, Free names browser, Uninstall. That takes Firefox, its profile and the Start menu entry away.

The packages are not signed: signing costs money and the free names are free, so macOS and Windows each warn once, as above. That makes the checksum the way to know a file is the one this page offers: check the SHA-256 of what you downloaded against the one above before you open it (sha256sum on Linux, shasum -a 256 on a Mac, Get-FileHash in PowerShell on Windows). Each package takes Firefox from Mozilla and checks it against the SHA-256 Mozilla publishes beside it before it installs anything (the Windows one also checks that it is signed by Mozilla Corporation). Firefox and its profile live in your own folders, never in the computer's, and nothing the packages do is done as the whole computer's administrator.

What you take on by using it. The root's key is kept in this platform's private repository. Anyone who gets a copy of the repository can impersonate any site under any of the 413 top-level domains Route 53 sells (.com, .org, .dev, .uk and the rest) to this browser, until you uninstall it. The root carries X.509 name constraints so that it is trusted for those top-level domains only and for no address. That limits the harm and does not remove it, because gmail.com is under .com. Nothing here is a promise that the key cannot leak. A new root means a new package of this browser, and this page says so when it happens. So do not use this browser for anything but the free names.

The root's SHA-256 fingerprint is 2D:4A:97:CD:93:CD:32:7C:7E:16:1B:2D:AC:3E:34:83:5C:67:84:42:44:B2:9A:71:6F:2B:17:11:ED:42:5C:95, valid from 2026-10-18 to 2028-10-17.

Phones and tablets

Phones and tablets are not offered yet.

Read this before you use it

If this resolver cannot be reached, the free names browser loses all name resolution, not only the free names. It does not fall back to your network's own DNS, because a name that falls back would stop being a free name without saying so. The sign is that every site fails at once in that browser; any other browser is unaffected. Uninstall it, or use another browser for everything else.

Your network's family decides which server you depend on. dns.vm.bd has an IPv4 address in brilliant and an IPv6 address in dhanmondi-west-1, each answering by itself. A network that offers you only IPv4 depends on brilliant alone, and one that offers only IPv6 on dhanmondi-west-1 alone. If yours offers both, either may be used.

This resolver sees every name you look up in that browser, not only the free ones, as any DNS provider you choose does. It keeps no record of who asked: it writes no query log, holds no list of addresses, and the servers' logs do not contain yours. A source is counted in memory for a few seconds so that no one source can use it all, and that count is never written anywhere.

A free name serves HTTPS when you have asked ACM in this cloud for a certificate for it; the certificate is signed under the platform's root, which only this browser trusts. Until then it serves plain http:// only, and the browser says so. A few top-level domains, among them .app, .dev, .page, make every browser insist on HTTPS, so a name under one opens only once it has such a certificate.

What was tried, and what was not

Tried against this resolverDNS over TLS and DNS over HTTPS, answered with a verified certificate for dns.vm.bd: a real name is answered and a name nobody holds is denied. The rate limit and the cap on connections from one address, and that no log names the asker's address, are proved from outside before this page is published.
Tried: the browserMozilla Firefox 158.0 on Linux, 2026-10-18, taken from Mozilla and unchanged, on the profile this browser carries: it loaded 3 free names, every one resolved through the resolver, and refused a certificate for a name under a top-level domain that is not on offer, one for an address, and one for a name it was not made for. Another profile of the same Firefox, asking the same resolver and without the root, refused a certificate the root had signed.
Tried: the packagesEach was built twice, in different directories, time zones and seconds, and was the same bytes both times; and each was read back by a tool that is not ours (dpkg-deb, libarchive, Microsoft's package tables through msitools). The Linux package's program was run in a home directory with a stand-in for Mozilla's server: it refused a download that was not what Mozilla publishes, installed Mozilla's files unchanged, and left the home directory exactly as it was after the removal. The macOS package's script was run with stand-ins for macOS's own tools, and the Windows package's tables and script were read. No package has been opened by a real Mac, a real Windows computer or a Linux desktop's software installer.
Not tried yetThe packages on a real Mac, a real Windows computer and a Linux software installer, and the warnings above, which are what Apple and Microsoft document and not something seen here. The browser on macOS and on Windows: the measurement above is Firefox for Linux. Firefox updating itself in the folder the packages use is how Mozilla documents it, not something measured here.

This is a free service of an unaffiliated platform. It can be stopped, and when it is, uninstall the browser.