Encrypt Online
Theme

S3 Presigned URL Debugger

Check the expiry and signing details of an S3 presigned URL

The link is checked in your browser without opening it. Treat it like a temporary password.

Check a presigned linkNo AWS credentials needed

GET downloads; PUT uploads. Choose the method your client sends; it isn't included in the URL.

Request headers, time, and signing key

Enter one name: value per line, using the values your client sends.

Leave empty for the current time, or enter the time of a failed request.

Add the key to compare signatures. Use test credentials when debugging your signing code.

Expiry and signed headers

Paste the complete URL to see its expiry, region, and required headers. Add a signing key only if you need to compare signatures.

SignatureDoesNotMatch

Compare the request your client sends with the one used to sign the URL. The method, host, path, query parameters, and signed headers must match. For uploads, check Content-Type first.

Use the original URL, including every X-Amz- parameter. Changing a parameter or decoding the URL before sending it can change the signature.

Fix S3 presigned URL SignatureDoesNotMatch errors

Temporary credentials and expiry

A link stops working when its signing credentials expire, even if X-Amz-Expires allows more time. Check the expiry returned with the temporary credentials. IAM, bucket policies, and KMS permissions can also deny access; browser CORS errors need a separate CORS check.

To build an Authorization header, use the AWS SigV4 calculator. The canonical request guide explains the values used to calculate a signature.

This page supports S3 URLs signed with AWS4-HMAC-SHA256. Use an AWS SDK for SigV4a, streaming signatures, or presigned POST forms.

PUT, GET, and Content-Type

Download examples (JSON)

Compare one matching presigned PUT with method and Content-Type mismatches using the same synthetic URL, public example key, and fixed reference time.

Matching PUT request

The supplied PUT method and text/plain Content-Type reproduce the signature in this synthetic upload URL.

The calculated signature equals the URL signature. At the fixed reference time, 1,800 seconds remain in the requested lifetime.

Inputs and expected values
  1. Paste this synthetic presigned URL and choose PUT as the Request method.
  2. Open Request headers, time, and signing key. Enter Content-Type: text/plain and the public example secret below.
  3. Set Reference time in UTC to May 24, 2013 at 00:30:00 so the historical example is checked within its original hour.
  4. Select Check URL. The signature matches; compare the canonical request and both signatures below.
Presigned URL
https://examplebucket.s3.amazonaws.com/test.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIOSFODNN7EXAMPLE%2F20130524%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20130524T000000Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=content-type%3Bhost&X-Amz-Signature=3283ea304eace967b5bac32c10643da28a8e29777fefaa542771984238c2c7f3
Request method
PUT
Request headers
Content-Type: text/plain
Reference time (UTC)
2013-05-24T00:30:00Z
Public AWS example secret
wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
Canonical request
PUT
/test.txt
X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIOSFODNN7EXAMPLE%2F20130524%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20130524T000000Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=content-type%3Bhost
content-type:text/plain
host:examplebucket.s3.amazonaws.com

content-type;host
UNSIGNED-PAYLOAD
Signature in the URL
3283ea304eace967b5bac32c10643da28a8e29777fefaa542771984238c2c7f3
Calculated signature
3283ea304eace967b5bac32c10643da28a8e29777fefaa542771984238c2c7f3

GET with a URL signed for PUT

Choosing GET for the same URL changes the calculated signature even though its query parameters are unchanged.

Use PUT for this upload URL. The HTTP method is signed even though the URL does not contain a method parameter.

Inputs and expected values
  1. Paste the same synthetic URL, then choose GET instead of PUT.
  2. Keep Content-Type: text/plain, the public example secret, and Reference time in UTC at May 24, 2013 at 00:30:00.
  3. Select Check URL. The first canonical request line is now GET, and its calculated signature differs from the URL signature.
  4. Change only Request method back to PUT and check again to restore the match.
Presigned URL
https://examplebucket.s3.amazonaws.com/test.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIOSFODNN7EXAMPLE%2F20130524%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20130524T000000Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=content-type%3Bhost&X-Amz-Signature=3283ea304eace967b5bac32c10643da28a8e29777fefaa542771984238c2c7f3
Request method
GET
Request headers
Content-Type: text/plain
Reference time (UTC)
2013-05-24T00:30:00Z
Public AWS example secret
wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
Canonical request
GET
/test.txt
X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIOSFODNN7EXAMPLE%2F20130524%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20130524T000000Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=content-type%3Bhost
content-type:text/plain
host:examplebucket.s3.amazonaws.com

content-type;host
UNSIGNED-PAYLOAD
Signature in the URL
3283ea304eace967b5bac32c10643da28a8e29777fefaa542771984238c2c7f3
Calculated signature
1415fd73752d790a55ee5ad5af3c82e02906afa3797dc27d5b9d6bc68b916ee6

A different Content-Type

Changing the signed Content-Type from text/plain to application/json changes the signature for the same PUT URL.

Send the Content-Type used by the signer, or generate a new URL for the intended type. This URL signs text/plain.

Inputs and expected values
  1. Paste the same synthetic URL, choose PUT, and enter Content-Type: application/json in Request headers.
  2. Keep the public example secret and Reference time in UTC at May 24, 2013 at 00:30:00.
  3. Select Check URL. The canonical Content-Type value and calculated signature now differ from the matching upload example.
  4. Change only the header value back to text/plain and check again to restore the match.
Presigned URL
https://examplebucket.s3.amazonaws.com/test.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIOSFODNN7EXAMPLE%2F20130524%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20130524T000000Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=content-type%3Bhost&X-Amz-Signature=3283ea304eace967b5bac32c10643da28a8e29777fefaa542771984238c2c7f3
Request method
PUT
Request headers
Content-Type: application/json
Reference time (UTC)
2013-05-24T00:30:00Z
Public AWS example secret
wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
Canonical request
PUT
/test.txt
X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIOSFODNN7EXAMPLE%2F20130524%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20130524T000000Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=content-type%3Bhost
content-type:application/json
host:examplebucket.s3.amazonaws.com

content-type;host
UNSIGNED-PAYLOAD
Signature in the URL
3283ea304eace967b5bac32c10643da28a8e29777fefaa542771984238c2c7f3
Calculated signature
42be1cff50d54fec5ca261e8386253c900e568175b869eee72afff9602b2c101

This synthetic PUT variation uses AWS's public example credentials and a fixed 2013 reference time. The comparisons check signature bytes; they do not send requests or test AWS permissions. The historical URL is expired today.

Checked 2026-10-20. From the site's webapp3 directory, run npm run check:citation-evidence to compare the tool results with the saved expectations. The JSON includes every input, expected output, and source hash.

Inputs are not saved. The site may load analytics and advertising. Privacy details.