Skip to contentVerifycate
NewBrand · VerificationNo. 032

Put certificate pages on your own domain

Serve recipient-facing certificate pages from a domain you control, instead of a Verifycate subdomain. Available on Pro.

By Ashwin Shenoy · Founder and engineer

The last visible trace of another platform is often the address bar.

On Pro, certificate pages can use a domain you control. Point a domain or subdomain at Verifycate, add the DNS records, and verify it from workspace settings. The portal and public certificate pages then load from your address instead of a Verifycate subdomain.

The domain sits alongside the portal logo, colours, and cover image. It changes the address, not the verification model: the certificate is still checked against the same signed credential and public record. For a university department or a training provider, the link becomes part of the programme's identity rather than a redirect to someone else's.

Related

← Back to all updates

Start issuing

Certificates people can prove.

Design once, issue in bulk or from your LMS, and give every recipient a public page anyone can verify.