# BeaverCheck Audit Report — https://minimaxh3.art **Date:** August 26, 2026 **URL:** https://minimaxh3.art **Overall Grade:** A (90/100) **Report:** https://beavercheck.com/results/64a20a2d-bf61-44c0-969b-e55a6d4e5c91 ## Top Findings 1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers 2. **[CRITICAL]** No Content-Security-Policy header found — Security > Content Security Policy 3. **[WARNING]** 1 `@font-face` rule(s) without `font-display` -- causes FOIT — Performance > CSS Performance Depth 4. **[WARNING]** 101 HTTP requests — consider bundling or reducing — Performance > Page Weight Budget 5. **[WARNING]** Cross-Origin-Embedder-Policy header is missing — Security > Security Headers --- ## Lighthouse Scores | Category | Score | |----------|-------| | Performance | 76 | | Accessibility | 96 | | Best Practices | 100 | | SEO | 100 | --- ## Security ### Security Headers (B — 70/100) *7 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 - **[PASS]** Referrer-Policy is properly configured - **[PASS]** Permissions-Policy is set - **[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, 8 checks passed* - **[PASS]** TLS 1.3 is used - **[PASS]** Strong cipher suite is used - **[PASS]** HTTP/2 is negotiated - **[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 62 days) - **[PASS]** Certificate chain has 3 certificates - **[PASS]** Certificate uses modern signature algorithm - **[PASS]** Certificate covers 3 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: a31663f7687e9b08-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) *All 19 new-tab link(s) carry rel=noopener* - **[PASS]** All 19 new-tab link(s) carry rel=noopener ### 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 (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 (A+ — 100/100) *Referrer-Policy is `strict-origin-when-cross-origin` (modern default -- full URL same-origin, origin-only cross-origin)* - **[PASS]** Referrer-Policy: `strict-origin-when-cross-origin` -- modern default -- full URL same-origin, origin-only cross-origin — The modern browser default (Chrome 85+, Firefox 87+, Safari 15+). Full URL Referer on same-origin; origin only on cross-origin; no Referer on HTTPS-to-HTTP downgrade. Privacy-safe and breaks no analytics. The recommended explicit value. ### 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 (C — 59/100) *DMARC: reject, SPF: ~all* - **[PASS]** DMARC policy is reject — strongest protection - **[INFO]** DMARC configured without rua= aggregate reporting — Without rua=, you have no visibility into spoof attempts or auth failures from your own legitimate senders. Add rua=mailto:dmarc@ (or a managed inbox at a reporting service). - **[INFO]** SPF ends in ~all (soft fail) — Soft fail tells receivers to accept-but-mark unauthorized mail. Migrate to -all once you've confirmed all legitimate senders are listed (DMARC aggregate reports help verify). - **[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 (B — 75/100) *3 directives, 2 missing* - **[PASS]** camera=() — blocked for all origins - **[PASS]** microphone=() — blocked for all origins - **[PASS]** geolocation=() — 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+ — 97/100) *633 KB transferred, 101 requests* - **[PASS]** Page weighs 2.1 MB (633 KB transferred) - **[WARNING]** 101 HTTP requests — consider bundling or reducing — Each request adds latency. Bundle small files, use sprites, or eliminate unnecessary requests. - **[INFO]** Estimated 0.13 g CO2 per page load ### Third-Party Impact (A+ — 100/100) *1% third-party, 0 ms blocking* - **[INFO]** Third-party code accounts for 1% of page weight (6.2 KiB of 633.1 KiB) - **[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+ — 100/100) *10 images, 0 KB saveable* - **[PASS]** All images are well-optimized ### JS Execution Cost (D — 40/100) *2713ms total JS execution* - **[WARNING]** https://minimaxh3.art/assets/framework-DJH1pfSr.js: 857ms CPU time - **[WARNING]** https://minimaxh3.art/: 757ms CPU time - **[WARNING]** https://minimaxh3.art/assets/demo-reel-DuPcTGlO.js: 706ms CPU time - **[WARNING]** Unattributable: 393ms CPU time ### Font Loading (A+ — 100/100) *2 fonts (21 KB)* - **[INFO]** 2 font(s) use font-display: swap (FOUT risk but functional) ### JS Bundles (A+ — 100/100) *73 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 — 90/100) *6 hints, 0 missing preconnects* - **[INFO]** 1 dns-prefetch redundant with preconnect on same origin — preconnect already does the DNS lookup; adding dns-prefetch to the same origin is at best a no-op. Sample: https://www.googletagmanager.com. Remove the redundant dns-prefetch entries. - **[INFO]** 1 URL(s) appear in multiple hints — The same href shouldn't appear in multiple hint rels -- one wins, the others are wasted markup and may confuse cache behavior. Sample: https://www.googletagmanager.com (dns-prefetch+preconnect). - **[PASS]** Page uses 6 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 (A+ — 100/100) *Main HTML max-age=0 (≤ 5min) is appropriate* - **[PASS]** Main HTML max-age=0 (≤ 5min) is appropriate ### 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, Accept, Next-Router-State-Tree, Next-Router-Prefetch, Next-Router-Segment-P... — 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) *101 resources · 633 KB · 0 KB savings available* - **[PASS]** Within 1MB page-weight target - **[INFO]** 7 third-party resources (1% of weight) ### 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 — 90/100) *1 CSS depth issue(s) detected* - **[WARNING]** 1 `@font-face` rule(s) without `font-display` -- causes FOIT — An `@font-face` rule without `font-display` causes Flash of Invisible Text (FOIT): the browser hides the styled text for up to 3 seconds while the custom font downloads, then either swaps to fallback (Chrome / Firefox) or stays invisible (older Safari). Add `font-display: swap` (shows fallback immediately, swaps in the custom font when ready) or `font-display: optional` (uses fallback if the font isn't ready in 100ms; never causes visible swap). Either eliminates FOIT outright. --- ## Content Quality ### Links (A — 90/100) *137 links checked, 135 healthy, 2 broken* - **[WARNING]** 135 of 137 links are healthy - **[WARNING]** Broken link: https://www.googletagmanager.com — Found in . Returns HTTP 404. - **[WARNING]** Broken link: https://pbs.twimg.com/profile_images/2046023889969692672/... — Found in . Returns HTTP 404. ### 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+ — 100/100) *Open Graph tags are well configured for social sharing.* ### 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 — 90/100) *1 JSON-LD block(s) found — structured data is well configured.* - **[WARNING]** Missing required property "name" for Organization — The "name" property is required for the Organization schema type. - **[INFO]** Missing recommended property "url" for Organization — Adding "url" can improve how search engines display your content. - **[INFO]** Missing recommended property "logo" for Organization — Adding "logo" can improve how search engines display your content. - **[INFO]** Missing recommended property "sameAs" for Organization — Adding "sameAs" can improve how search engines display your content. ### Rich Results Eligibility (A+ — 100/100) *1 JSON-LD block(s) declaring 6 schema type(s)* - **[PASS]** 6 rich-result schema type(s) declared — Inventory of structured-data types on the page (each may unlock a different SERP feature): FAQPage, Organization, SoftwareApplication, VideoObject, WebPage, WebSite 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 (D — 65/100) *5 issues found across 48 images* - **[WARNING]** 2 images significantly larger than display size — Resizing to display dimensions could save approximately 165 KB. - **[INFO]** 1 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight. - **[INFO]** 10 of 48 images use legacy formats - **[INFO]** 3 image(s) wider than 400px without srcset (no responsive serving) — These images deliver the same asset to every viewport (mobile, tablet, retina). Adding srcset / lets the browser pick a viewport-appropriate variant and typically saves 40-70% of bytes on mobile. Sample: https://minimaxh3.art/videos/h3-demos/hero-3.webp, https://minimaxh3.art/images/h3-viral/03-poster.jpg, https://minimaxh3.art/images/h3-official/multi-poster.webp. - **[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://minimaxh3.art/videos/h3-demos/hero-3.webp, https://minimaxh3.art/videos/h3-cases/music-mv.webp, https://minimaxh3.art/videos/h3-cases/groovy-t2v.webp (+7 more). ### Autoplay Media (A+ — 100/100) *2 media element(s) found, none autoplay* - **[PASS]** 2 media element(s) found, none autoplay --- ## Infrastructure ### DNS Records (A+ — 100/100) *2 A records, 41 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 - **[PASS]** DNS resolution time: 41 ms ### 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 188.114.97.2: lookup 188.114.97.2: 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 188.114.96.2: lookup 188.114.96.2: 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 2a06:98c1:3121::2: lookup 2a06:98c1:3121::2: 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 2a06:98c1:3120::2: lookup 2a06:98c1:3120::2: 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 — 90/100) *Mean 55ms across 3 resolvers (spread 58ms)* - **[PASS]** Google: 28ms - **[PASS]** Cloudflare: 51ms - **[PASS]** Quad9: 86ms ### 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 2a06:98c1:3121::2, 2a06:98c1:3120::2 ### Crawlability (A+ — 100/100) *robots.txt present, sitemap with 136 URLs* - **[PASS]** robots.txt is present - **[PASS]** sitemap.xml is present - **[PASS]** sitemap.xml is valid XML - **[PASS]** sitemap.xml contains 136 entries - **[PASS]** robots.txt references sitemap ### URL Variants (A+ — 100/100) *www/non-www, trailing slash, HTTP→HTTPS* - **[PASS]** www/non-www redirect configured correctly (preferred: non-www) - **[PASS]** HTTP correctly redirects to HTTPS permanently ### Domain Intelligence (A+ — 100/100) *minimaxh3.art — via NameCheap, Inc., 27 days old* - **[PASS]** Domain registered until Jul 30, 2027 (11 months remaining) - **[INFO]** Domain is only 27 days old — Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix. - **[INFO]** DNSSEC is not enabled — DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it. - **[PASS]** Registrar: NameCheap, Inc. - **[WARNING]** Registrar lock is NOT enabled — The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers. --- ## 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 9 hreflang tag(s) look correct* - **[PASS]** All 9 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 (C — 65/100) *3 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. - **[INFO]** Cookie Policy not detected — No link matching common Cookie Policy URL patterns or link text was found. Most websites are expected to have a Cookie Policy, especially those collecting user data. - **[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 MiniMax H3 · minimaxh3* - **[PASS]** Copyright notice is up to date — Copyright notice is up to date: © 2026 MiniMax H3 · minimaxh3 - **[PASS]** Copyright holder: MiniMax H3 · minimaxh3 ### Regulatory Indicators *1 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. ### 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 (B — 75/100) *public, max-age=0, s-maxage=60, must-revalidate* - **[PASS]** Cache-Control header is set - **[PASS]** CDN TTL: 1 minute (s-maxage=60) - **[INFO]** No ETag or Last-Modified header — Conditional requests (304 Not Modified) are not possible without validators. ### 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+ — 100/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. - **[PASS]** HSTS enabled (includeSubDomains, preload) - **[PASS]** HSTS preload enabled - **[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) *9 landmarks* - **[PASS]**
landmark present - **[PASS]** 2