Mozilla's browserid.org server is used for two things, currently: - validating the signed authentication token you get back from calling the authentication fun

Mozilla's browserid.org server is used for two things, currently: - validating the signed authentication token you get back from calling the authentication function. As user "decentralized" points out, this is just a convenience; your service can do this itself if you don't mind getting your hands dirty with crypto code. - Serving the JS shim for user-agents that don't implement navigator.id.getVerifiedEmail() natively. Once browsers implement this function themselves, and webmail systems can tell the browser that the user owns a particular email address, this won't be needed either.