Binary security, without the guesswork

Know what your binary is protecting.

checksec makes compiler and linker hardening visible. Inspect the security posture of a Linux executable, understand each finding, and fix the gaps that matter.

What gets checked

RELRO

Relocation hardening

See whether the binary protects its relocation tables.

CANARY

Stack canaries

Verify whether stack-smashing protection is present.

NX

Non-executable memory

Check whether writable memory is kept separate from execution.

PIE

Position independence

Understand whether address-space randomization can be used.

FORTIFY

Fortified functions

Find out whether common libc calls have compile-time checks.

RPATH

Loader paths

Spot runtime search paths that can weaken deployment safety.

A report you can act on

$ checksec --file=./app
RELRO           CANARY           NX             PIE
Partial RELRO   Canary found     NX enabled    PIE enabled