> For the complete documentation index, see [llms.txt](https://docs.sign-web.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sign-web.app/certification/verification-explorer.md).

# Verification Explorer

### **OVERVIEW**

![](/files/-M8-lSQNEmJCkw3YpZEO)

Accessible at <https://www.sign-web.app/explorer> the explorer is a straight forward way to search if a file has already been certified or if a certification sent to you is valid.

**VERIFY BY PROOF OF CERTIFICATION**

You can verify a certification simply by selecting it's Proof Of Certification after clicking on the "Select or Drop a Proof Of Certification" button:

![](/files/-M8-m4udH8Xh5edx97Nx)

The Proof Of Certification is a PDF that looks like the following:

![](/files/-M8-mTy_5-_CeuoJC67d)

This PDF includes the details of the Certification as well as some metadata allowing the SIGN explorer to automatically read this information and retrieve the associated transaction from the Waves Blockchain.

{% hint style="info" %}
**FIELDS**\
*Reference, Date, File Hash or Email ID, Link to the transaction on the Waves Explorer, QR Code to the transaction on the Waves Explorer. Multi Party Agreement will include a second page with the counterparts addresses and their signature status*
{% endhint %}

If the transaction exists, the certificate will be displayed in the SIGN explorer as follow:

![](/files/-M8-nV5g5Bhavc5kRbHs)

**VERIFY BY HASHING A FILE**

You also have the option to hash any file, using the **"Select or Drop a File to hash"** and it will retrieve all the certifications, if any, that are included with this exact file hash:

![](/files/-M8-o3RhFXjSONXU4qHf)

Once the file is selected, its hash will be added in the Hash field and by clicking the "SEARCH" button you will start retrieving the data.

![](/files/-M8-o_meRyBEQ0oC8cuU)

**VERIFY BY DATA**

Similarly you can choose to search directly by Transaction ID, File Hash, Message ID or reference as well as combining some of them for more accurate results.

![](/files/-M8-pBdt8-7GP6cFz55y)

Direct link to a Certification in the explorer looks like the following:

`https://www.sign-web.app/explorer/{the_transaction_ID}`

**Example:**\
<https://www.sign-web.app/explorer/Hv5UC2dwFZSadhNFtqtxuSTrRSg8drGx4mWw2igL9KaQ>

If the certificate have been revoked by its creator, you will see the "revoked" mention on the top right corner:

![](/files/-MBmpFlTuTZMjEclwlG9)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sign-web.app/certification/verification-explorer.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.