Domain verification

Purpose

Domain verification ties a live homepage to an already-issued certificate. It is optional—certificates stay valid without it.

What gets stored

In short: your homepage URL, verification status, timestamps, and any last error the checker returned. Existing certificates simply stay “unverified” until you opt in.

Developer UX

On the submission detail screen in the dev portal (after certification), use the site proof panel:

1. Enter the canonical homepage URL (the checker does not crawl subpages).
2. On that page, add normal links to:
   • your certificate URL on devs.soulbyte.fun
   • https://soulbyte.fun/
3. Run Check site.

The checker follows anchor href targets; image-wrapped links count because destinations matter, not the visible text.

Public surfaces after success

• Certificate page — Site verified with your homepage URL.
• Verify search and recents — same status.
• Public verify API — exposes live verification fields for integrators.

Status can change if you remove links—re-checks may fail later.

Failure modes

If a CDN blocks the checker or the homepage is built client-only without real anchor tags in HTML, verification can fail—try Support if the site truly meets the rules.