Why three formats instead of one
An <iframe> only works where the destination actually renders raw HTML. Most Markdown renderers — GitHub READMEs, GitHub issues and PRs, most wiki and docs platforms — strip iframes outright for security reasons, so an iframe snippet pasted into a GitHub issue simply won't render. In those places a plain link that opens the real player is the correct output, which is why this tool also generates a Markdown link and a bare HTML link alongside the iframe.
What the validation actually checks
The parser accepts a bare public id or a full clipy.online watch URL. It rejects a different domain outright, including lookalikes (a domain that merely contains "clipy.online" as a substring) and Clipy's own CDN subdomain, and it rejects a clipy.online URL that isn't actually a watch page. That way the embed code this tool generates always points at something real.
Sister tools
Need to share a one-off file instead of a recording? Share a file gets you a public link for up to 2 GB. If you're looking to record the thing you want to embed in the first place, Clipy gives you an instant, embeddable share link the moment you stop recording — no watermark, no signup wall for viewers.