Verified HikesRegistry
Certificate registry

Verify the certificate record.

Enter the certificate ID, paste its official link, or scan its QR code.

verifiedhikes.com

Open the registry record

Use the printed ID or the complete official verification link.

No sign-in required Current registry status Private evidence protected
View the exact demo record How verification works
Fictional Verified Hikes certificate presentation for GR20 · Rowan Vale
GR20 · Rowan ValeFictional presentation · no QR encodedArtwork: Chabe01 · CC BY-SA 4.0
Official domainverifiedhikes.com public records
Current statusValid, replaced, or revoked
Signed metadataCertificate-critical data integrity
PDF fingerprintCompare the issued file bytes

Find the ID on your certificate

The same registry identity appears as text, inside the QR destination, and on the public verification record.

Fictional Verified Hikes certificate with controls identifying the certificate ID, QR code, and verification link1Show certificate ID explanation2Show QR code explanation3Show verification URL explanation
  1. 1
    Certificate ID

    A real issued ID follows the VHR-TRAILCODE-YEAR-SHORTID format.

  2. 2
    QR code

    Scan it to read the official destination. The scanner never opens an external link automatically.

  3. 3
    Verification URL

    Genuine public records use https://verifiedhikes.com/v/[certificate ID].

Fictional demonstration

What a public record shows

A registry record connects the printed certificate to its current status and privacy-safe public metadata.

Open the demo verification
Example recordNot an issued certificate
Current status
Demonstration state
Certificate ID
VHR-DEMO-EBC-2026
Trail
Everest Base Camp Trek
Completion
3-18 April 2026
Verification level
GPS Evidence Reviewed
Registry signature
Demonstration state

Raw GPS files, photographs, permits, and reviewer notes are not shown.

Read the current state

Understand the result

The public record tells you whether the document is current. Privacy choices can also limit the recipient name shown without publishing private evidence.

Valid

The displayed certificate is the current issued registry record.

Use the public record as the current version.

Reissued

A replacement certificate was issued for this record.

Follow the replacement link when it is public.

Superseded

This certificate has been replaced and is no longer the current version.

Use the linked current record instead.

Revoked

Verified Hikes has withdrawn the certificate's active registry status.

Do not treat the displayed document as current.

Not found

No public registry record matches the submitted identifier.

Check the ID. A missing record alone does not prove fraud.

What verification means

A public record is deliberately specific about what Verified Hikes can confirm.

Verification confirms

  • The record was issued by Verified Hikes
  • Its current registry status
  • Public trail and completion details
  • The stated verification level
  • Signed metadata and recorded PDF fingerprint

It does not automatically confirm

  • Legal identity, fitness, or safety
  • Present trail or weather conditions
  • Immigration or permit validity
  • Official trail-authority recognition
  • Anything not stated on the public record

A verification level describes what was reviewed or confirmed. It does not imply trail-authority endorsement unless the public record explicitly says Authority Confirmed.

Private evidence. Public proof.

The record shares enough to verify a certificate without exposing the material used to review it.

Kept private

Raw GPS and activity files, exact coordinates, original photographs and metadata, permits, contact and payment details, reviewer notes, and support correspondence.

Shown on the record

The chosen name display, trail, completion date, verification level, evidence summary, status, issuer, signature state, PDF fingerprint, and certificate ID.

Read privacy for hikers
Document integrity

Two checks, two clear jobs

The registry records both the issued PDF's exact fingerprint and a signature over certificate-critical metadata.

PDF fingerprint

A SHA-256 fingerprint identifies the exact issued file bytes. Editing or re-exporting the PDF changes that fingerprint.

Compare the full SHA-256 value shown on a real public record with a locally calculated file hash.

Signed certificate data

Certificate ID, status, snapshot hash, PDF hash, issue time, issuer ID, and signing key ID are signed with Ed25519.

A valid signature confirms consistency with the registry signing key. It does not expand the claims made by the record.
Technical verification details Certificate IDs, URLs, signatures, and hashes

Canonical identity

VHR-TRAILCODE-YEAR-SHORTID

https://verifiedhikes.com/v/[certificate ID]

Signed payload

Schema verified-hikes.certificate.v1 uses Ed25519. The public record exposes the signature state, metadata hash, PDF SHA-256, and signing key ID without exposing private signing material.

Exact file comparison

A matching SHA-256 value confirms identical PDF bytes. It does not independently prove legal identity or claims beyond the registry record.

Check the address before trusting the result

Genuine public records use HTTPS, the exact verifiedhikes.com hostname, and the /v/ certificate route.

https://verifiedhikes.com/v/VHR-EBC-2026-8K42P9Lookalike domains, unexpected ports, embedded usernames, and unrelated paths are rejected.

Something does not match?

Report an unknown ID, unexpected domain, changed certificate detail, fingerprint mismatch, privacy concern, or misleading claim privately.

Contact registry support

See a complete verification record

Open the fictional certificate to see status, verification level, privacy, and document integrity together.

View demo recordLearn how Verified Hikes works