What is a website security checker?

A website security checker is an automated web risk assessment tool that scans live web applications for external security risks, OWASP Top 10 vulnerabilities, misconfigured HTTP headers, exposed API secrets, and server data leaks. Igris Radar acts as a complete website security checker and vulnerability scanner with severity-ranked findings and AI remediation steps.

What is Subdomain Radar and how does it detect takeover risks?

Subdomain Radar enumerates your public subdomains from Certificate Transparency (CT) logs and DNS records, then automatically audits each subdomain for takeover risks—such as dangling CNAME records pointing to decommissioned S3 buckets, Heroku apps, or GitHub Pages.

Does it detect vulnerable JavaScript libraries?

Yes. We fingerprint the exact version of every JavaScript library your page loads and check each one against the OSV vulnerability database, which aggregates GitHub, npm and other advisories. You get the specific CVEs and the version to upgrade to - not a generic "update your dependencies."

What does the AI security analysis do?

After the scan, an AI analyst reviews your findings and streams back a plain-language report: an executive summary and prioritized risks on every paid tier, plus attack-chain threat modeling, OWASP Top 10 mapping, copy-paste remediation code, and GDPR / PCI compliance readiness on the Pro plan. It turns a list of findings into a clear plan of what to fix first and why.

Is this a penetration test?

No. A penetration test is a manual engagement by security experts. Igris Radar is a continuous, automated security audit - the layer you run weekly to catch configuration drift, leaked keys, vulnerable dependencies, and missing headers between deeper engagements.

Do I need to install anything?

No agents, no DNS changes, no code snippets. Enter a URL and the scanner analyses everything visible from the outside - the same vantage point an attacker has.

Headers Security

critical Severity

Free Check

Content Security Policy (CSP)

Restricts sources from which scripts, styles, and assets can load to prevent XSS and code injection.

Test Your Website for Content Security Policy (CSP)

Run this check along with 90+ automated tests across your domain.

Why It Matters

Cross-Site Scripting (XSS) allows attackers to steal user session cookies, log keystrokes, and execute unauthorized actions. A strict CSP provides essential defense-in-depth even if an input sanitization flaw exists.

How We Check This

We evaluate Content-Security-Policy headers for missing directives (default-src, script-src, object-src, frame-ancestors) and dangerous wildcards or 'unsafe-inline' tokens.

How to Fix & Implement

Copy-paste configuration blocks tailored for your web server or edge proxy.

nginx snippet

add_header Content-Security-Policy "default-src 'self'; script-src 'self' 'nonce-$request_id'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self' https:; frame-ancestors 'none'; base-uri 'self';" always;

Frequently Asked Questions

Why is unsafe-inline flagged in CSP?

Because it allows malicious scripts injected into DOM innerHTML or HTML attributes to run without restriction.

Related Security Checks