← Identity home

IDENTITY / VERIFICATION

Verify VigiaLabsBot

Public keys and HTTP message signatures.

01

Check whether a request comes from VigiaLabsBot

Any crawler can copy VigiaLabsBot’s User-Agent. Finding our name in your logs does not, by itself, prove that a request comes from us.

VigiaLabsBot may use dynamic IP addresses. For requests signed with Web Bot Auth, verify the signature and its validity using the public keys associated with vigialabs.net.

The presence of signature headers alone does not establish authenticity.

If you cannot verify a request, contact bot@vigialabs.net with the source IP, date and time including the timezone, requested URL and available headers. Do not include credentials or unnecessary personal data.

A valid signature authenticates the signing identity. Cloudflare’s Verified designation is a separate recognition; consult its official directory to check it.

02

Public Key Directory

The directory publishes a JSON Web Key Set (JWKS). When configured, its response is signed by every published Ed25519 key.

https://vigialabs.net/.well-known/http-message-signatures-directory
Open the public directory ↗

Public Keys

Use the directory link to inspect the published public keys.

03

How Web Bot Auth works

Ed25519 produces digital signatures that a recipient can verify using a public key. RFC 9421 HTTP Message Signatures specifies how HTTP components and signature parameters are encoded for signing.

A JWK is a JSON representation of a key; a JWKS contains a set of those keys. The JWK Thumbprint identifies a public key using a SHA-256 digest of its canonical required members, following RFC 7638 and the OKP rules in RFC 8037.

The bot’s Signature-Agent is https://vigialabs.net. In the HTTP header it is a quoted structured string. The directory signature binds to the request authority, its content type and the digest of the published body.

04

HTTP headers

Crawler request — illustrative only

The examples below illustrate the protocol and are not valid signatures.

Signature-Agent: "https://vigialabs.net"
Signature-Input: sig1=("@authority" "signature-agent");created=<UNIX_TIME>;expires=<UNIX_TIME_PLUS_60>;keyid="<JWK_THUMBPRINT>";alg="ed25519";tag="web-bot-auth"
Signature: sig1=:<BASE64_SIGNATURE>:

Directory response — illustrative only

Content-Type: application/http-message-signatures-directory+json
Content-Digest: sha-256=:<BASE64_SHA256>: 
Signature-Input: sig1=("@authority";req "content-type" "content-digest");alg="ed25519";keyid="<JWK_THUMBPRINT>";tag="http-message-signatures-directory";created=<UNIX_TIME>;expires=<UNIX_TIME_PLUS_300>
Signature: sig1=:<BASE64_SIGNATURE>:
05

Validate with independent tools

Retrieve the directory over HTTPS and check the media type, the body digest, the published key thumbprints and every response signature against the requested authority and validity window. Establish trust in the operator through the authenticated domain and an independently trusted key fingerprint. A self-signed key set is not proof of Cloudflare approval.

Use Cloudflare’s official Web Bot Auth tools and the current integration documentation. Consult Cloudflare Radar for an official listing when one becomes available. No listing is claimed here.