# BeaverCheck Audit Report — https://akj.io **Date:** May 12, 2026 **URL:** https://akj.io **Overall Grade:** B (86/100) **Report:** https://beavercheck.com/results/d23428df-e864-4bb8-9846-80df876e9ff3 ## Top Findings 1. **[CRITICAL]** Page body has only 168 chars of text -- likely empty / placeholder — Security > Empty Page Detection 2. **[WARNING]** DMARC policy is none — monitoring only — Security > Email Security 3. **[WARNING]** Permissions-Policy covers 3/10 high-risk features (30%) — Security > Permissions-Policy Granularity 4. **[WARNING]** Referrer-Policy has a weak value — Security > Security Headers 5. **[WARNING]** Referrer-Policy: `origin-when-cross-origin` -- leaky -- origin sent cross-origin even on protocol downgrade — Security > Referrer-Policy Strictness --- ## Lighthouse Scores | Category | Score | |----------|-------| | Performance | 100 | | Accessibility | 95 | | Best Practices | 96 | | SEO | 100 | --- ## Security ### Security Headers (A — 90/100) *8 of 10 headers properly configured* - **[PASS]** Strict-Transport-Security is properly configured - **[PASS]** X-Content-Type-Options is properly configured - **[PASS]** X-Frame-Options is properly configured - **[WARNING]** Referrer-Policy has a weak value - **[PASS]** Permissions-Policy is set - **[PASS]** Content-Security-Policy is present - **[PASS]** Cross-Origin-Opener-Policy is properly configured - **[PASS]** Cross-Origin-Embedder-Policy is set - **[WARNING]** X-Powered-By header reveals technology stack — This header discloses server technology (e.g. Express, PHP), helping attackers target known vulnerabilities. Remove it. - **[PASS]** Server header is present without version info - **[INFO]** Domain is not in the Chrome HSTS preload list (status: removed) — Submit your domain to hstspreload.org to close the trust-on-first-use gap. Requires a preload-ready HSTS header (max-age=31536000+, includeSubDomains, preload). ### Content Security Policy (A+ — 100/100) *9 of 10 CSP checks passed* - **[INFO]** Raw CSP policy - **[PASS]** default-src directive is set - **[PASS]** No 'unsafe-inline' in script source - **[PASS]** No 'unsafe-eval' in script source - **[PASS]** No wildcard in script source - **[PASS]** object-src is set to 'none' - **[PASS]** base-uri is properly restricted - **[PASS]** frame-ancestors directive is set - **[PASS]** form-action directive is set - **[PASS]** upgrade-insecure-requests is enabled ### TLS & Certificates (A+ — 100/100) *TLS 1.3, 7 checks passed* - **[PASS]** TLS 1.3 is used - **[PASS]** Strong cipher suite is used - **[INFO]** HTTP/2 is not negotiated — HTTP/2 provides multiplexing and header compression for better performance. - **[INFO]** OCSP stapling not enabled — Without stapling, the browser performs a separate OCSP roundtrip on first connection -- adding latency and leaking the visited host to the CA. Enable OCSP stapling on your TLS server. - **[PASS]** Certificate is valid (expires in 80 days) - **[PASS]** Certificate chain has 2 certificates - **[PASS]** Certificate uses modern signature algorithm - **[PASS]** Certificate covers 1 domain(s) - **[PASS]** Certificate is issued by a trusted CA ### Cookie Security (A+ — 100/100) *No cookies set — no cookie security risks* - **[PASS]** No cookies set — no cookie security risks ### Cookie Hygiene (A+ — 100/100) *No cookies set -- cookie-hygiene check is N/A* - **[PASS]** No cookies set ### WAF / Bot Protection (B — 75/100) *No WAF detected via response headers* - **[INFO]** No WAF detected — Response headers don't match any known WAF or bot-management product. Sites exposed to abuse (login, signup, payment) typically benefit from a WAF such as Cloudflare, Akamai, AWS WAF, or Imperva. ### security.txt (A+ — 100/100) *Vulnerability disclosure policy* - **[PASS]** security.txt found ### Cross-Origin Tab Safety (A+ — 100/100) *All 1 new-tab link(s) carry rel=noopener* - **[PASS]** All 1 new-tab link(s) carry rel=noopener ### CSP Inline-Style Readiness (B — 90/100) *4 inline style attribute(s) detected* - **[INFO]** 4 inline style attribute(s) detected — Each `style=""` attribute forces `style-src 'unsafe-inline'` in any Content-Security-Policy, which negates most of CSP's XSS-mitigation value. 4 inline style(s) is low. Affected element types include: div. Move styles to a stylesheet; use CSS custom properties for runtime-dynamic values; or adopt a nonce/hash CSP policy. Most teams take the stylesheet path because it's also a maintainability win. ### Trusted Types (XSS Sink Hardening) (B — 95/100) *Trusted Types not enabled* - **[INFO]** Trusted Types not enabled — Trusted Types (CSP3) is a Chrome 83+ defense that requires DOM-XSS sinks (innerHTML, document.write, eval, ...) to receive a typed-and-sanitized value rather than a raw string. Adding `Content-Security-Policy: require-trusted-types-for 'script'; trusted-types default` neutralizes most DOM-XSS even when a payload reaches a sink. Adoption is currently ~0.1% of pages so this is informational; a roll-out usually starts in report-only mode. ### Bot Challenge Detection (A+ — 100/100) *Scan reached real page content (no bot-protection interstitial)* - **[PASS]** No bot-protection interstitial detected -- the rest of the report reflects the real page ### Soft-404 Detection (A+ — 100/100) *No soft-404 patterns detected in page title or headings* - **[PASS]** No soft-404 patterns detected in page title or headings ### Empty Page Detection (F — 0/100) *1 empty-page signal(s) detected -- page may be a placeholder or have content-rendering bugs* - **[CRITICAL]** Page body has only 168 chars of text -- likely empty / placeholder — After HTML stripping, the page body contains 168 characters of text content. Below 200 chars almost always means: (1) the page is a placeholder that was never filled in, (2) JavaScript was supposed to render content but failed, (3) the page is a redirect / interstitial / wrapper that should have a real status code other than 200, or (4) it's a legitimately small page like a single-form login (in which case this finding is a false positive that confirms 'minimal content' is intentional). Review the page in a browser. If content is missing, the most common root cause is a JS-rendering pipeline that needs prerendering or server-side rendering for crawlers / scanners to capture content. ### Geo-Restriction Detection (A+ — 100/100) *No geo-restriction signals detected -- scan reached the page from an allowed region* - **[PASS]** No geo-restriction detected ### Maintenance Mode Detection (A+ — 100/100) *No maintenance-mode signals detected -- scan reached a normal page* - **[PASS]** No maintenance-mode signals detected ### Subresource Integrity Adoption (A+ — 100/100) *Page has no third-party scripts or stylesheets -- SRI not applicable* - **[PASS]** No third-party scripts or stylesheets to protect with SRI ### CORS Depth (A+ — 100/100) *No CORS response headers -- the resource is same-origin-only by browser default* - **[PASS]** No CORS response headers -- the resource is same-origin-only by browser default ### Permissions-Policy Granularity (D — 50/100) *30% high-risk feature coverage (3/10)* - **[WARNING]** Permissions-Policy covers 3/10 high-risk features (30%) — The Permissions-Policy header explicitly declares policies for 3/10 high-risk features. Covered: camera, microphone, geolocation Not declared (default-allow): payment, usb, serial, midi, accelerometer, gyroscope, magnetometer The non-declared features fall back to their spec-default policy (usually `self`), which means an XSS-injected or compromised iframe could request them. For features the page genuinely doesn't use, declare `feature=()` to fully close them. ### Referrer-Policy Strictness (D — 50/100) *Referrer-Policy is `origin-when-cross-origin` (leaky -- origin sent cross-origin even on protocol downgrade)* - **[WARNING]** Referrer-Policy: `origin-when-cross-origin` -- leaky -- origin sent cross-origin even on protocol downgrade — Same-origin requests get full URL; cross-origin gets only origin. Similar shape to the modern default BUT does NOT suppress Referer on HTTPS-to-HTTP downgrade -- the origin leaks even when the protocol is downgrading to HTTP. Switch to `strict-origin-when-cross-origin` for the same UX with no downgrade leak. ### Source Map Exposure (A+ — 100/100) *Source-map probe didn't run on this scan* - **[PASS]** Source-map probe didn't run on this scan ### HTML Version Disclosure (A+ — 100/100) *No software-version disclosures in HTML* - **[PASS]** No software-version disclosures in HTML ### Open Redirect Surface (A+ — 100/100) *No redirect-shaped query parameters in DOM links* - **[PASS]** No redirect-shaped query parameters in DOM links ### Auth Security (A+ — 100/100) *Page is not a login form -- auth-security checks are N/A* - **[PASS]** Page does not appear to be a login form ### Subdomain Inventory Exposure (A+ — 100/100) *No risky subdomain names in certificate SANs* - **[PASS]** No risky subdomain names in certificate SANs --- ## Advanced Security ### Subresource Integrity (A+ — 100/100) *No external resources* - **[PASS]** No external resources to protect ### JS Library Vulnerabilities (A+ — 100/100) *No known vulnerabilities* - **[PASS]** No known JavaScript library vulnerabilities detected ### Information Leakage (A+ — 100/100) *No exposures* - **[PASS]** security.txt is present — good practice - **[PASS]** No sensitive files exposed ### Email Security (D — 45/100) *DMARC: none, SPF: ?all, DKIM* - **[WARNING]** DMARC policy is none — monitoring only — This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject after monitoring DMARC reports. - **[WARNING]** SPF ends in ?all — provides no enforcement — ?all (neutral) and +all (pass-everything) make the SPF record decorative. Receivers will accept any sender. Switch to -all (hard fail) or ~all (soft fail). - **[PASS]** DKIM configured (selectors: fm1, fm2, fm3) - **[INFO]** MTA-STS not configured — MTA-STS forces inbound mail to use TLS, preventing downgrade attacks. Requires both a TXT record at _mta-sts. and a policy file at https://mta-sts./.well-known/mta-sts.txt. - **[INFO]** TLS-RPT not configured — TLS-RPT (RFC 8460) lets MTAs report TLS-handshake failures, so you can detect and fix MTA-STS misconfigurations. Add a TXT record at _smtp._tls.. - **[INFO]** BIMI not configured — BIMI (Brand Indicators for Message Identification) lets supporting clients (Gmail, Apple Mail, Yahoo) display your verified logo next to your messages. Optional but raises trust signals. Requires DMARC at p=quarantine or p=reject to be honored. ### API Surface (A+ — 100/100) *No API specs or GraphQL introspection found (probed 11 candidate path(s))* - **[PASS]** No API specs or GraphQL introspection found (probed 11 path(s)) ### Permissions-Policy (B — 80/100) *4 directives, 2 missing* - **[PASS]** camera=() — blocked for all origins - **[PASS]** microphone=() — blocked for all origins - **[PASS]** geolocation=() — blocked for all origins - **[PASS]** browsing-topics=() — blocked for all origins - **[INFO]** payment not restricted — Consider adding payment=() to block payment access from embedded content. - **[INFO]** usb not restricted — Consider adding usb=() to block usb access from embedded content. ### CORS Configuration (B — 80/100) *No CORS headers* - **[PASS]** No CORS headers present — secure default --- ## Performance ### Page Weight Budget (A+ — 100/100) *45 KB transferred, 15 requests* - **[PASS]** Page weighs 66 KB (45 KB transferred) - **[PASS]** 15 HTTP requests - **[INFO]** Estimated 0.01 g CO2 per page load ### Third-Party Impact (A+ — 100/100) *No third-party resources* - **[PASS]** No third-party resources detected ### Text Compression (A+ — 100/100) *All text resources are compressed* - **[PASS]** All text resources are compressed ### Image Optimization (A+ — 100/100) *No images on this page* - **[PASS]** No images on this page ### JS Execution Cost (A+ — 100/100) *281ms total JS execution* - **[INFO]** Unattributable: 149ms CPU time - **[INFO]** https://akj.io/: 132ms CPU time - **[WARNING]** Third-party scripts: 149ms (53% of total) ### Font Loading (A+ — 100/100) *2 fonts (1 KB)* - **[INFO]** 2 font(s) use font-display: swap (FOUT risk but functional) ### JS Bundles (A+ — 100/100) *9 scripts, 0 KB unused* ### Resource Caching (A+ — 100/100) *All resources properly cached* - **[PASS]** No caching issues found ### Critical Rendering Path (A+ — 100/100) *No render-blocking resources* - **[PASS]** No render-blocking resources detected ### Resource Hints (A+ — 100/100) *No optimization needed* - **[PASS]** No resource hint issues ### HTTP/3 (QUIC) (B — 75/100) *HTTP/3 not advertised* - **[INFO]** HTTP/3 (QUIC) is not advertised — HTTP/3 isn't advertised via Alt-Svc and the worker didn't negotiate h3. HTTP/3 reduces handshake latency (1-RTT instead of 2-3 RTTs) and is more resilient on lossy connections. Most modern CDNs (Cloudflare, Fastly, AWS CloudFront, Google Cloud CDN) support HTTP/3 with a single config switch -- consider enabling for mobile-heavy workloads. ### Compression Algorithm (C — 70/100) *Main response served uncompressed* - **[INFO]** Main HTML response has no Content-Encoding (uncompressed) — The main HTML document is served without compression. The Text Compression section above lists the broader picture; for the main response specifically, even gzip would shave ~70-80% off most text payloads. ### LCP Image Preload (A+ — 100/100) *LCP preload audit not available* - **[PASS]** LCP image preload audit not available for this scan ### Main HTML Cache-Control (A+ — 100/100) *Main HTML uses no-store -- correct for sensitive/dynamic content* - **[PASS]** Main HTML uses no-store -- correct for sensitive/dynamic content ### Server-Timing Observability (B — 85/100) *No Server-Timing header found* - **[INFO]** No Server-Timing header found — Server-Timing exposes backend timing breakdowns to browser DevTools (e.g., `db: 45ms; render: 120ms; cache: 2ms`). Useful for diagnosing slow pages without backend log access. Most modern frameworks (Next.js, Cloudflare Workers, Fastly) emit it automatically; absence on a managed platform usually means telemetry headers are stripped at the edge. ### Server Response Intelligence (A+ — 95/100) *2 server-response signal(s) detected* - **[PASS]** `Vary` header declared: rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch — The page declares a `Vary` header, telling downstream caches which request headers the response varies on. Critical for content-negotiated responses (compression, language, cookies, device class). - **[INFO]** No `ETag` or `Last-Modified` -- conditional GET not supported — Without either header, browsers can't issue conditional GETs and refresh always re-downloads the full response body even when nothing changed. Add `ETag: ""` (or `Last-Modified: `) on cacheable responses; the server returns 304 Not Modified when the client's cached copy is still valid, saving bandwidth. ### Page Weight Inventory (A+ — 100/100) *15 resources · 45 KB · 0 KB savings available* - **[PASS]** Within 1MB page-weight target ### Render-Blocking Resources (A+ — 100/100) *No render-blocking resources detected* - **[PASS]** No render-blocking resources detected in ### Third-Party Resources (A+ — 100/100) *No third-party resources detected* ### JavaScript Blocking (A+ — 100/100) *No render-blocking JS or document.write usage detected* - **[PASS]** No JavaScript blocking issues detected ### CSS Performance Depth (A+ — 100/100) *No CSS performance depth issues detected* - **[PASS]** No CSS performance depth issues detected --- ## Content Quality ### Links (A+ — 100/100) *1 links checked, 1 healthy, 0 broken* - **[PASS]** 1 of 1 links are healthy ### Mixed Content (A+ — 100/100) *No mixed content detected — all resources use HTTPS.* - **[PASS]** No mixed content detected — all resources use HTTPS ### Open Graph (F — 0/100) *No Open Graph tags found — social sharing previews will be generic.* - **[WARNING]** No Open Graph meta tags found — Without og:title, og:description, and og:image, social media platforms will generate a generic preview when your page is shared. ### Open Graph / Twitter Card Depth (A+ — 100/100) *No OG image or Twitter card set -- depth check is N/A (presence covered by Open Graph section)* - **[PASS]** No OG image / Twitter card to evaluate ### Structured Data (C — 40/100) *No structured data (JSON-LD) found.* - **[INFO]** No structured data (JSON-LD) found — Adding structured data helps search engines understand your content and can enable rich results. ### Rich Results Eligibility (C — 75/100) *No JSON-LD found -- no rich-result eligibility* - **[INFO]** No JSON-LD structured data on the page — No `