Skip to content
AEGIS

How it works

A short tour of the product, then the details of what happens during a scan.
scroll to explore ↓
  1. 1
  2. 2
  3. 3
  4. 4
  5. 5
  6. 6
step 01 / 06demo · illustrative
shop.example.com
BLOCKED_TARGET — 169.254.169.254 is a link-local address
Arcade · 30 seconds

Packet defense.

Click malicious packets before they reach your server. Let normal traffic through. (Just a game — Aegis itself never attacks anything.)

score 0shield ▮▮▮▮▮time 30sbest 0

red = malicious · green = normal traffic

Inside a scan

    01
    Target
    02
    Domain
    03
    HTTPS / TLS
    04
    Security headers
    05
    Cookies
    06
    DNS
    07
    Exposure
    08
    Risk analysis
    09
    Final score

Target validation

The hostname is resolved server-side. If any address is private, loopback, link-local, multicast, reserved or a cloud-metadata endpoint, the scan stops as BLOCKED_TARGET.

Observation & checks

Aegis makes a small number of GET requests, one TLS handshake and public DNS queries, then evaluates each registered check against those observations and stores the evidence.

Risk & score

New issues become findings, fixed ones are resolved automatically, and the score is recalculated: 100 minus 25/15/7/2/0 per open critical/high/medium/low/info finding.

Try it on your website