ScoreDetect Docs
  • What is ScoreDetect?
  • FAQ
    • How does it work?
    • What types of data can I protect?
    • Why should I use it?
    • Is it suitable for me?
    • I have historical content
    • Is it free?
    • Is my data secure?
    • Why do I need to register an account?
    • How do I contact support?
    • How do I report bugs?
  • Certificates
    • What is a certificate?
    • How does a certificate work?
    • What sets these certificates apart from others?
    • Can I use a certificate for copyright protection?
    • How can I verify the information in a certificate?
    • Are these certificates secure?
    • Can I create certificates for all types of data?
    • How can I use certificates to build trust with my audience?
    • Is there a limit to how many certificates I can create?
    • How long does it take to get a certificate?
    • How many certificates can I create?
    • How can I download / export my certificates?
    • How long can I keep my account and certificates?
    • How can I use my own certificate label?
    • Custom Domains
    • Certificate Languages
  • Integrations
    • ScoreDetect Integrations
    • Zapier
    • WordPress
    • WooCommerce
  • API
    • ScoreDetect API
      • Authentication
      • Rate Limits
      • Usage Policy
  • Product
    • Changelog
    • Roadmap
Powered by GitBook
On this page

Was this helpful?

  1. Certificates

How can I verify the information in a certificate?

Verifying the information in a ScoreDetect verification certificate is straightforward. You can use the provided blockchain transaction URL and digital checksum to confirm the authenticity of your content with ease.

All you need is the file or text used in the certificate. And you can hash it using any SHA256 converter.

To generate the hash (SHA-256) of a signed document, you can use any SHA-256 hashing tool or execute specific commands based on your operating system:

  • OpenSSL (Command): openssl dgst -sha256 <filename>

  • Windows (Command Prompt): CertUtil -hashfile <filepath> SHA256

  • MacOS (Terminal): shasum -a 256 <filepath>

  • Linux (Terminal): sha256sum <filepath>

After generating the hash, compare it with the document's hash from the blockchain transaction details. If the hashes match, the document's signing at the recorded time is considered verifiably true.

We do not keep backups of your File / Text - it is up to you to make sure that the File / Text will be available in the future if its existence needs to be proven. This way, it ensures maximum protection for your digital asset.

PreviousCan I use a certificate for copyright protection?NextAre these certificates secure?

Last updated 9 months ago

Was this helpful?