**Imaginary dialogue: Me and my NIP-05 provider**

Raw JSON

{
  "kind": 1,
  "id": "3594fcbffa530d1061830d52b237ce3ade45c6a0a7ff4366b26850cbc47fb56e",
  "pubkey": "841b017d49f8211881a23acbd002bfb07c0d9c0d720c4a99c42669458bf0ee39",
  "created_at": 1775559082,
  "tags": [],
  "content": "**Imaginary dialogue: Me and my NIP-05 provider**\n\n**Me:** Hey, my NIP-05 is crossed out again. I followed all instructions. Why?\n\n**NIP-05 Provider (with a tired server voice):** Because you put `\"nip05\": \"[email protected]\"` but the `.well-known/nostr.json` file won't open. You forgot CORS headers, or maybe you used Cloudflare and it blocked the MIME type.\n\n**Me:** But I copied the JSON from GitHub!\n\n**Provider:** Yes, but you saved it with a `.html` extension by mistake. And then you have a broken HTTP → HTTPS redirect. Nostr client sees ` http://`, but you only have ` https://`. Crossed out.\n\n**Me:** So NIP-05 is useless?\n\n**Provider:** It's meant to make you look “verified” in clients. But if the provider is unreliable, your checkmark becomes a cross. Real verification is the Web of Trust, not a JSON file.\n\n**Me:** What should I do?\n\n**Provider:** Either use a stable provider like `nostrcheck.me` or `nostplebs.com`, or give up on the checkmark and just use your public key. NIP-05 is a crutch, not legs.\n\n**Me:** And crossed-out addresses?\n\n**Provider:** They mean the client tried to resolve your NIP-05, got a 404 or 500 error, and tagged you as “unreliable.” But it's not you: it's your hosting that sucks.\n\n**Me:** Thanks, I'll switch to a free provider that works.\n\n**Provider:** Remember: free often means crossed out after two weeks. Either learn to run a web server, or accept being an anonymous npub. No shame.\n\n**Moral:** NIP-05 is like a tie at a wedding: nice if straight, embarrassing if crooked.",
  "sig": "aa7b5e98ea52399dc9963c5154e1f7c951a64fcae7661302c9909d6b1892dea58a94a8e2f0340c45d442757aee7a0e149c29ea276a2f176a49acb158fdb2462e"
}