Event JSON
{
"id": "00001d90e13b38e0d2c401e9916d482c126212a203fcc9cebf317c397997ae3b",
"pubkey": "7bdef7be22dd8e59f4600e044aa53a1cf975a9dc7d27df5833bc77db784a5805",
"created_at": 1743173147,
"kind": 1,
"tags": [
[
"p",
"17538dc2a62769d09443f18c37cbe358fab5bbf981173542aa7c5ff171ed77c4"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"e",
"417dc1ae1427f8673a8434f39f0729e73ff2b03d5ce0f86c30f11d166d58c5ce",
"wss://wot.dtonon.com/",
"root"
],
[
"e",
"6f281bbf4fdde3a3d05284555d53dc4738b68313b52d3aead3f5de0594ac80e3",
"wss://wot.utxo.one/",
"reply",
"17538dc2a62769d09443f18c37cbe358fab5bbf981173542aa7c5ff171ed77c4"
],
[
"nonce",
"11068046444225753925",
"18"
]
],
"content": "https://github.com/nostr-protocol/nips/blob/master/05.md explains a lot of things.\n\nApart from the fact that the specific case is formally invalid, since it is not an address (user@domain.com), to check whether a NIP-05 is valid, it is necessary to retrieve some data from an endpoint and check whether the npub matches.\n\nNostr applications do not suffer in any way from an invalid NIP-05; it should be considered by the user as a red flag since it is often (but not always) related to impersonation. ",
"sig": "fa9f7c1cd70c7d1cc464c7f01f4056136ffc3ab7d33429eb0634cd9d0dad1fefb299188fd168e22bc87afd2d80bb9ba462587f3b115e85a5313dab1eb2599551"
}