Technical auditing implementation for automated inspection of HTTP response headers, TLS protocol configurations, and cookie policies.
This application provides a strictly non-intrusive security analysis of public web assets. It focuses on the evaluation of security configuration baselines, compliance with RFCs, and alignment with OWASP standards. No state-changing requests, exploitation attempts, or active payloads are performed.
- HTTP Security Headers: Inspection of HSTS, CSP, X-Frame-Options, X-Content-Type-Options, and Referrer-Policy.
- TLS Configuration: Posture assessment of server-supported protocols and cipher suites.
- Cookie Security Attributes: Baseline review of
Secure,HttpOnly, andSameSiteflags. - Configuration Artifacts: Detection of metadata exposed in HTTP response parameters.
- Frontend: React 18, Vite, Axios
- Backend: Node.js, Express
- UI Architecture: Centralized CSS Token System, CSS Grid/Flexbox layout with viewport-aware sticky contextual navigation.
This application implements defensive programming principles aligned with the OWASP API Security Top 10 (2023):
- SSRF Prevention (API3:2023): A custom native DNS resolution interceptor drops requests to internal networks (e.g.,
169.254.169.254,10.0.0.0/8,192.168.0.0/16,127.0.0.1). The server refuses to act as a proxy for internal network enumeration. - Rate Limiting (API4:2023): Implements
express-rate-limitto strictly constrain IP-bound execution, mitigating brute-force polling and DoS vectors. - Security Header Injection (API7:2023): Utilizes
helmetto wrap API responses in XSS, HSTS, and MIME-sniffing mitigations. - CORS Hardening: Strict Origin binding limits cross-origin exposure of the API backend.
- Backend Configuration:
cd backend npm install npm run dev - Frontend Configuration:
cd frontend npm install npm run dev
After initialization, the frontend is accessible at http://localhost:5174 (or the evaluated Vite port).
This project is constrained to passive analysis:
- No Payload Injection: Observes server responses only.
- No Active Exploitation: Focuses entirely on configuration state.
- Factual Reporting: Delivers technical findings based on explicit RFC divergence.
This tool is developed for research and authorized security inspections. It performs passive metadata extraction and does not impact the availability or integrity of target infrastructure.