# BeaverCheck Audit Report — https://scenegenerator.io **Date:** August 15, 2026 **URL:** https://scenegenerator.io **Overall Grade:** B (87/100) **Report:** https://beavercheck.com/results/31fb7656-e78e-48a9-8c14-80a8ed0dc3e2 ## Top Findings 1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers 2. **[CRITICAL]** HSTS header is missing — Security > Security Headers 3. **[CRITICAL]** No Content-Security-Policy header found — Security > Content Security Policy 4. **[WARNING]** Compressed response missing `Vary` header — Performance > Server Response Intelligence 5. **[WARNING]** Cross-Origin-Embedder-Policy header is missing — Security > Security Headers --- ## Lighthouse Scores | Category | Score | |----------|-------| | Performance | 79 | | Accessibility | 100 | | Best Practices | 96 | | SEO | 100 | --- ## Security ### Security Headers (F — 10/100) *2 of 10 headers properly configured* - **[CRITICAL]** HSTS header is missing — Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year. - **[WARNING]** X-Content-Type-Options header is missing — This header prevents MIME-type sniffing, which can lead to XSS attacks. Set it to 'nosniff'. - **[WARNING]** X-Frame-Options header is missing — This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN. - **[WARNING]** Referrer-Policy header is missing — Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter. - **[WARNING]** Permissions-Policy header is missing — Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features. - **[CRITICAL]** Content-Security-Policy header is missing — CSP is the most important header for preventing XSS attacks. See the CSP section for detailed analysis. - **[WARNING]** Cross-Origin-Opener-Policy header is missing — COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'. - **[WARNING]** Cross-Origin-Embedder-Policy header is missing — COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers. - **[PASS]** X-Powered-By header is not present - **[PASS]** Server header is present without version info - **[INFO]** Domain is not in the Chrome HSTS preload list (status: unknown) — 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 (F — 0/100) *No enforcing CSP policy found* - **[CRITICAL]** No Content-Security-Policy header found — CSP is the most effective defense against XSS attacks. Add a Content-Security-Policy header to restrict resource loading. ### 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 77 days) - **[PASS]** Certificate chain has 3 certificates - **[PASS]** Certificate uses modern signature algorithm - **[PASS]** Certificate covers 2 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 (A — 90/100) *Cloudflare* - **[PASS]** Cloudflare detected — Detected via: cf-ray: a2b5317c7ab446a0-CDG ### security.txt (C — 60/100) *No security.txt file found* - **[INFO]** No security.txt file found — security.txt (RFC 9116) provides a standardized way for security researchers to report vulnerabilities. Create one at /.well-known/security.txt with at least a Contact field. ### Cross-Origin Tab Safety (A+ — 100/100) *No new-tab links found -- no tabnabbing surface* - **[PASS]** No new-tab links present ### CSP Inline-Style Readiness (A+ — 100/100) *No inline style attributes -- strict CSP is feasible* - **[PASS]** No inline style attributes detected ### Trusted Types (XSS Sink Hardening) (A+ — 100/100) *No CSP header -- Trusted Types check is N/A* - **[PASS]** No CSP header found -- Trusted Types check is N/A ### 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 (A+ — 100/100) *Page has substantive body text and no placeholder / template-leak signals* - **[PASS]** Page has substantive body text and no placeholder / template-leak signals ### 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 (C — 60/100) *No Permissions-Policy header set -- powerful features (camera / microphone / geolocation / payment / USB) default to allow-on-same-origin* - **[WARNING]** Permissions-Policy header not set -- features default to allow-on-same-origin — Without a `Permissions-Policy` (or legacy `Feature-Policy`) header, every powerful browser feature defaults to its spec default policy (typically `self`). A third-party iframe injected via XSS or a misconfigured embed can still request access to the user's camera, microphone, geolocation, payment APIs, USB devices, etc. Explicitly deny features the page doesn't need: ``` Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), accelerometer=(), gyroscope=() ``` Features the page legitimately uses can stay enabled with `feature=(self)`. ### Referrer-Policy Strictness (B — 75/100) *Referrer-Policy header not set -- browser default applies (modern: strict-origin-when-cross-origin; legacy browsers: no-referrer-when-downgrade)* - **[INFO]** Referrer-Policy header not set -- browser default applies — Without an explicit `Referrer-Policy` header, the browser falls back to its default policy. Modern browsers (Chrome 85+, Firefox 87+, Safari 15+) default to `strict-origin-when-cross-origin`, which is privacy-safe. Legacy browsers default to the leaky `no-referrer-when-downgrade`, which sends the full URL (including path + query) on cross-origin HTTPS-to-HTTPS requests. Set an explicit header to ensure consistent behavior: ``` Referrer-Policy: strict-origin-when-cross-origin ``` This matches the modern browser default and is privacy-safe without breaking referrer-based same-origin analytics. ### Source Map Exposure (A+ — 100/100) *No source maps accessible (probed 1 candidate URL(s))* - **[PASS]** No source maps accessible across 1 probed candidate(s) ### 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* - **[INFO]** No security.txt found — Consider adding a security.txt at /.well-known/security.txt. - **[PASS]** No sensitive files exposed ### Email Security (F — 0/100) *no DMARC, SPF: PERMERROR* - **[WARNING]** No DMARC record found — Without DMARC, email receivers have no policy for handling authentication failures. Add a TXT record at _dmarc. starting with v=DMARC1. - **[WARNING]** Multiple SPF records found at apex (PERMERROR) — RFC 7208 forbids more than one v=spf1 record per domain. Receivers reject SPF evaluation entirely when this happens, breaking your authentication. Merge into a single record. - **[INFO]** No DKIM detected via common selectors — DKIM signs outbound mail to prove origin. We probed common selectors (default, google, selector1, etc.) without finding a record. If you use a non-standard selector, this is a false negative. - **[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 (D — 40/100) *No header set* - **[WARNING]** No Permissions-Policy header — Consider adding a Permissions-Policy header to restrict browser feature access from embedded content. ### CORS Configuration (B — 80/100) *No CORS headers* - **[PASS]** No CORS headers present — secure default --- ## Performance ### Page Weight Budget (F — 36/100) *2.7 MB transferred, 68 requests* - **[WARNING]** Page weighs 4.1 MB (2.7 MB transferred) - **[WARNING]** Images are 1.9 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size. - **[WARNING]** JavaScript is 658 KB — consider code splitting or lazy loading — Large JavaScript bundles delay interactivity. Split code by route or defer non-critical scripts. - **[INFO]** 68 HTTP requests - **[INFO]** Estimated 0.57 g CO2 per page load ### Third-Party Impact (A+ — 100/100) *10% third-party, 0 ms blocking* - **[INFO]** Third-party code accounts for 10% of page weight (263.7 KiB of 2.7 MiB) - **[PASS]** Third-party blocking time is low (0 ms) ### Text Compression (A+ — 100/100) *All text resources are compressed* - **[PASS]** All text resources are compressed ### Image Optimization (A+ — 95/100) *16 images, 0 KB saveable* - **[PASS]** All images are well-optimized ### JS Execution Cost (C — 60/100) *1492ms total JS execution* - **[WARNING]** https://scenegenerator.io/assets/index-C8QKsFnE.js: 454ms CPU time - **[WARNING]** https://scenegenerator.io/: 420ms CPU time - **[WARNING]** Unattributable: 404ms CPU time - **[INFO]** https://www.googletagmanager.com/gtag/js?id=G-WBWN...: 149ms CPU time - **[INFO]** https://accounts.google.com/gsi/client: 64ms CPU time - **[INFO]** Third-party scripts: 214ms (14% of total) ### Font Loading (A+ — 100/100) *2 fonts (77 KB)* - **[INFO]** 2 font(s) use font-display: swap (FOUT risk but functional) ### JS Bundles (C — 60/100) *43 scripts, 294 KB unused* - **[WARNING]** https://www.googletagmanager.com/gtag/js?id=G-WBWN...: 91 KB unused (55%) — Consider code splitting or tree shaking to reduce unused code. - **[WARNING]** https://scenegenerator.io/assets/index-C8QKsFnE.js: 74 KB unused (51%) — Consider code splitting or tree shaking to reduce unused code. - **[WARNING]** https://accounts.google.com/gsi/client: 73 KB unused (75%) — Consider code splitting or tree shaking to reduce unused code. - **[WARNING]** https://scenegenerator.io/assets/messages-AhUplvUH...: 56 KB unused (63%) — Consider code splitting or tree shaking to reduce unused code. - **[INFO]** Total unused JavaScript: 294 KB ### 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) *5 hints, 0 missing preconnects* - **[PASS]** Page uses 5 resource hint(s) ### HTTP/3 (QUIC) (A+ — 100/100) *HTTP/3 advertised via Alt-Svc* - **[PASS]** HTTP/3 (QUIC) is supported — First-load mobile users on cellular networks see meaningful latency improvements with HTTP/3. The QUIC transport collapses TLS + TCP handshakes into one and recovers faster from packet loss. ### Compression Algorithm (A+ — 100/100) *Main response uses brotli* - **[PASS]** Main HTML response uses brotli (Content-Encoding: br) — Brotli is the best text-compression algorithm for general use, ~20% smaller than gzip on average (40% on smaller files). Modern browsers all support it. ### 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 (B — 80/100) *No Cache-Control header on main HTML response* - **[INFO]** Main HTML response has no Cache-Control header — Without an explicit Cache-Control, browsers fall back to heuristic caching (~10% of Last-Modified age). Set `Cache-Control: no-cache` or `max-age=300` for HTML to control freshness explicitly -- prevents stale auth state and SPA shell drift. ### 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 — 87/100) *2 server-response signal(s) detected* - **[WARNING]** Compressed response missing `Vary` header — The page is served with `Content-Encoding: br` but has no `Vary` header. Without `Vary: Accept-Encoding`, intermediary caches (corporate proxies, ISP caches) may serve the compressed variant to clients that didn't send the matching `Accept-Encoding` -- the client sees garbled bytes. Add `Vary: Accept-Encoding` whenever the response is conditionally compressed. - **[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 (C — 55/100) *68 resources · 2.7 MB · 294 KB savings available* - **[WARNING]** Page weight 2.7 MB exceeds 1 MB target by 1.7 MB - **[INFO]** ~294 KB of savings available - **[INFO]** 3 third-party resources (10% of weight) - **[INFO]** 2 resources over 200KB ### 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) *98 links checked, 98 healthy, 0 broken* - **[PASS]** 98 of 98 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 (A — 95/100) *Open Graph tags are well configured for social sharing.* - **[INFO]** Missing og:site_name — The og:site_name tag displays the website name in social previews. ### Open Graph / Twitter Card Depth (A+ — 100/100) *OG image dimensions and Twitter card configuration look healthy* - **[PASS]** OG/Twitter Card depth is clean -- dimensions, card type, and inheritance all valid ### Structured Data (A+ — 100/100) *1 JSON-LD block(s) found — structured data is well configured.* - **[PASS]** Custom type "WebApplication" — unable to validate specific properties ### Rich Results Eligibility (A+ — 100/100) *1 JSON-LD block(s) declaring 1 schema type(s)* - **[PASS]** 1 rich-result schema type(s) declared — Inventory of structured-data types on the page (each may unlock a different SERP feature): WebApplication Search engines decide whether to render rich results based on content quality + page-level signals; declaring the schema is necessary but not sufficient. ### Image Optimization (F — 45/100) *5 issues found across 36 images* - **[WARNING]** 7 images significantly larger than display size — Resizing to display dimensions could save approximately 1069 KB. - **[WARNING]** 29 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes. - **[INFO]** 5 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight. - **[WARNING]** Total image weight: 1828 KB (1.8 MB) — Consider compressing images, using modern formats, and serving appropriately sized images. - **[INFO]** 10 image(s) rendered at a different aspect ratio than the source — The displayed dimensions distort the source -- CSS is forcing the image into a container at the wrong ratio, producing visible stretching or squashing. Either crop the source to match or use object-fit: cover (and accept the crop). Sample: https://scenegenerator.io/imgs/models/samples/seedream-5-0-pro-lumen-serum.webp, https://scenegenerator.io/imgs/models/samples/nano-banana-pro-tea-packaging.webp, https://scenegenerator.io/imgs/models/samples/gpt-image-2-editorial-cover.webp (+7 more). ### Autoplay Media (A+ — 100/100) *No autoplay media on the page* - **[PASS]** No autoplay media on the page --- ## Infrastructure ### DNS Records (A — 90/100) *2 A records, 256 ms lookup* - **[PASS]** Resolves to 2 IPv4 address(es) - **[PASS]** Has 2 IPv6 (AAAA) record(s) - **[PASS]** 2 nameserver(s) configured - **[PASS]** 3 mail exchanger(s) configured - **[PASS]** SPF record present in TXT - **[WARNING]** DNS resolution is slow (256 ms) — Slow DNS adds latency to every page load. Consider a faster DNS provider. ### Subdomain Takeover (A+ — 100/100) *No subdomain takeover risk detected* - **[PASS]** No CNAME record present ### DNSSEC (B — 80/100) *Unsigned (DNSSEC not deployed)* - **[INFO]** DNSSEC is not deployed — The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government). ### CAA Records (B — 80/100) *No CAA records (any CA may issue certificates)* - **[INFO]** No CAA records published — Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud. ### Reverse DNS (C — 60/100) *0/4 IPs match cert SAN* - **[INFO]** PTR lookup failed for 104.21.63.148: lookup 104.21.63.148: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue. - **[INFO]** PTR lookup failed for 172.67.147.30: lookup 172.67.147.30: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue. - **[INFO]** PTR lookup failed for 2606:4700:3030::6815:3f94: lookup 2606:4700:3030::6815:3f94: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue. - **[INFO]** PTR lookup failed for 2606:4700:3034::ac43:931e: lookup 2606:4700:3034::ac43:931e: no such host — No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue. ### Multi-Resolver DNS Speed (A+ — 100/100) *Mean 17ms across 3 resolvers (spread 21ms)* - **[PASS]** Quad9: 5ms - **[PASS]** Cloudflare: 22ms - **[PASS]** Google: 26ms ### Redirect Chain (A+ — 100/100) *No redirects — direct access* - **[PASS]** No redirects — direct access ### IPv6 Readiness (A+ — 100/100) *IPv6 reachable (17 ms)* - **[PASS]** IPv6 is configured and reachable at 2606:4700:3030::6815:3f94, 2606:4700:3034::ac43:931e ### Crawlability (A+ — 100/100) *robots.txt present, sitemap with 82 URLs* - **[PASS]** robots.txt is present - **[PASS]** sitemap.xml is present - **[PASS]** sitemap.xml is valid XML - **[PASS]** sitemap.xml contains 82 entries - **[PASS]** robots.txt references sitemap ### URL Variants (B — 75/100) *www/non-www, trailing slash, HTTP→HTTPS* - **[PASS]** www/non-www redirect configured correctly (preferred: non-www) - **[CRITICAL]** HTTP version does not redirect to HTTPS ### Domain Intelligence *Domain intelligence data not available* --- ## Compliance ### WCAG Compliance (A+ — 100/100) *No testable criteria* ### Cookie Consent & Privacy (A+ — 100/100) *privacy policy found* - **[PASS]** Privacy policy link found - **[PASS]** Terms of service link found - **[INFO]** No cookie consent banner detected - **[INFO]** This is an automated check, not legal advice — BeaverCheck detects technical indicators of consent management. This does not constitute a legal compliance assessment. Consult a privacy professional for GDPR/CCPA compliance. ### Consent UX Depth (A+ — 100/100) *No consent-UX depth issues detected* - **[PASS]** No consent-UX depth issues detected ### Tracker Inventory (A+ — 100/100) *No known trackers detected on this page* - **[PASS]** No known trackers detected on this page ### Language & i18n (A — 90/100) *Lang attribute present* - **[PASS]** attribute is present - **[PASS]** value is valid - **[INFO]** No Content-Language HTTP header - **[INFO]** Language signals are inconsistent — The attribute and Content-Language header should agree. ### Hreflang Configuration (A+ — 100/100) *All 3 hreflang tag(s) look correct* - **[PASS]** All 3 hreflang tag(s) look correct ### Internationalization Extras (A+ — 100/100) *No additional i18n signals detected* - **[PASS]** No additional i18n signals detected ### Readability & Typography (A+ — 100/100) *Font sizes and tap targets checked* ### Viewport Configuration (A+ — 100/100) *Viewport properly configured* - **[PASS]** Viewport meta tag is present - **[PASS]** width=device-width is set - **[PASS]** User zooming is allowed ### Accessibility Statement (B — 70/100) *No accessibility statement detected* - **[WARNING]** No accessibility statement detected — Sites are increasingly expected to publish an accessibility statement. Required by EU Web Accessibility Directive 2016/2102 for public-sector bodies; recommended best practice elsewhere. Common URLs: /accessibility, /accessibility-statement, /a11y. ### GDPR Article 13 Disclosures (F — 12/100) *1 / 8 Art. 13 categories matched in homepage body* - **[WARNING]** GDPR Article 13 disclosure coverage: 1 / 8 categories — Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 1 of 8 categories: Data subject rights (access, erasure, rectification, etc.). Missing: Data Protection Officer contact (where applicable), Data retention period, Identity / contact details of the data controller, International data transfers, Legal basis for processing, Recipients of personal data, Right to lodge a complaint with a supervisory authority. Note: only the FIRST same-origin privacy-policy link is followed; deeper sub-pages (e.g. /legal/data-subject-rights) are not fetched. ### Third-Party Trackers (A+ — 95/100) *1 trackers detected* - **[INFO]** 1 third-party trackers detected — Found 1 analytics, 0 advertising, 0 marketing, 0 tag manager, 0 session-replay, 0 heatmap trackers. ### Cookie & Tracker Inventory (A+ — 100/100) *0 cookies · 1 trackers · 0 pre-consent* - **[INFO]** 1 third-party tracker(s) detected on page ### Tracking Pixel Inventory (A+ — 100/100) *No tracking pixels detected* - **[PASS]** No tracking pixels detected ### Browser Fingerprinting (A+ — 100/100) *No browser-fingerprinting libraries detected* - **[PASS]** No browser-fingerprinting libraries detected ### Cross-Site Cookies (SameSite=None) (A+ — 100/100) *No cookies on the page* - **[PASS]** No cookies set on the page response ### Beacon Tracking (sendBeacon) (A+ — 100/100) *No navigator.sendBeacon usage detected in inline scripts* - **[PASS]** No navigator.sendBeacon usage detected in inline scripts --- ## Legal ### Legal Page Ecosystem (B — 80/100) *4 of 7 expected legal pages detected* - **[PASS]** Privacy Policy detected — Found at /privacy-policy, linked from footer. - **[PASS]** Terms of Service detected — Found at /terms-of-service, linked from footer. - **[PASS]** Cookie Policy detected — Found at /cookie-policy, linked from footer. - **[INFO]** Accessibility Statement not detected — No link matching common Accessibility Statement URL patterns or link text was found. Most websites are expected to have a Accessibility Statement, especially those collecting user data. - **[INFO]** DMCA / Copyright Notice not detected — No link matching common DMCA / Copyright Notice URL patterns or link text was found. Most websites are expected to have a DMCA / Copyright Notice, especially those collecting user data. - **[PASS]** Refund / Returns Policy detected — Found at /refund-policy, linked from footer. - **[INFO]** Acceptable Use Policy not detected — No link matching common Acceptable Use Policy URL patterns or link text was found. Most websites are expected to have a Acceptable Use Policy, especially those collecting user data. ### Copyright Notice (A+ — 100/100) *© 2026 SceneGenerator* - **[PASS]** Copyright notice is up to date — Copyright notice is up to date: © 2026 SceneGenerator - **[PASS]** Copyright holder: SceneGenerator ### Regulatory Indicators *2 regulatory indicator(s) detected* - **[INFO]** This is a technical scan, not a legal assessment — BeaverCheck detects technical indicators that may suggest regulatory relevance. This is not a compliance audit and should not be relied upon for legal decisions. Consult qualified legal counsel for compliance assessments. - **[INFO]** GDPR indicators detected (moderate confidence) — Indicators suggesting GDPR may be relevant: Privacy policy page found. EU General Data Protection Regulation — governs collection and processing of personal data of EU residents. - **[INFO]** HIPAA indicators detected (weak confidence) — Indicators suggesting HIPAA may be relevant: Text mentions: phi. Health Insurance Portability and Accountability Act — protects sensitive patient health information. ### Third-Party Data Sharing *0 third-party service(s) detected* - **[INFO]** Data inventory for transparency purposes — This inventory identifies third-party services that receive data from your site visitors. Under regulations like GDPR (Article 30), maintaining records of data processing activities is commonly considered a best practice. This automated scan provides a starting point — it may not capture all data flows. - **[INFO]** No recognized third-party data-sharing services detected — This page does not appear to load external tracking, analytics, or advertising scripts. ### Compliance Badges (C — 55/100) *0 compliance badge(s) detected* - **[INFO]** No compliance badges detected — No recognized compliance certification badges or seals were found. This is common — many sites do not display compliance badges. --- ## Availability ### CDN & Delivery (B — 80/100) *Cloudflare* - **[PASS]** Site is served via Cloudflare CDN (edge: CDG) ### HTTP Caching (F — 30/100) *No cache headers* - **[WARNING]** No Cache-Control header found — Browsers will use heuristic caching, which can be unpredictable. Set explicit cache headers. ### Operational Status Page (B — 80/100) *No status page link detected* - **[INFO]** No operational status page link detected — Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure. ### Transport Security (A — 85/100) *HTTP/3, HSTS, and TLS version analysis* - **[PASS]** HTTP/3 (QUIC) supported — The server advertises HTTP/3 via Alt-Svc for faster connections on mobile networks. - **[WARNING]** Missing Strict-Transport-Security header — HSTS tells browsers to only use HTTPS, preventing SSL stripping attacks. - **[PASS]** TLS 1.3 in use (fastest handshake, 1-RTT) ### Health Check Endpoint (B — 80/100) *No conventional health endpoint found* - **[INFO]** No conventional health endpoint found — Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404. ### CDN Cache Observability (B — 85/100) *No CDN cache-status headers in the response* - **[INFO]** No CDN cache-status headers in the response — Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy. --- ## Accessibility ### Landmark Structure (A — 85/100) *5 landmarks* - **[PASS]**
landmark present - **[PASS]** 1