Skip to archive

Web Hacking Techniques Index / research archive

Opening the archive

Indexing two decades of web security research…

WEB HACKINGTECHNIQUES INDEXResearch archive

2006—NOW Research record

GH GitHub AI Judge your research X @irsdl ♥ Sponsor

Ways into the archive07

Research trail0 / 0

Archive held locally

— records indexed

⌕ /

GHGitHub AIJudge research X@irsdl ♥Sponsor

Search results

Room 01 / exhibition mode

Museum at Night

Walk through twenty years of research as rooms, illuminated winners and recovered artifacts.

— artifacts in this room

Support

This archive is free, and it stays free. Two decades of web hacking research, preserved before its hosts disappear. If it has been useful to you, a star is how other researchers find it — and sponsorship keeps the hosting, the recaptures and the curation going.

★Star it on GitHubFree, one click, helps the most ♥Sponsor the archiveHosting, preservation and tooling →Other ways to helpFix a dead link, report a bad capture

Credits

Jeremiah Grossman — created the list and curated 2006–2015.

James Kettle and PortSwigger — curators since 2016.

Every researcher behind the 1,100+ techniques collected here.

Maintained by Soroush Dalili (@irsdl).

Contribute / research submission

Submit research to the archive

Every officially nominated technique is already here. What the nomination rounds missed is the open question — and that is what this is for. Fill in what you know; the button below opens a prefilled GitHub issue you can read and edit before posting. Nothing leaves this page until you do.

Source URL required The researcher's own publication — not a newsletter or a summary of it. Title of the research Year published Researcher(s) What is new about it

↗ Open the prefilled issue

A GitHub account is needed to post it. Submissions are judged on the evidence — novel method, primary source, verified non-duplicate — and accepted ones join their year under “Missed from the original list”. Submitting your own research is welcome and judged no differently.

Something else? Dead or wrong link Faulty archived copy Researcher credit Website bug How submissions are reviewed

Report / record inaccuracy

Report an inaccuracy

Everything on this record is either machine-derived or a judgement call — the preserved Markdown and PDF, the links out, the byline, the summary, any recording — so any of it can be wrong. Tell us what looks off. The button below opens a prefilled GitHub issue you can read and edit before posting; nothing leaves this page until you do.

Record Filled in from the record you opened. What is wrong required Which part of the record Everything this record offers, listed as you just saw it. Leave it on “Not sure” if the fault is the record as a whole. What it should be, if you know Anything else

↗ Open the prefilled issue

A GitHub account is needed to post it. Every report is checked against the archived copy and its original source before the record changes.

Preserved material remains the work of its original author and publisher. The local copies are presented for research and historical access.

Preserved Markdown

Article reader

On this page

Archived article text is untrusted third-party content. It is displayed as data and cannot execute code here; external images load only after you choose their link.

Opening preserved Markdown…

Preserved PDF

Document viewer

Open PDF ↗ Download

Preparing the preserved document…

PDF

Open the complete PDF

The preserved file is still available using the Open PDF or Download controls above.

Open full PDF ↗

Links in this document

A link clicked inside the embedded PDF is handled by the browser's own viewer, which opens it in place rather than in a new tab. These open in a new tab.

Browser-native viewer Open PDF uses the browser or system viewer; Download saves a copy for another app. The embedded viewer has its own navigation, search and zoom.