Skip to main content

Scanning Tools

Each tool runs in its own container and writes output to a dedicated results table.

Tool Matrix

ToolPurposeResult Table
probeendpoint metadata, technologies, network/server detailsprobe_results
domaindomain metadata, DNS records, passive subdomainsdomain_results
whoisIP whois enrichmentwhois_results
sslcertificate metadata and expiryssl_results
seoTypeScript SEO audit and scoring (@seomator/seo-audit)seo_results
wcagaccessibility checks + screenshotswcag_results
securityaggregated vulnerability findings and scoresecurity_results
stressload testing and latency metricsstress_results
mailDNS based email healthmail_results

Execution Notes

  • probe executes first and gates downstream queue creation.
  • WCAG may fan out by device profile.
  • Queue retries/backoff are managed by orchestrator.

Expected Runtime

These reference times were measured on a VPS with 4 AMD EPYC 9645 cores, 8GB RAM, and NVMe storage. Target behavior and network latency can change results substantially.

ToolExpected time
domain37s
mail14s
probe4s
security10m
seo13s
ssl3s
stress37s
wcag12s per device
whois5s per IP

Data Quality Notes

  • Geo lookup is persisted at probe time to avoid read-time external API calls.
  • DNS records are stored in structured objects keyed by record type.
  • Security scoring depends on SECURITY_SCORE_THRESHOLD.
  • Security runtime is tuned through SECURITY_NUCLEI_*, SECURITY_NIKTO_*, and SECURITY_WAPITI_* variables. The production defaults keep scans web-focused and bounded; higher values may recover slower network-fingerprint findings.
  • WCAG can be narrowed with WCAG_RUN_ONLY or WCAG_EXCLUDE_RULES.
  • Stress tests are controlled with STRESS_* variables such as rate, duration, method, timeout, workers, headers, body, and latency warning threshold.