Request evidence · free inspection

Request inspector

See what your request reveals. Inspect its reported referrer, navigation context, client declarations and verification evidence.

10 checks per network address per UTC day, shared with Page check. Each inspection uses one check.

Open as JSON (uses a check). This link also works without JavaScript.

What the inspector shows

  1. Reported contextReferrer state, navigation signals and whether the source and site-relationship claims agree.
  2. Client declarationsClient names, browser-family and form claims, kept separate from verified evidence.
  3. VerificationNetwork-list results, available signatures and their coverage. Missing evidence stays unknown.

The button inspects a fetch sent from this page. Opening the JSON link sends a navigation request, so its evidence can differ. Neither reconstructs how you first arrived here or inspects traffic arriving at another site.

A reported referrer does not authenticate its source or establish a new search click. Referrer URLs, raw user agents and network addresses are not returned by this assessment.

For scripts and agents

Inspect a request as JSON

Call the endpoint from the client you want to inspect. It assesses the request that reaches this service and uses the same shared allowance.

API request example
curl https://gkoreli.com/api/request-check

API reference · Privacy and retention · Assessment source

Dispatch

GK-001

A note when there is signal.

Engineering records, failed experiments, and the life around the work.

gkoreli.com

Find a thought.

Search the full text of published articles. Results link directly to source passages.