# BeaverCheck Audit Report — https://www.duckydecor.co.uk **Date:** October 28, 2026 **URL:** https://www.duckydecor.co.uk **Overall Grade:** B (83/100) **Report:** https://beavercheck.com/results/4a8c337b-e93e-4ec3-9d53-dea929d7ad82 ## Top Findings 1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers 2. **[CRITICAL]** HSTS header is missing — Security > Security Headers 3. **[CRITICAL]** Page weighs 5.0 MB (4.6 MB transferred) — Performance > Page Weight Budget 4. **[CRITICAL]** 1 button(s) with no accessible text — Accessibility > Link & Button Quality 5. **[CRITICAL]** 1 control(s) without accessible label — Accessibility > Form Accessibility --- ## Lighthouse Scores | Category | Score | |----------|-------| | Performance | 67 | | Accessibility | 90 | | Best Practices | 100 | | SEO | 85 | --- ## 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, 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 180 days) - **[PASS]** Certificate chain has 4 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 (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 (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 (D — 60/100) *4 of 6 new-tab link(s) missing rel=noopener* - **[WARNING]** 4 link(s) open in a new tab without rel=noopener — Without rel="noopener", the destination tab can navigate the original tab via window.opener -- a reverse-tabnabbing phishing primitive. Modern browsers default to noopener since Chrome 88 / Firefox 79 / Safari 12.1, but explicit rel="noopener noreferrer" remains the documented best practice for older browsers, in-app webviews, and security scanners. ### CSP Inline-Style Readiness (D — 60/100) *253 inline style attribute(s) detected* - **[WARNING]** 253 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. 253 inline style(s) is high. Affected element types include: div, header, nav, span, h2. 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) (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 (B — 90/100) *1 generator tag(s) without version info* - **[INFO]** 1 generator tag(s) without version info: MyWebsite NOW — Generator tags reveal the CMS / build tool but no version specifics. Attackers can't directly cross-reference CVEs but can probe known weaknesses for the named platform. Removing the tag entirely is preferable; most CMSes have a one-config-flag option to suppress it. ### 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, no SPF* - **[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]** No SPF record found — Without SPF (Sender Policy Framework), receivers can't tell which servers are authorized to send mail for your domain. Add a TXT record at the apex starting with v=spf1, ending in -all. - **[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 — 0/100) *4.6 MB transferred, 38 requests* - **[CRITICAL]** Page weighs 5.0 MB (4.6 MB transferred) - **[WARNING]** Images are 4.0 MB — compress or use modern formats — Convert images to WebP/AVIF and resize to display dimensions to reduce transfer size. - **[INFO]** CSS is 266 KB — consider purging unused styles — Remove unused CSS rules with tools like PurgeCSS to reduce stylesheet size. - **[INFO]** Fonts are 224 KB — consider subsetting or using system fonts — Subset fonts to include only used characters, or switch to system font stacks. - **[PASS]** 38 HTTP requests - **[INFO]** Estimated 0.96 g CO2 per page load ### Third-Party Impact (A+ — 100/100) *-0% third-party, 0 ms blocking* - **[INFO]** Third-party code accounts for -0% of page weight (-1 B of 4.6 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 (C — 60/100) *16 images, 0 KB saveable* - **[WARNING]** https://www.duckydecor.co.uk/wp-content/uploads/go... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS. - **[WARNING]** https://www.duckydecor.co.uk/wp-content/uploads/go... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS. - **[WARNING]** https://www.duckydecor.co.uk/wp-content/uploads/go... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS. - **[WARNING]** https://www.duckydecor.co.uk/wp-content/uploads/go... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS. - **[WARNING]** https://www.duckydecor.co.uk/wp-content/uploads/go... is missing width/height — may cause layout shift — Set explicit width and height to prevent CLS. ### JS Execution Cost (B — 80/100) *637ms total JS execution* - **[WARNING]** https://www.duckydecor.co.uk/: 332ms CPU time - **[WARNING]** Unattributable: 305ms CPU time ### Font Loading (A+ — 100/100) *6 fonts (224 KB)* - **[INFO]** 6 font(s) use font-display: swap (FOUT risk but functional) ### JS Bundles (A+ — 100/100) *10 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. ### Document Compression (A+ — 100/100) *Document 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. ### Asset Compression *No text asset hosts to measure* - **[INFO]** No third-party or subdomain host served enough text assets to measure — Asset compression is measured per host, from one HEAD request against a sampled resource. Pages that serve all their JS and CSS from the document's own origin are covered by the document compression check instead. ### 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+ — 95/100) *2 server-response signal(s) detected* - **[PASS]** `Vary` header declared: accept-encoding — 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 (C — 60/100) *38 resources · 4.6 MB · 0 KB savings available* - **[WARNING]** Page weight 4.6 MB exceeds 1 MB target by 3.6 MB - **[INFO]** 1 third-party resources (-0% of weight) - **[INFO]** 7 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 — 90/100) *1 CSS depth issue(s) detected* - **[WARNING]** 78 `@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 (C — 75/100) *60 links checked, 55 healthy, 5 broken* - **[CRITICAL]** 55 of 60 links are healthy - **[WARNING]** Broken link: https://www.duckydecor.co.uk/wp-json/oembed/1.0/embed?url... — Found in . Returns HTTP 403. - **[WARNING]** Broken link: https://www.duckydecor.co.uk/wp-json/oembed/1.0/embed?url... — Found in . Returns HTTP 403. - **[WARNING]** Broken link: https://www.duckydecor.co.uk/wp-json/ — Found in . Returns HTTP 403. - **[WARNING]** Broken link: https://www.duckydecor.co.uk/wp-json/wp/v2/pages/96 — Found in . Returns HTTP 403. - **[WARNING]** Broken link: https://www.duckydecor.co.uk/xmlrpc.php?rsd — 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 (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 (A+ — 100/100) *1 JSON-LD block(s) found — structured data is well configured.* - **[INFO]** Missing recommended property "telephone" for LocalBusiness — Adding "telephone" can improve how search engines display your content. ### 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): LocalBusiness 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 — 50/100) *4 issues found across 13 images* - **[WARNING]** 13 images missing explicit width/height — Images without dimensions cause layout shifts (CLS). Set explicit width and height attributes. - **[INFO]** 12 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight. - **[WARNING]** All 13 images use legacy formats (JPEG/PNG/GIF) — WebP offers 25-35% smaller files than JPEG. Use with for modern format support. - **[WARNING]** 12 images missing alt text — Alt text is essential for screen readers and SEO. Every meaningful image needs descriptive alt text. ### Autoplay Media (A+ — 100/100) *No autoplay media on the page* - **[PASS]** No autoplay media on the page --- ## Infrastructure ### DNS Records (A — 85/100) *1 A records, 40 ms lookup* - **[PASS]** Resolves to 1 IPv4 address(es) - **[INFO]** Single A record — no DNS redundancy — Multiple A records provide failover if one server goes down. - **[PASS]** Has 1 IPv6 (AAAA) record(s) - **[INFO]** No NS records found - **[INFO]** No MX records — email not configured via DNS - **[INFO]** No SPF record found in TXT records — SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'. - **[PASS]** DNS resolution time: 40 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 (B — 75/100) *0/2 IPs match cert SAN* - **[INFO]** PTR for 212.227.172.252 does not match any cert SAN: 212-227-172-252.elastic-ssl.ui-r.com — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree. - **[INFO]** PTR for 2001:8d8:105:1:0:1:0:3 does not match any cert SAN: 2001-08d8-0105-0001-0000-0001-0000-0003.elastic-ssl.ui-r.com — Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree. ### Multi-Resolver DNS Speed (A+ — 100/100) *Mean 22ms across 3 resolvers (spread 37ms)* - **[PASS]** Quad9: 1ms - **[PASS]** Google: 28ms - **[PASS]** Cloudflare: 38ms ### Redirect Chain (A+ — 100/100) *No redirects — direct access* - **[PASS]** No redirects — direct access ### IPv6 Readiness (A+ — 100/100) *IPv6 reachable (31 ms)* - **[PASS]** IPv6 is configured and reachable at 2001:8d8:105:1:0:1:0:3 ### Crawlability (A+ — 100/100) *robots.txt present, sitemap with 1 URLs* - **[PASS]** robots.txt is present - **[PASS]** sitemap.xml is present - **[PASS]** sitemap.xml is valid XML - **[PASS]** sitemap.xml contains 1 entries - **[PASS]** Sitemap index with 1 child sitemaps - **[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: www) - **[PASS]** HTTP correctly redirects to HTTPS permanently ### Domain Intelligence (A+ — 100/100) *duckydecor.co.uk — via Ionos SE, 2 months old* - **[PASS]** Domain registered until Aug 26, 2027 (10 months remaining) - **[INFO]** Domain is only 2 months 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: Ionos SE - **[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+ — 95/100) *privacy policy found* - **[PASS]** Privacy policy link found - **[INFO]** No terms of service link detected - **[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) *No hreflang tags on this page* - **[PASS]** No hreflang tags found (single-language site) ### 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 (C — 60/100) *Viewport prevents zooming* - **[PASS]** Viewport meta tag is present - **[PASS]** width=device-width is set - **[CRITICAL]** Viewport prevents user zooming — user-scalable=no or maximum-scale < 2 prevents users from zooming. This is a WCAG 1.4.4 (Level AA) failure and an accessibility barrier for users with low vision. ### 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. Detection is by link URL and anchor text, in a limited set of languages, so this is an unconfirmed absence. ### GDPR Article 13 Disclosures (D — 50/100) *4 / 8 Art. 13 categories matched in homepage body* - **[WARNING]** GDPR Article 13 disclosure coverage: 4 / 8 categories — Scanned the homepage body text AND the linked /privacy page for GDPR Article 13 disclosures. Matched 4 of 8 categories: Data retention period, Data subject rights (access, erasure, rectification, etc.), International data transfers, Legal basis for processing. Missing: Data Protection Officer contact (where applicable), Identity / contact details of the data controller, 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+ — 100/100) *No third-party trackers detected* - **[PASS]** No third-party trackers detected ### 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 — 55/100) *2 of 7 expected legal pages detected* - **[PASS]** Privacy Policy detected — Found at /privacy-policy/. - **[PASS]** Terms of Service detected — Found at /legal-notice/. - **[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. - **[INFO]** Refund / Returns Policy not detected — No link matching common Refund / Returns Policy URL patterns or link text was found. Most websites are expected to have a Refund / Returns Policy, especially those collecting user data. - **[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 Ducky Décor* - **[PASS]** Copyright notice is up to date — Copyright notice is up to date: © 2026 Ducky Décor - **[PASS]** Copyright holder: Ducky Décor ### 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 (strong confidence) — Indicators suggesting GDPR may be relevant: Text mentions: gdpr; 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 (D — 50/100) *No CDN (document or assets)* - **[WARNING]** No CDN (document or assets) — Neither the HTML document nor the page's subresources are served through an edge network. A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them. ### 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 (B — 75/100) *HTTP/3, HSTS, and TLS version analysis* - **[INFO]** HTTP/3 (QUIC) not advertised — HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it. - **[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