SOURCE_URL: https://majikah.solutions/products/majik-slink/docs/slink-getting-started --- title: "Getting Started with Majik SLink" id: "slink-getting-started" group: "majik-slink" type: "products" version: "0.0.2" lastUpdated: "2026-08-07T00:00:00.000Z" difficulty: "Beginner" time: "3–5 minutes" tags: [getting-started, slink, url, ownership, attribution, reference, attestation, signing, muid, beginner, onboarding, post-quantum] --- # Getting Started with Majik SLink > What Majik SLink is, the three kinds of claims it supports, and what you need before publishing your first one ## Overview Majik SLink lets you cryptographically bind your Majik Universal ID to a public URL — proving you own the domain, control the content, or simply want to attest a connection to it — by publishing a signed, publicly verifiable record. ### What is a Majik SLink? A Majik SLink is a signed, publicly verifiable record linking your Majik Universal ID to a public URL — a YouTube channel, a social profile, a personal website, a repo, or any publicly accessible page. Every SLink is one of three claim types, depending on how you actually relate to the URL: Ownership (you control the domain), Attribution (you control the content but not the domain), or Reference (neither — a plain signed attestation). Ownership and Attribution claims are independently checkable; Reference claims are not, and are always shown to others as an attestation rather than a verification. Whichever type you pick, your Majik Key signs the canonical URL using hybrid Ed25519 + ML-DSA-87 cryptography, and the resulting record is published to the Majikah registry and linked from your public MUID profile. > **NOTE:** Creating SLinks requires a registered Majikah account and an active Majik Universal ID. If you don't have one yet, Majik Signature will walk you through creating it right inside the Sign a Link panel — no separate trip required. Your MUID doesn't need to be fully verified to sign a SLink, but a verified MUID carries more weight with anyone checking your claim. ### Where to Find It Open Majik Signature and go to the Sign a Link panel — it defaults to Sign mode, which is what you'll use to create a SLink. The same panel has a Verify mode for checking who has signed a URL, and a My SLinks button for managing everything you've already published. ### The Three Claim Types | Claim type | Use it when… | Proven by | | --- | --- | --- | | Ownership | You control the domain itself. | A DNS TXT record — strongest, independent of any single page. | | Attribution | You control the content at this URL, but not the domain (a channel, profile, or repo). | A short code embedded on the page. | | Reference | You control neither, but want to sign a statement about the URL anyway. | Nothing — recorded as a signed attestation only. | *Caption: You'll pick one of these for every URL you sign — see the Signing and Publishing a SLink guide for full detail.* ### The Challenge-Response Model (Ownership & Attribution) Ownership and Attribution claims use a challenge-response flow to prove your claim without ever needing Majikah to have access to your account or domain. Majik Signature derives a short, deterministic code (prefixed majik-slink:) from the URL — the same URL always produces the same code. You publish that code either in your domain's DNS (Ownership) or somewhere visible on the page itself (Attribution). Majik Signature then checks for it — a DNS lookup for Ownership, or a page scrape for Attribution — and once found, finalizes and publishes the signed record. > **NOTE:** Reference claims skip this step entirely. There's no code to publish anywhere — you sign the attestation directly, and it's recorded immediately. ### Prerequisites - Majikah Account — Register at majikah.solutions if you don't have one. - Majik Universal ID — Create one inline the first time you open Sign a Link, or ahead of time at id.majikah.solutions/id. See Getting Started with Majik Universal ID if needed. - The public URL you want to sign — it must be reachable over https:// without a login. - For Ownership claims: access to that domain's DNS settings, to add a TXT record. - For Attribution claims: edit access to the page itself (bio, description, README, or page content), so you can paste a short code somewhere on it. - For Reference claims: nothing further — no page or DNS access needed at all. ### Platform Compatibility | Platform | Where to Paste | | --- | --- | | YouTube | Video description or channel About section | | X / Twitter | Profile bio or a pinned post | | Instagram | Profile bio | | Everything else — GitHub, TikTok, personal websites, blogs, etc. | Anywhere visible in the page's content | *Caption: Where the challenge code goes for Attribution claims. Ownership claims always use a DNS TXT record instead, regardless of platform.* > **NOTE:** Once your SLink is verified and published, you can safely remove the challenge code from your page or DNS records. It was only needed for that one verification step and serves no purpose afterward. ### Next Steps Ready to publish your first SLink? See Signing and Publishing a SLink for the full step-by-step walkthrough. To check whether a URL has already been signed by someone else, see Searching & Verifying a SLink — no account required for that part.