Technologies
The publicly observable stack: CMS, frameworks, web server, CDN and third-party libraries.
External security assessment
Get a clear report on the technologies visible on your website, external security signals and areas your development team should validate.
Enter the domain and your contact details. The review starts only after the right to request it is confirmed.
The publicly observable stack: CMS, frameworks, web server, CDN and third-party libraries.
HTTPS, TLS, HTTP headers, cookies and other externally available configuration signals.
Matches between recognised technologies, public security advisories and known CVEs.
Prioritised checks and recommendations on when an authorised audit or remediation is needed.
This is not a penetration test and not an attempt to access a system. We analyse only what the website exposes to the public internet.
We review the submitted domain and standard public web-server responses. We do not use credentials or request restricted areas.
We match observable signals with technology databases. Detection can be incomplete, so every technology is marked as an assumption or a confirmed external signal.
When a publicly recognised component is associated with a CVE, we flag it as a potential area to validate — not as proof of a vulnerability.
We give a clear priority: what a site owner can validate and what requires an authorised technical audit with agreed access and scope.
If the external assessment identifies a reason to investigate, we will agree an authorised audit scope: access, scenarios, constraints and reporting format.
If the external assessment identifies a reason to investigate, we will agree an authorised audit scope: access, scenarios, constraints and reporting format.
Request assessment