Raw Record Source

{
  "$type": "site.standard.document",
  "canonicalUrl": "https://standard.site/docs/verification",
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreifn7hebxiin5xc7vyxwqwvmwoivtfbrdj33uzpuo472qbrwouvk4a"
    },
    "mimeType": "image/png",
    "size": 107550
  },
  "description": "Understanding how Standard.site records are verified to avoid impersonation or spam..",
  "path": "/docs/verification",
  "publishedAt": "2026-02-10T00:00:00.000Z",
  "site": "at://did:plc:re3ebnp5v7ffagz6rb6xfei4/site.standard.publication/3me5vykp6lf2y",
  "textContent": "import { StandardSite } from '@/app/components/docs'\n\nVerification\n\nSince <StandardSite /> records reference domains and web pages, a verifiable way for these resources to point back to their corresponding records is needed.\n\nOverview\n\nVerification is accomplished using a .well-known endpoint for publications, and an HTML <link> tag for documents.\n\nWhen an application needs to verify a record, it fetches the appropriate verification endpoint and checks that the returned value matches the record's AT-URI.\n\nA <StandardSite /> record should only be considered \"valid\" if the author of the material provides an accurate verification endpoint pointing to the record.\n\nPublication Verification\n\nTo verify a publication, add a .well-known endpoint to the domain:\n\nThe endpoint should return the AT-URI of the publication record:\n\nNon-root Publications\n\nIf the publication does not live at the domain root, append the publication path to the endpoint:\n\nDocument Verification\n\nTo verify an individual document, include a <link> tag in the document's <head> that references its AT-URI.\n\nHTML Example\n\nThis confirms the association between the rendered document and its site.standard.document record.\n\nVerification Flow\n\n1. An application discovers a <StandardSite /> record\n2. The record contains a url (for publications) or site + path (for documents)\n3. The application fetches the verification endpoint from that URL\n4. The application checks if the returned AT-URI matches the record\n5. If they match, the record is verified\n\nBest Practices\n\n- Always implement verification for production records\n- Use HTTPS for all publication and document URLs\n- Keep AT-URIs consistent across records and verification endpoints\n- Update verification endpoints when migrating records to a new DID\n\nRelated\n\n- Publication lexicon - Understanding publication records\n- Document lexicon - Understanding document records\n- Quick Start - Implementation guide",
  "title": "Verification"
}