From L0 surface analysis to L3 in-depth content analysis, signals build up at each stage to assess risk.
URLs and hyperlinks in email bodies and documents are followed in Hyper Sandbox and judged by behavior.
From a first-pass check with no network requests to in-depth content analysis, signals build up at each stage for a precise risk assessment.
See in the log on the right which scanner checks each layer, from L0 to L3.
Instant analysis from the URL string alone, with no network requests.
Surface ScannerStatic URL structure parsing and encoding pattern analysisNetwork metadata inspection layer that sends no request to the target URL.
Domain ScannerVerifies domain age and registrant trust; analyzes hosting environment and IP geolocationNetwork-layer verification after a server connection is established. Inspects HTTP traffic and the certificate chain.
Header ScannerDetects anomalies in HTTP headersCert ScannerChecks trust of the SSL/TLS certificate chainIn-depth content analysis through sandbox rendering. Inspects the DOM tree and script behavior.
Html ScannerInspects the DOM tree for suspicious tag patternsJS ScannerJavaScript deobfuscation and behavior analysisSurface ScannerStatic URL structure parsing and encoding pattern analysisRUNDomain ScannerVerifies domain age and registrant trust; analyzes hosting environment and IP geolocationHeader ScannerDetects anomalies in HTTP headersCert ScannerChecks trust of the SSL/TLS certificate chainHtml ScannerInspects the DOM tree for suspicious tag patternsJS ScannerJavaScript deobfuscation and behavior analysisWhy multiple layers? Filtering threats step by step, from surface analysis at L0 to deep analysis at L3, uses resources efficiently and raises detection accuracy.
We actually follow the URLs behind hyperlinks in a document and analyze the behavior of the pages they lead to before giving a verdict.
In this example PDF, we found a fake CAPTCHA (FakeCaptchaOverlay) on the followed page, analyzed the additional URLs, and judged it Risk 8 · malicious.
File names · URLs · risk · events · techniques · time: example based on a sample analysis report (analysis flow)
Buttons, hyperlinks and macros in documents are forced to run, drawing out malicious behavior that hides until a click.
Followed URLs stay in the report as IOCs; if malicious, they are blocked, or CDR removes only the URLs and hyperlinks.
Detection case · We ran a hidden hyperlink in an APT37 ‘Artemis’ HWP document and caught concealed PowerShell activity.
This technology was selected as a 2025 KISA excellent information security technology.