RECON External · EASM

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
recon.orizon.one
Risk Assessment
Medium Risk

How it is calculated · Verification details

Critical1provenof 2 possible
High2provenof 3 possible
Medium4provenof 5 possible
Low2provenof 2 possible

Also 1 proven header-hygiene issues, counted apart from vulnerabilities.

Exploitability · among the proven vulnerabilities
0Exploitable nowreproduced with a minimal, harmless proof
1Actively exploitedCISA KEV catalog
2Attack likely≥ 50% chance of attack within 30 days (EPSS)
1Used by ransomwareCISA KEV catalog, ransomware use

From domain to proof in three steps

Enter a domain. RECON does the rest and shows you every stage while it runs.

  1. Discover

    RECON maps subdomains, DNS, open ports, web services, technologies and certificates, and matches what it finds against known vulnerabilities.

  2. 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.

  3. 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.

recon.orizon.one

One map of everything exposed

The scan builds the map while it runs, from your domain name alone. No agent to install.

recon.orizon.one

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.
recon.orizon.one
recon.orizon.one
1 vulnerability is in CISA Known Exploited Vulnerabilities catalog
Proven10To verify4Closed9
Filter by Category:All categories(10)CVE Vulnerabilities(4)Found by the verification(6)
Sort by Risk Score
Search CVE, problem or asset
All Severities
10 proven vulnerabilities of 14 possible · ordered by weight on the risk score (of which 1 informational, not in the severity cards)
  • CriticalProvenrisk 10.0
    Fortinet FortiOS 7.2.4 CVE-2024-21762
    Actively exploited · vpn.meccanicaadda.it
  • HighProvenrisk 7.9
    nginx 1.18.0 CVE-2021-23017
    Likely · 64% · staging.meccanicaadda.it
  • HighProvenrisk 6.8
    File /.git/config exposed on staging.meccanicaadda.it
    Moderate · staging.meccanicaadda.it
  • MediumProvenrisk 6.3
    TLS certificate of mail.meccanicaadda.it expired or expiring
    Moderate · mail.meccanicaadda.it
  • MediumProvenrisk 5.6
    Site source code recoverable (source maps) on portal.meccanicaadda.it
    Moderate · portal.meccanicaadda.it
  • LowProvenrisk 5.1
    TLS certificate not valid for erp.meccanicaadda.it
    Moderate · erp.meccanicaadda.it
  • MediumProvenrisk 4.4
    PHP 8.1.27 CVE-2024-2756
    Low · 1% · www.meccanicaadda.it
  • MediumProvenrisk 4.3
    Bootstrap 3.3.7 CVE-2019-8331
    Low · 2% · shop.meccanicaadda.it
  • LowProvenrisk 4.0
    SSH reachable from the internet on 198.51.100.12
    Low · ftp.meccanicaadda.it
  • InfoProvenrisk 2.7
    www.meccanicaadda.it discloses the exact version nginx 1.24.0
    Low · 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.
recon.orizon.one

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.
recon.orizon.one

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.

recon.orizon.one

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.

recon.orizon.one

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.

recon.orizon.one

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.
recon.orizon.one

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.
recon.orizon.one
Executive briefExposure on the internet
Executive report for managementReport date:

This document summarises and interprets the technical report. The full details remain in the technical report.

Scope analysed
meccanicaadda.it
Scan window
2 November 2026, 08:00 UTC – 2 November 2026, 10:51 UTC
Source
Orizon RECON External, 1 domain

This document contains confidential information about the security of the organisation named above.

Prepared by: Meccanica Adda

Summary for management

What does it mean for the company?

Risk Score
Medium

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.

What was analysed
9
Hosts online
9
Subdomains
17
Open ports
18
Technologies
Distinct findings
Distinct vulnerabilities14
Critical, proven1
To verify4
Closed9
Found by the verification7

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.

EASM is the continuous discovery and assessment of everything an organisation exposes to the internet: domains, subdomains, IP addresses, open ports, web applications and the software behind them. The aim is to see that perimeter the way an attacker does and to fix weaknesses before they are used. RECON External does this from your domain name alone, with nothing to install.
A scanner lists what might be vulnerable, often from a version number alone. RECON then tests each finding against the target from the scan’s own isolated server and marks it Proven, To verify or Closed, with the evidence of every test. The Risk Score and the reports are built on those verified results, so your team starts from what is real.
A penetration test is a time-boxed exercise that tries to chain weaknesses together to prove impact. RECON External runs automatically, on a schedule, across every domain you own, and keeps the evidence of each verdict. Many teams use RECON to keep watch continuously and Fireline, Orizon’s autonomous external penetration test, which starts from a RECON scan, when they need impact proven on an authorised scope.
RECON is built not to. The most sensitive checks run last and stop at the server’s first reaction, a server that stops answering is reported instead of retried for hours, and proofs only read. Scans run from fresh, ephemeral IP addresses, and when a WAF or a bot challenge answers instead of your site, the scan flags it.
Proven: the verification confirmed that the problem exists on the target and the evidence is attached. To verify: the test could not decide, so you get a manual check with the commands to run. Closed: the finding was disproved or excluded, for example because the installed version is not affected; it no longer counts in your numbers or in the Risk Score.
Each finding is scored on severity (40%), exploitation signals such as CISA KEV and EPSS (35%), exposure from the internet (15%) and how sensitive the technology is (10%), then weighted by its verdict: proven counts in full, to verify at 0.8, accepted risk at 0.3, disproved and excluded not at all. The 0 to 10 score is a weighted mean of the 30 most serious findings, and the score before verification is shown beside it.
Yes. Each scan classifies the company as an Essential Entity, an Important Entity or not applicable, with the criteria that decided it, and the executive brief has a NIS2 section. Scheduled scans and signed reports also document how you find and fix vulnerabilities. RECON does not replace a legal assessment of your obligations.
A domain scan costs EUR 90. Bundles bring the price down to EUR 52.50 per domain with 100 domains, valid for 12 months. Your first 3 domain scans are free. Prices exclude VAT.
Yes. A group scan covers many domains in one run, with a group Risk Score, one live stream and one Vulnerabilities page. Schedules repeat scans daily, weekly, every two weeks, monthly or quarterly, and the timeline shows what changed between scans.
Yes. The public REST API (v1, with an OpenAPI description) starts scans, returns their data and generates, downloads and shares reports. Integrations send events to Jira, ServiceNow, Splunk, Microsoft Sentinel, Slack, an email digest or a signed webhook, and the CSV export gives you every data set.

See what an attacker sees

Your first 3 domain scans are free. Enter a domain and get verified findings, a Risk Score and reports.