Security
· 11 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.DSubresource IntegrityAction1 of 65 external resources have SRIFIX
| Tag | Domain | Integrity |
|---|---|---|
| <script> | connect.facebook.net | ✗ Missing |
| <script> | www.gstatic.com | ✓ Protected |
| <script> | www.recaptcha.net | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | accounts.google.com | ✗ Missing |
| <link> | accounts.google.com | ✗ Missing |
| <script> | connect.facebook.net | ✗ Missing |
| <link> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
| <script> | s.pinimg.com | ✗ Missing |
FEmail SecurityActionNo DMARCFIX
No DMARC record found
Without DMARC, email receivers have no policy for handling authentication failures from your domain.
Without DMARC, email receivers have no policy for handling authentication failures.
Without DMARC, anyone can send phishing emails using your domain name.
Learn more ▾ ▴
DMARC tells receiving mail servers what to do with email that fails SPF/DKIM checks for your domain. With a strict 'p=reject' policy, spoofed emails get bounced; without it they reach the inbox. Domains used in phishing campaigns lose deliverability and brand trust fast.
Source: DMARC.org / NIST
DPermissions-PolicyActionNo header setFIX
No Permissions-Policy header set.
Without this header, embedded iframes can request access to sensitive device features.
Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=()
BSecurity Headers6 of 10 headers properly configuredREVIEW
strict-origin-when-cross-originWeak Referrer-Policy values leak full URLs (with query params, tokens, IDs) to every third-party resource on the page.
Learn more ▾ ▴
Default referrer behavior shares the full referring URL with images, scripts, and other resources from third-party origins. If your URLs contain tokens, session IDs, or user emails (in query strings or paths), every third-party tracker gets them. Set `Referrer-Policy: strict-origin-when-cross-origin` (or stricter).
Source: MDN Referrer-Policy / W3C
Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.
geolocation=(), camera=(), microphone=()Permissions-Policy locks down browser APIs you don't use — without it, every page can request camera/mic/geolocation if XSS lands.
Learn more ▾ ▴
By default every page can request the camera, microphone, geolocation, payment APIs, and dozens more. Permissions-Policy turns off the ones you don't need so a future bug can't quietly start using them. It's a defense-in-depth header — one line, big surface reduction.
Source: MDN / W3C
COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.
same-originCOOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.
Learn more ▾ ▴
Cross-Origin-Opener-Policy: same-origin prevents cross-origin pages from sharing a browsing-context group with yours. This blocks cross-window references that enable Spectre-style timing attacks and tab-nabbing. Required if you want to enable SharedArrayBuffer.
Source: MDN / web.dev
COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.
require-corpCOEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.
Learn more ▾ ▴
Cross-Origin-Embedder-Policy: require-corp ensures every embedded resource (script, iframe, image) explicitly allows being loaded cross-origin. Combined with COOP, this enables the cross-origin-isolated context that unlocks SharedArrayBuffer, high-resolution timers, and other powerful APIs.
Source: MDN / web.dev
BContent Security Policy6 of 10 CSP checks passedREVIEW
'unsafe-inline' allows inline <script> tags, defeating CSP against XSS. Remove it and use nonces or hashes instead.
Unsafe value (unsafe-inline, unsafe-eval) in script-src defeats CSP's main protection — XSS injections can execute again.
Learn more ▾ ▴
unsafe-inline allows inline <script> tags; unsafe-eval allows eval() and similar. Both are necessary for some legacy code but explicitly dangerous. Migrate to nonces (per-page random tokens) or hashes (per-script SHA-256) instead.
Source: OWASP CSP / MDN
Set object-src to 'none' to prevent Flash/Java plugin exploits.
object-src 'none'object-src open in CSP allows Flash/PDF/plugin embedding — a now-deprecated attack vector that should be explicitly blocked.
Learn more ▾ ▴
object-src controls <object>, <embed>, and <applet> elements. Modern sites have no need for plugins; setting `object-src 'none'` blocks an entire class of legacy XSS vectors at zero cost. If your CSP missed it, add the directive.
Source: MDN CSP
This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.
upgrade-insecure-requestsWithout upgrade-insecure-requests, any HTTP subresource link survives as a mixed-content warning instead of auto-upgrading.
Learn more ▾ ▴
Adding `upgrade-insecure-requests` to your CSP turns every http:// subresource fetch into https:// at the browser layer. One-line defense against accidental mixed content from legacy links or third-party widgets.
Source: MDN CSP
Parsed Policy
BCORS ConfigurationNo CORS headersREVIEW
No CORS headers detected.
Cross-origin requests are blocked by browser same-origin policy.
Origin reflection test
Some servers mirror the request Origin header, which can be exploited. Test manually:
curl -sI -H "Origin: https://evil.com" <url> | grep -i access-control
Bsecurity.txtPublished with 0 contact(s)REVIEW
security.txt
A+TLS & CertificatesTLS 1.3, 7 checks passedPASS
HTTP/2 provides multiplexing and header compression for better performance.
HTTP/1.1 forces the browser to make sequential requests, multiplying latency on every page.
Learn more ▾ ▴
HTTP/2 (and HTTP/3) multiplex many requests over a single connection, eliminating head-of-line blocking. HTTP/1.1 forces the browser to either queue requests or open many parallel connections — both worse. Most modern web servers support HTTP/2 with one config line.
Source: MDN Web Docs
Certificate Chain
A+JS Library VulnerabilitiesNo known vulnerabilitiesPASS
No known JavaScript library vulnerabilities detected.
A+Information LeakageNo exposuresPASS
No sensitive files exposed — all paths returned 404.
| Path | Status | Category | Risk |
|---|---|---|---|
| /.git/HEAD | ✓ Not found | Version Control | — |
| /.git/config | ✓ Not found | Version Control | — |
| /.svn/entries | ✓ Not found | Version Control | — |
| /.env | ✓ Not found | Configuration | — |
| /.env.local | ✓ Not found | Configuration | — |
| /.env.production | ✓ Not found | Configuration | — |
| /wp-config.php | ✓ Not found | Configuration | — |
| /.htaccess | ✓ Not found | Configuration | — |
| /phpinfo.php | ✓ Not found | Debug | — |
| /server-status | ✓ Not found | Debug | — |
| /server-info | ✓ Not found | Debug | — |
| /.well-known/security.txt | ✗ Exposed | Security Policy | Info |