For CTF players
CTF Mode.
You've got a 30-minute clock and a UART boot log. BootIntel gets out of your way: unmasked CVE IDs, a higher daily quota, and pre-fill URL params so a challenge description can hand you a one-click link. Free, no signup, no email.
Two entry points, know when to use each
Fingerprint tool runs in your browser. Zero server round-trip. Bootloader / kernel / CPU / autoboot state / device family in 200 ms.
Open fingerprint tool →Paste at /terminal and hit Run Free Preview — or POST directly to /api/analysis/ctf-preview. Full CVE IDs, exploit paths. 10/day per IP.
Pre-fill URL params (for challenge descriptions)
Challenge organizers: drop these links directly in your problem statement so players don't need to copy-paste.
- /tools/fingerprint?paste=<url-encoded log text>
- /tools/fingerprint?log=/samples/<filename>.txtFetches from /samples/ only — no arbitrary URLs, no SSRF surface.
Warm-up challenges
Three real boot logs shipped in /samples/. Click a title to jump straight into the fingerprint tool with the log pre-loaded.
A budget consumer wireless router. Identify the SoC, the kernel, the userland version, and at least three CVEs the running BusyBox is vulnerable to.
A 2009-vintage boot chain. What year is the bootloader? What SoC family? Is autoboot interruptable?
A complete boot-to-userland capture. Enumerate every service that starts, and flag which ones bind to the WAN interface.
Direct API (server-side, unmasked)
curl -X POST https://bootintel.com/api/analysis/ctf-preview \
-H "Content-Type: application/json" \
-d '{"raw_log":"<paste boot log here>","device_name":"challenge-1"}'ctf: true so tooling can identify the mode.CVE-YYYY-**** in the response.Running a CTF? Want to partner?
If you're organizing a hardware or embedded CTF and want to use BootIntel in your challenge design — happy to bump your team's quota, share sample logs, or contribute a challenge writeup post-event. No sponsorship money, just collab.
[email protected] →