Skip to main content
This page was machine-translated and may contain errors or omissions.

Security Reference

How to use

What it does

A quick-reference handbook for web security: sample test payloads for common XSS and SQL injection cases, the classes and meanings of HTTP status codes, the main risks listed by OWASP, combinations that tend to go wrong in CORS configuration, what each DNS record type is for, and common ports with their usual services. Handy for a security self-check, writing test cases, or revising for an exam.

How to use it

Pick a category on the left and its entries appear with explanations and examples. The search box matches keywords across categories. Payload entries can be copied for testing in environments you control — use them only on systems you are authorised to test. Configuration entries typically contrast a safe pattern with an unsafe one, which makes it easier to judge whether your own setup holds up.

FAQ

Can I take the payloads here and test any website with them?

No. Payloads are copyable but belong only on systems you own or are explicitly authorised to test; unauthorised testing is illegal. This reference exists for self-checks and learning, not as an arsenal.

I want to check my CORS setup — how do I use this reference for that?

Open the CORS category and check your configuration against the safe-versus-unsafe contrasts in each entry. The combinations that typically break are spelled out, which pinpoints the misconfiguration faster than browser errors alone.

Is this reference usable without a security background?

It is a quick reference, not a tutorial: entries carry explanations and examples, best for verifying details once you know the basic concepts, or as a self-audit checklist and revision material. Complete beginners get more out of it after a primer.