Map the surface

Every scan opens with the same disciplined sweep, because you cannot follow a lead you have not found yet. Ports and services, technology fingerprints, WAF presence, subdomains, crawled endpoints, hidden parameters, TLS posture, and a first pass of template-based CVE detection.

phase 1 — reconnaissance and enumeration
nmap ports, services, versions whatweb framework, CMS, language, server wafw00f WAF present? adjust aggressiveness accordingly subfinder subdomains in scope theharvester OSINT — hosts, emails, exposed infrastructure gospider crawl for endpoints, forms, JS-referenced routes gobuster directory and vhost enumeration ffuf fuzz for exposed paths and files arjun discover parameters nothing links to nikto server misconfiguration and dangerous defaults testssl protocol versions, ciphers, certificate chain nuclei CVE and exposure templates

Follow the leads

This is the part a fixed tool list cannot do. Ironimo reads phase one's findings and decides what deserves a closer look — then runs the tool that answers the question.

WordPress fingerprinted

→ wpscan
Enumerate plugins and themes, check each against known vulnerabilities, test for user enumeration.

Parameter reflects input

→ xsstrike, sqlmap, commix
Probe for cross-site scripting, SQL injection, and command injection against the specific parameter, not blindly across the site.

Login form found

→ hydra
Test for weak and default credentials — only in profiles you have explicitly enabled.

JWT in a response

→ jwt_tool
Check algorithm confusion, signature stripping, weak secrets, and claim tampering.

Outdated version banner

→ searchsploit
Look up the exact version against Exploit-DB and report what public exploit code exists.

Nothing further to chase

→ report
When the leads are exhausted, the scan correlates, deduplicates, ranks by severity, and writes the report.

Every finding shows its work

A severity label with nothing behind it is an opinion. Each Ironimo finding carries the evidence that produced it, so your engineer can reproduce it in one command instead of arguing about whether it is real.

Severity and rank

Critical through informational, ordered so the top of the report is the part worth reading first.

Affected location

The exact URL, port, parameter, or header where the issue lives — not just "the application".

The tool and its output

Which binary found it, with what flags, and the raw output it returned. Verify it yourself.

A remediation path

What to change, in terms a developer can act on this sprint, not a link to a generic advisory.

Authenticated scanning

An unauthenticated scan sees your front door. The interesting attack surface — the admin panel, the account settings, the upload handler, the internal API — is behind the login. Ironimo supports password, token, and cookie-based sessions.

How credentials are handled: encrypted at rest with Fernet symmetric encryption, decrypted only at scan time and only inside the scan worker, never written to a report, and never returned by the API. Full detail on the Security page.

All 20 tools

These are the same binaries a consultant runs on an engagement. We name every one of them, because a scanner you cannot audit is a scanner you have to take on faith.

nmapPort & service discovery
whatwebTechnology fingerprinting
wafw00fWAF detection
subfinderSubdomain enumeration
theharvesterOSINT & domain intelligence
gospiderCrawling & endpoint discovery
gobusterDirectory / DNS / vhost brute force
dirbContent discovery
ffufFast web fuzzing
arjunHidden parameter discovery
niktoWeb server misconfiguration
nucleiTemplate-based CVE detection
testsslTLS configuration testing
sqlmapSQL injection
xsstrikeCross-site scripting
commixCommand injection
jwt_toolJWT analysis & attacks
hydraCredential brute force
wpscanWordPress vulnerabilities
searchsploitExploit-DB lookup

Where results land

Scheduled scanning

Weekly on Starter, daily on Pro, continuous on Enterprise. Set it once and stop remembering to run it.

Slack notifications

Scan completion and new findings pushed to the channel your team already watches. Pro and Enterprise.

Email notifications

Scan results delivered when a run finishes, on every plan.

PDF reports

Export a full report for your auditor, your board, or the customer security questionnaire that started all this.

API access

Pull findings into your own systems. Pro and Enterprise, with webhooks on Enterprise.

Teams and organisations

Invite your team, separate environments by organisation, and control who can see which targets.

What Ironimo will not find

Any vendor who tells you their scanner replaces a pentester is selling you something. Automated scanning is very good at enumerable problems and genuinely bad at a few things:

Keep your pentester. Ironimo covers the enumerable surface on the days nobody is testing — which, for most teams, is roughly 355 days a year.

See it against your own application.

First scan is free — a fixed six-tool pass over one target. Paid plans run the full 20-tool, two-phase chain described above.

We count page views without cookies (PostHog, EU-hosted) — nothing is stored on your device until you choose. Accept for full analytics, Decline to switch it off entirely. No personal data is sold or shared with advertisers.