Security
· 13 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.FSecurity HeadersAction4 of 10 headers properly configuredFIX
Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.
max-age=31536000; includeSubDomainsWithout HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.
Learn more ▾ ▴
HSTS tells browsers 'never speak HTTP to this domain again.' Without it, a network attacker (public WiFi, malicious ISP, hostile DNS) intercepts the first HTTP attempt and serves a downgraded version of your site. One header, big surface reduction.
Source: RFC 6797 / OWASP
This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.
DENYWithout frame protection, your site can be embedded in a hostile page and used for clickjacking.
Learn more ▾ ▴
Clickjacking overlays your site under a transparent malicious page so users click invisible buttons. Setting X-Frame-Options: DENY (or a modern frame-ancestors CSP directive) blocks the embedding entirely. There's almost never a legitimate reason to allow it.
Source: OWASP / MDN
Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.
strict-origin-when-cross-originDefault browser behavior leaks full URLs (including query params and tokens) to every third-party resource — set a strict policy.
Learn more ▾ ▴
Without a Referrer-Policy header, browsers send the full referring URL with images, scripts, and fonts loaded from third-party origins. URLs containing tokens, user IDs, or session params end up in third-party logs. Set `Referrer-Policy: strict-origin-when-cross-origin` (or stricter) to limit leakage.
Source: MDN / 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
FSubresource IntegrityAction0 of 42 external resources have SRIFIX
| Tag | Domain | Integrity |
|---|---|---|
| <script> | rules.quantcount.com | ✗ Missing |
| <script> | connect.facebook.net | ✗ Missing |
| <script> | platform.twitter.com | ✗ Missing |
| <script> | connect.facebook.net | ✗ Missing |
| <script> | scdn.cxense.com | ✗ Missing |
| <script> | sb.scorecardresearch.com | ✗ Missing |
| <script> | secure.quantserve.com | ✗ Missing |
| <script> | clickiocmp.com | ✗ Missing |
| <link> | cdn.allafrica.com | ✗ Missing |
| <link> | cdn.allafrica.com | ✗ Missing |
| <link> | cdn.allafrica.com | ✗ Missing |
| <link> | cdn.allafrica.com | ✗ Missing |
| <link> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <link> | cdn.allafrica.com | ✗ Missing |
| <link> | cdn.allafrica.com | ✗ Missing |
| <link> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <link> | cdn.allafrica.com | ✗ Missing |
| <script> | clickiocmp.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | s.clickiocdn.com | ✗ Missing |
| <script> | securepubads.g.doubleclick.net | ✗ Missing |
| <script> | www.google-analytics.com | ✗ Missing |
| <script> | www.googletagmanager.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | securepubads.g.doubleclick.net | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
| <script> | cdn.allafrica.com | ✗ Missing |
DEmail SecurityActionDMARC: noneFIX
This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject.
DMARC p=none collects reports but doesn't actually block spoofed mail — phishing emails still reach inboxes.
Learn more ▾ ▴
DMARC's three policies are p=none (monitor only), p=quarantine (mark as spam), and p=reject (bounce). Most domains start at p=none to gather data, but stay there forever, leaving spoofers unblocked. After 30 days of clean DMARC reports, graduate to p=quarantine, then p=reject.
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=()
Dsecurity.txtActionNo /.well-known/security.txt publishedFIX
security.txt
No security.txt found at /.well-known/security.txt
BContent Security Policy2 of 10 CSP checks passedREVIEW
default-src provides a fallback for other directives. Set it to restrict default resource loading.
default-src 'self'Security gaps expose your site and users to attacks, eroding trust.
Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
base-uri 'self'Missing base-uri in CSP leaves a base-tag injection attack path open even on otherwise strict policies.
Learn more ▾ ▴
A common omission: developers add CSP for script-src and frame-ancestors but forget base-uri. The result is a CSP that looks strict but lets an attacker rewrite every URL on the page via <base href>. Add `base-uri 'self'` to close the gap.
Source: MDN CSP
form-action restricts where forms can submit data, preventing form hijacking.
form-action 'self'Security gaps expose your site and users to attacks, eroding trust.
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
CKnown vulnerability matchesAction17 known vulnerability match(es) against detected techREVIEW
Known Vulnerabilities
| Library | Version | Severity | Summary | Fixed In |
|---|---|---|---|---|
| Bootstrap | 3.3.7 | medium | In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute. | 3.4.0 |
| Bootstrap | 3.3.7 | medium | XSS in data-container property of tooltip | 3.4.0 |
| Bootstrap | 3.3.7 | medium | In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property. | 3.4.0 |
| Bootstrap | 3.3.7 | medium | XSS in data-target property of scrollspy | 3.4.0 |
| Bootstrap | 3.3.7 | medium | XSS in collapse data-parent attribute | 3.4.0 |
| Bootstrap | 3.3.7 | medium | XSS in data-container property of tooltip | 3.4.0 |
| Bootstrap | 3.3.7 | medium | XSS is possible in the data-target attribute. | 3.4.0 |
| Bootstrap | 3.3.7 | medium | Bootstrap Cross-Site Scripting (XSS) vulnerability for data-* attributes | 3.4.1 |
| Bootstrap | 3.3.7 | medium | XSS in data-template, data-content and data-title properties of tooltip/popover | 3.4.1 |
| Bootstrap | 3.3.7 | medium | Bootstrap Cross-Site Scripting (XSS) vulnerability for data-* attributes | 3.4.2 |
| Bootstrap | 3.3.7 | low | Bootstrap before 4.0.0 is end-of-life and no longer maintained. | 3.999.999 |
| jQuery | 1.9.1 | medium | 3rd party CORS request may execute | 1.12.0 |
| jQuery | 1.9.1 | medium | parseHTML() executes scripts in event handlers | 2.2.0 |
| jQuery | 1.9.1 | low | jQuery 1.x and 2.x are End-of-Life and no longer receiving security updates | 2.999.999 |
| jQuery | 1.9.1 | medium | jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution | 3.4.0 |
| jQuery | 1.9.1 | medium | passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. | 3.5.0 |
| jQuery | 1.9.1 | medium | Regex in its jQuery.htmlPrefilter sometimes may introduce XSS | 3.5.0 |
BTransport SecurityHTTP/3, HSTS, and TLS version analysisREVIEW
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 | ✓ Not found | Security Policy | — |