Verify Nostr NIP-05 with Your Own Domain

To verify your Nostr identity using your own domain, create a file at ./well-known/nostr.json on your website. The content should look like this:

{
  "names": {
    "joomaen": "77c2969ea4db4ca1859305d7ebabf6053fd132ddcc88e1b178bfd938a33cfa50"
  },
  "relays": {
    "77c2969ea4db4ca1859305d7ebabf6053fd132ddcc88e1b178bfd938a33cfa50": [ "wss://nostr.235421.xyz" ]
  }
}

Replace joomaen with your desired name — this will appear before the @ sign, like [email protected]. The value after the name is your public key in hexadecimal format, not the npubxxx version. You can use the Damus key tool to convert your key.

If you prefer to display only your domain (e.g., @joomaen.com), you can set the name as _. Like this:

{
  "names": {
    "_": "77c2969ea4db4ca1859305d7ebabf6053fd132ddcc88e1b178bfd938a33cfa50"
  },
  "relays": {
    "77c2969ea4db4ca1859305d7ebabf6053fd132ddcc88e1b178bfd938a33cfa50": [ "wss://nostr.235421.xyz" ]
  }
}

The relays section is optional. It maps your hexadecimal public key to one or more relays where others can find you. It helps clients discover your activity but is not required for NIP-05 verification.

You can deploy this using any static site setup, as long as the directory structure is correct. The file must be accessible via:

https://yourdomain.com/.well-known/nostr.json

For example: https://joomaen.com/.well-known/nostr.json (replace with your actual domain).

If you don't have a server, you can host it using GitHub Pages. Simply fork this repository: NIP-05-Verification, and follow the instructions in the README.md — it's similar to deploying a static blog on GitHub Pages.

Once your file is live, update the "Nostr Address" or "Username" (may also be labeled as "NIP-05") in your Nostr client. If you used _ as the name, make sure to enter the full address like [email protected]. The change may take a few minutes to propagate.