Attack surface management, proven
RECON External finds every subdomain, port and service you expose to the internet, then tests each finding from an isolated server. You get evidence for what is real, a Risk Score built on it and reports your board can read. From EUR 90 per domain.
- 3 free domain scans
- Evidence with every proven finding
- Reports in English, Italian and Spanish
How it is calculated · Verification details
Also 1 proven header-hygiene issues, counted apart from vulnerabilities.
From domain to proof in three steps
Enter a domain. RECON does the rest and shows you every stage while it runs.
Discover
RECON maps subdomains, DNS, open ports, web services, technologies and certificates, and matches what it finds against known vulnerabilities.
Verify
Each finding is tested against the target from the scan’s own isolated server: proven, to verify or closed, with the evidence of every test.
Act
Fix what is proven first. The Risk Score, the reports and the 7/30/90-day plan all start from the verified results.
What one scan maps
Everything an attacker can reach from the internet, found from your domain name alone.
One map of everything exposed
The scan builds the map while it runs, from your domain name alone. No agent to install.
Every asset, in one inventory
Each host with its IP addresses, technologies, open ports, status and TLS version, as the scan recorded them.
Subdomains and DNS
Every subdomain, forgotten test hosts included, resolved to its addresses.
Open ports and banners
Which ports answer, and what each service says about itself.
Web services
Each site that answers, with a screenshot, its login forms and a crawled sitemap.
Technology fingerprinting
Servers, frameworks and products, recorded on the host where they were found.
Admin panels by favicon
Login and admin panels recognised by their favicon hash, even on unusual ports.
TLS, cloud and CDN footprint
Certificates, hosting providers, CDNs and the countries your hosts are served from.
CVE correlation with exploit signals
Detected products are matched to known CVEs and weighed by CISA KEV, Exploit-DB, Metasploit and EPSS. Then the verification tests them.
Every finding tested, with proof
A scanner reports what might be wrong. RECON then tests each finding against the target from the scan’s own isolated server and keeps the evidence of every test.
- Proven
Confirmed on the target from the scan’s own isolated server, with the evidence of every check attached.
- To verify
The test could not decide either way. It stays open and is flagged for a person to check by hand.
- Closed
A false positive the test disproved, or a finding excluded from the count. It no longer weighs on the Risk Score.
What a proof looks like
Open any proven finding and you see the host it was tested on, the verdict, the evidence quoted from the test log and how it was decided, step by step.
- A proof script you can download and run yourself. It only reads, and tells you whether the problem is still there.
- When the test cannot decide, a manual check with the exact commands to run and what to expect.
- Problems the verification finds on its own are added to the results.
- Actively exploited CVEs (CISA KEV) are decided on the evidence, like every other finding.
An internal working file is visible to everyone: it reveals how the site is built and helps anyone looking for weak spots.
Anyone can download /.git/config from staging.meccanicaadda.it: the server returns the repository configuration, not an error.
- Verified by
- Orizon AI
- Verifier
- orizon-ai-nova
- When
- Nov 2, 2026, 10:27 AM
Non-destructive: it only reads. It returns REPRODUCED if the problem is still there.
#!/usr/bin/env bash
# Reproducible proof (PoC) - /.git/config exposed on staging.meccanicaadda.it
# poc-format: 2
# Kind: proof ([REPRODUCED] = the vulnerable signal is still observed)
# Target: staging.meccanicaadda.it
# Verdict: PROVEN (proven severity: high) - Orizon RECON, verifier orizon-ai-nova, Nov 2, 2026
# Non-destructive: GET/HEAD reads.
# Requires: bash, curl, openssl, dig (all stock on macOS/Linux).
# curl runs with -k so a broken certificate (itself a finding) does not hide the response.
set -u
alias curl='curl -k'; shopt -s expand_aliases 2>/dev/null || true
PASS=0; FAIL=0; TMP="$(mktemp -d)"; trap 'rm -rf "$TMP"' EXIT
step() { printf '\n== %s\n' "$1"; }
NORESP=0; BLK=0; CTL=0
# no response / a WAF block are "no observation" (UNDECIDED), never "not reproduced"
observed() { if [ ! -s "$2" ]; then echo "[NO RESPONSE] $1"; NORESP=$((NORESP+1)); return 1; fi; if head -1 "$2" | grep -qE '^HTTP/[0-9.]+ (403|429|503)' && grep -qiE 'cf-mitigated|attention required|just a moment|captcha|access denied|request blocked|x-waf|incapsula|akamai' "$2"; then echo "[BLOCKED] $1"; BLK=$((BLK+1)); return 1; fi; return 0; }
expect() { observed "$1" "$2" || return 0; if grep -qiF -- "$3" "$2"; then echo "[REPRODUCED] $1"; PASS=$((PASS+1)); else echo "[NOT REPRODUCED] $1 (expected: $3)"; FAIL=$((FAIL+1)); fi; }
expect_absent() { observed "$1" "$2" || return 0; if grep -qiF -- "$3" "$2"; then echo "[NOT REPRODUCED] $1 (unexpected: $3)"; FAIL=$((FAIL+1)); else echo "[REPRODUCED] $1"; PASS=$((PASS+1)); fi; }
# negative control: the marker must NOT appear on a never-existing path of the same host
control() { curl -sS -i --max-time 20 "$2" > "$TMP/ctl" 2>/dev/null; if [ -s "$TMP/ctl" ] && grep -qiF -- "$3" "$TMP/ctl"; then echo "[CONTROL FAILED] $1: the marker also appears on $2"; CTL=$((CTL+1)); fi; }
step '[V1] GET https://staging.meccanicaadda.it/.git/config'
for try in 1 2; do curl -sS -i --max-time 20 https://staging.meccanicaadda.it/.git/config > "$TMP/r1"; grep -qE '^HTTP/[0-9.]+ 429' "$TMP/r1" || break; echo '(429 from a previous burst: waiting 65 s for the rate-limit window)'; sleep 65; done; sed -n '1,/^{0,1}$/p' "$TMP/r1" | grep -iE '^(HTTP|content-type|server|via|cf-ray|x-powered-by)'; sed '1,/^{0,1}$/d' "$TMP/r1" | head -c 800; echo
expect '[V1] response shows the recorded evidence' "$TMP/r1" '[core]'
control '[V1] negative control' https://staging.meccanicaadda.it/rcn-poc-control-"$RANDOM$RANDOM" '[core]'
# --- reachability ---
step '[REACH] reachability from the internet: open'
curl -sS -D "$TMP/reach" -o "$TMP/reachb" --max-time 20 https://staging.meccanicaadda.it/.git/config; head -1 "$TMP/reach"; grep -iE '^(server|cf-ray|cf-mitigated):' "$TMP/reach"
expect '[REACH] answers from the internet' "$TMP/reach" 'HTTP/'
expect_absent '[REACH] not blocked by a WAF' "$TMP/reach" 'cf-mitigated:'
# --- end reachability ---
echo
TOTAL=$((PASS+FAIL))
if [ "$NORESP" -gt 0 ] || [ "$BLK" -gt 0 ] || [ "$CTL" -gt 0 ]; then echo "RESULT: UNDECIDED (no response $NORESP, blocked $BLK, failed controls $CTL; $PASS/$TOTAL checks passed)"; exit 2; fi
if [ "$FAIL" -eq 0 ] && [ "$PASS" -gt 0 ]; then echo "RESULT: REPRODUCED ($PASS/$TOTAL checks)"; exit 0; fi
echo "RESULT: NOT REPRODUCED ($PASS/$TOTAL checks passed)"; exit 1
It answers directly from the internet: no security filter blocks the request.
curl -sS -i --max-time 15 https://staging.meccanicaadda.it/.git/config- Verified in the log · V1 L41Copy
[core] - Verified in the log · V1 L42Copy
repositoryformatversion = 0
- Identificationnot needed
- Analysis2 tools1.5 s
- Independent verification1 tools520 ms
- Proof1 tools390 ms
| Severity | Vulnerability | Status | Exploitability | Affected Asset | Risk | Actions |
|---|---|---|---|---|---|---|
CriticalCVSS 9.8 | Fortinet FortiOS 7.2.4CVE-2024-21762 | Proven | Actively exploited | vpn.meccanicaadda.it | 10.0 | |
HighCVSS 7.7 | nginx 1.18.0CVE-2021-23017 | Proven | Likely · 64% | staging.meccanicaadda.it | 7.9 | |
High | File /.git/config exposed on staging.meccanicaadda.itExposed file | Proven | Moderate | staging.meccanicaadda.it | 6.8 | |
Medium | TLS certificate of mail.meccanicaadda.it expired or expiringTLS certificate | Proven | Moderate | mail.meccanicaadda.it | 6.3 | |
Medium | Site source code recoverable (source maps) on portal.meccanicaadda.itExposed source code | Proven | Moderate | portal.meccanicaadda.it | 5.6 | |
Low | TLS certificate not valid for erp.meccanicaadda.itTLS certificate | Proven | Moderate | erp.meccanicaadda.it | 5.1 | |
MediumCVSS 6.5 | PHP 8.1.27CVE-2024-2756 | Proven | Low · 1% | www.meccanicaadda.it | 4.4 | |
MediumCVSS 6.1 | Bootstrap 3.3.7CVE-2019-8331 | Proven | Low · 2% | shop.meccanicaadda.it | 4.3 | |
Low | SSH reachable from the internet on 198.51.100.12Service exposed to the internet | Proven | Low | ftp.meccanicaadda.it | 4.0 | |
Info | www.meccanicaadda.it discloses the exact version nginx 1.24.0Version disclosed | Proven | Low | www.meccanicaadda.it | 2.7 |
- CriticalProvenrisk 10.0Fortinet FortiOS 7.2.4 CVE-2024-21762Actively exploited · vpn.meccanicaadda.it
- HighProvenrisk 7.9nginx 1.18.0 CVE-2021-23017Likely · 64% · staging.meccanicaadda.it
- HighProvenrisk 6.8File /.git/config exposed on staging.meccanicaadda.itModerate · staging.meccanicaadda.it
- MediumProvenrisk 6.3TLS certificate of mail.meccanicaadda.it expired or expiringModerate · mail.meccanicaadda.it
- MediumProvenrisk 5.6Site source code recoverable (source maps) on portal.meccanicaadda.itModerate · portal.meccanicaadda.it
- LowProvenrisk 5.1TLS certificate not valid for erp.meccanicaadda.itModerate · erp.meccanicaadda.it
- MediumProvenrisk 4.4PHP 8.1.27 CVE-2024-2756Low · 1% · www.meccanicaadda.it
- MediumProvenrisk 4.3Bootstrap 3.3.7 CVE-2019-8331Low · 2% · shop.meccanicaadda.it
- LowProvenrisk 4.0SSH reachable from the internet on 198.51.100.12Low · ftp.meccanicaadda.it
- InfoProvenrisk 2.7www.meccanicaadda.it discloses the exact version nginx 1.24.0Low · www.meccanicaadda.it
A Risk Score built on proof
Every scan gets a Risk Score from 0 to 10. Proven problems count in full, those still to verify count less, and disproved or excluded ones do not count. Problems the verification found on its own count too. Beside it you see the score before verification, so you know what the verification changed.
- Verdict weights: proven × 1.0, to verify × 0.8, accepted risk × 0.3, disproved and excluded × 0.
- A weighted mean of the 30 most serious findings, with the most serious weighing most.
- Bands: Critical from 8.5, High from 6.0, Medium from 3.5, Low from 1.5.
- Every scan has one, including scans with only low or informational findings.
- Per problem: 0.40 × severity (the higher of CVSS/10 and the weight: critical 1.0 · high 0.8 · medium 0.5 · low 0.2 · informational 0.05) + 0.35 × exploitation (EPSS probability; already exploited per CISA KEV = 1.0; +0.3 if a Metasploit module exists; +0.2 if public attack code exists; max 1) + 0.15 × exposure (before: 1.0 for every exposed host; after, from the verified reachability: exposed 1.0 · filtered 0.4 · unreachable 0.2) + 0.10 × sensitive technology (identity, VPN, mail, payments, administration, database = 1.0; otherwise 0.3).
- Confirmation factor: version not observed × 0.8 · mitigated or fixed × 0.3 · disproved and excluded items do not count.
- Score: weighted mean of the 30 most serious problems (weights 1.0 · 0.98 · 0.96 … down to 0.4), on a 0–10 scale with one decimal.
- Bands: from 8.5 Critical · from 6.0 High · from 3.5 Medium · from 1.5 Low.
- Problems without a CVE: severity = verified severity; exploitation = 1.0 when the proof reproduces the abuse as is, 0.5 when it exposes information, 0.2 when informational.
- Before: every finding, as RECON computes it today. After: proven vulnerabilities (× 1.0) and those to verify (× 0.8).
Detailed calculation
- 1. CVE-2024-217621.0000 × 10 × 1.00 = 10.0000Severity 1.00 · Exploitation 1.00 (EPSS 94.00% · KEV) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×1.00
- 2. CVE-2024-231130.8000 × 10 × 0.98 = 7.8400Severity 1.00 · Exploitation 1.00 (EPSS 72.00% · KEV) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×0.80
- 3. CVE-2021-230170.7940 × 10 × 0.96 = 7.6224Severity 0.80 · Exploitation 0.84 (EPSS 64.00% · public attack code +0.2) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 4. /.git/config exposed on staging.meccanicaadda.it0.6750 × 10 × 0.94 = 6.3450Severity 0.80 · Exploitation 0.50 (exposure or disclosure (0.5)) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 5. CVE-2024-63870.6412 × 10 × 0.92 = 5.8990Severity 0.81 · Exploitation 0.65 (EPSS 45.00% · public attack code +0.2) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×0.80
- 6. TLS certificate of mail.meccanicaadda.it expired (2026-10-19)0.6250 × 10 × 0.90 = 5.6250Severity 0.50 · Exploitation 0.50 (exposure or disclosure (0.5)) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×1.00
- 7. CVE-2023-517640.5992 × 10 × 0.88 = 5.2730Severity 0.53 · Exploitation 0.82 (EPSS 62.00% · public attack code +0.2) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×0.80
- 8. Public source maps on portal.meccanicaadda.it (14)0.5550 × 10 × 0.86 = 4.7730Severity 0.50 · Exploitation 0.50 (exposure or disclosure (0.5)) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 9. TLS certificate of erp.meccanicaadda.it not valid for the name (CN=www.meccanicaadda.it)0.5050 × 10 × 0.84 = 4.2420Severity 0.20 · Exploitation 0.50 (exposure or disclosure (0.5)) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×1.00
- 10. CVE-2024-27560.4442 × 10 × 0.82 = 3.6424Severity 0.65 · Exploitation 0.01 (EPSS 1.20%) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 11. CVE-2019-83310.4314 × 10 × 0.80 = 3.4508Severity 0.61 · Exploitation 0.02 (EPSS 2.10%) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 12. SSH exposed to the internet on 198.51.100.12 (ftp.meccanicaadda.it): SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.60.4000 × 10 × 0.78 = 3.1200Severity 0.20 · Exploitation 0.20 (informational (0.2)) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×1.00
- 13. www.meccanicaadda.it discloses nginx/1.24.00.2700 × 10 × 0.76 = 2.0520Severity 0.05 · Exploitation 0.20 (informational (0.2)) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 14. /version.json on erp.meccanicaadda.it discloses deployment metadata without authentication0.2640 × 10 × 0.74 = 1.9536Severity 0.20 · Exploitation 0.00 (EPSS 0.00%) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×0.80
Sum of contributions 71.8382 ÷ sum of weights 12.18 = 5.8980 → Risk Score 5.9
- 1. CVE-2024-217621.0000 × 10 × 1.00 = 10.0000Severity 1.00 · Exploitation 1.00 (EPSS 94.00% · KEV) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×1.00
- 2. CVE-2024-231131.0000 × 10 × 0.98 = 9.8000Severity 1.00 · Exploitation 1.00 (EPSS 72.00% · KEV) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×1.00
- 3. CVE-2023-279971.0000 × 10 × 0.96 = 9.6000Severity 1.00 · Exploitation 1.00 (EPSS 97.00% · KEV) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×1.00
- 4. CVE-2022-424751.0000 × 10 × 0.94 = 9.4000Severity 1.00 · Exploitation 1.00 (EPSS 97.00% · KEV) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×1.00
- 5. CVE-2024-45770.9300 × 10 × 0.92 = 8.5560Severity 1.00 · Exploitation 1.00 (EPSS 94.00% · KEV) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 6. CVE-2024-63870.8015 × 10 × 0.90 = 7.2135Severity 0.81 · Exploitation 0.65 (EPSS 45.00% · public attack code +0.2) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×1.00
- 7. CVE-2021-230170.7940 × 10 × 0.88 = 6.9872Severity 0.80 · Exploitation 0.84 (EPSS 64.00% · public attack code +0.2) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 8. CVE-2023-517640.7490 × 10 × 0.86 = 6.4414Severity 0.53 · Exploitation 0.82 (EPSS 62.00% · public attack code +0.2) · Exposure 1.00 · Sensitive 1.00 · Confirmation ×1.00
- 9. CVE-2024-89260.7200 × 10 × 0.84 = 6.0480Severity 1.00 · Exploitation 0.40 (EPSS 40.00%) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 10. CVE-2019-95130.5070 × 10 × 0.82 = 4.1574Severity 0.80 · Exploitation 0.02 (EPSS 2.00%) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 11. CVE-2019-95110.5070 × 10 × 0.80 = 4.0560Severity 0.80 · Exploitation 0.02 (EPSS 2.00%) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 12. CVE-2024-27560.4442 × 10 × 0.78 = 3.4648Severity 0.65 · Exploitation 0.01 (EPSS 1.20%) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 13. CVE-2019-95160.4435 × 10 × 0.76 = 3.3706Severity 0.65 · Exploitation 0.01 (EPSS 1.00%) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 14. CVE-2019-83310.4314 × 10 × 0.74 = 3.1920Severity 0.61 · Exploitation 0.02 (EPSS 2.10%) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 15. CVE-2018-140400.4257 × 10 × 0.72 = 3.0654Severity 0.61 · Exploitation 0.01 (EPSS 0.50%) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
- 16. CVE-2018-140420.4254 × 10 × 0.70 = 2.9778Severity 0.61 · Exploitation 0.00 (EPSS 0.40%) · Exposure 1.00 · Sensitive 0.30 · Confirmation ×1.00
Sum of contributions 98.3301 ÷ sum of weights 13.60 = 7.2302 → Risk Score 7.2
Completed in 38 min 24 s
- Host identification
- Technology verification
- Exact correlation
- Automatic rules
- Automatic verification
- Discovery
- Verify discovered
- Exploration
Verified technologies and exploration of this scan, host by host.
Open the verification detailsFirst we identify the product and version with fixed rules; then an agent runs at most 6 harmless checks, a second, independent agent repeats the decisive proof and code checks every quoted piece of evidence.
- Verifier
- Orizon AI · orizon-ai-nova
- Callback server
- oast.pro,oast.live,oast.site,oast.online,oast.fun,oast.me (ProjectDiscovery public)
- Tools
- Tools isolated in containers
- Excluded (reason)
- -
What drives the score of each finding
Severity40%
The higher of the CVSS score and the severity weight.
Exploitation35%
EPSS probability, set to the maximum for CISA KEV, raised by Metasploit modules and public exploit code.
Exposure15%
Whether the host answers from the internet, sits behind a WAF or CDN, or does not answer.
Sensitive technology10%
Identity, VPN, mail, payments, administration and databases weigh more.
Watch every scan as it runs
From creation to the last result you see what runs: the start, each discovery tool, the reasoning of the verification and the analysis, under a single progress bar.
- Group scans for many domains: every domain is verified and the group gets its own Risk Score.
- One live stream for the whole group, with a filter per domain, and one Vulnerabilities page for all of them.
- Repeat a scan as a new one and keep the previous run whole, or rescan in place.
- A server that stops answering is reported in the stream instead of being retried for hours.
Quiet by design
Built not to trip your firewall or bot protection, and to tell you when they answered instead of your site.
An external scan that sets off every alarm is useless: the firewall bans it and half the results are missing.
RECON is built to see your perimeter without being thrown out of it, and to tell you when something did block it.
Sensitive checks run last
The most sensitive checks run at the end and stop at the server’s first reaction. A server that stops answering is reported, not retried for hours.
Last in line, stop on reaction, no endless retries
Fresh egress IPs
Each external scan runs from clean, ephemeral IP addresses, so shared-IP reputation blocks and WAF bans do not distort the results.
Ephemeral, clean reputation, one per scan
Blocks are flagged
When a WAF or a bot challenge answers instead of your site, the scan says so instead of handing you incomplete results in silence.
WAF, bot challenge, degraded results
Proofs only read
Verification runs from a server created for the scan, firewall included, and its proofs are non-destructive: they read, they never change.
Isolated server, read-only proofs, evidence kept
The basics attackers check first
Spoofable email, lapsed certificates and missing headers are where many attacks begin. RECON checks them on every scan.
Email authentication
SPF, DKIM and DMARC decide whether someone can send email in your name. RECON reads each record and says what it allows.
DNSSEC
Whether your zone is signed, so answers about your domain cannot be forged on the way.
TLS certificates
Issuer, validity and expiry for every host, so a certificate never lapses unnoticed.
Security headers
Which protective HTTP headers each site sends, and which are missing.
Cookie security
How securely your sites set their cookies.
Login forms and screenshots
Where your sites ask for a password, with a screenshot of each page and a crawled sitemap.
NIS2 and sector risk, in every scan
Know where the company stands under the Directive, and how exposed it is compared with its sector.
NIS2 classification with its rule
RECON classifies the company as an Essential Entity, an Important Entity or not applicable, and shows the criteria that decided it: EU operations, size, sector and revenue. The analysis is available in English, Italian and Spanish.
Industry Risk against your sector
Five weighted factors give a score and a grade from A to F: technical posture, exposure, the industry baseline, the organisation and how close recent breaches are. You also get the annual breach probability, threat scenarios, recommendations and recent breaches at similar companies in your country and sector.
Keep watching as it changes
Your attack surface changes every week. Schedule scans daily, weekly, every two weeks, monthly or quarterly, and follow the score and the findings from one scan to the next on the timeline, with proven vulnerabilities marked on it.
- Scan history with what changed since the previous scan.
- Revalidate a scan, or Re-check and Verify fix on one finding: queued for the next scan, shown as queued, and you can withdraw it.
- Events to Jira, ServiceNow, Splunk, Microsoft Sentinel, Slack, an email digest or a signed webhook.
Reports for engineers and the board
One click generates the technical report and the executive brief, both built on the verified results. Every report is digitally signed and can be checked on a verification page.
- Interactive HTML report: the same overview, charts, maps, attack paths and detail drawers as the app, in English, Italian or Spanish.
- Executive brief: decisions for management, the main business risks, how an attacker could get in, email spoofing risk, a 7/30/90-day plan with the residual risk, NIS2 and your sector.
- PDF, and a CSV ZIP with one file per data set and a column guide.
- Share links that expire and can be revoked, and a public REST API (v1, OpenAPI) that also generates, downloads and shares reports.
This document summarises and interprets the technical report. The full details remain in the technical report.
This document contains confidential information about the security of the organisation named above.
Prepared by: Meccanica Adda
What does it mean for the company?
Risk Score 5.9: medium. A 0 to 10 score of how dangerous, overall, what the scan reported and the verification found is: proven problems count in full, those still to verify or not verifiable now count with a reduced weight, disproved or excluded ones do not count. The higher it is, the more urgent it is to act.
Before verification: 7.2 · High Risk.
Simple pricing per domain
Pay for the domains you scan. Bundles lower the price per domain and stay valid for 12 months.
Pay as you go
EUR 90
One domain scan
- EUR 90 per domain
- 90 tokens
- Discovery, verification and reports
Starter
EUR 630
10 domains
- EUR 63 per domain
- 900 tokens
- Valid 12 months
- Save 30%
Professional
EUR 1,487.50
25 domains
- EUR 59.50 per domain
- 2,250 tokens
- Valid 12 months
- Save 34%
Business
EUR 2,800
50 domains
- EUR 56 per domain
- 4,500 tokens
- Valid 12 months
- Save 38%
Enterprise
EUR 5,250
100 domains
- EUR 52.50 per domain
- 9,000 tokens
- Valid 12 months
- Save 42%
Your first 3 domain scans are free. One domain scan uses 90 tokens. Prices exclude VAT. See every RECON plan
Questions about RECON External
External attack surface management, verification, pricing and NIS2.
The rest of RECON
See what an attacker sees
Your first 3 domain scans are free. Enter a domain and get verified findings, a Risk Score and reports.

