# BeaverCheck Audit Report — https://utkay.com **Date:** November 7, 2026 **URL:** https://utkay.com **Overall Grade:** B (88/100) **Report:** https://beavercheck.com/results/2df343da-a0b9-4a39-828e-6807e717a8cc ## Top Findings 1. **[CRITICAL]** Content-Security-Policy header is missing — Security > Security Headers 2. **[WARNING]** 12 inline style attribute(s) detected — Security > CSP Inline-Style Readiness 3. **[WARNING]** Cross-Origin-Embedder-Policy header is missing — Security > Security Headers 4. **[WARNING]** Cross-Origin-Opener-Policy header is missing — Security > Security Headers 5. **[WARNING]** HSTS is enabled but missing includeSubDomains — Security > Security Headers --- ## Lighthouse Scores | Category | Score | |----------|-------| | Performance | 0 | | Accessibility | 96 | | Best Practices | 100 | | SEO | 100 | --- ## Security ### Security Headers (C — 65/100) *6 of 10 headers properly configured* - **[WARNING]** HSTS is enabled but missing includeSubDomains — Without includeSubDomains, subdomains can still be accessed over HTTP. - **[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 88 days) - **[PASS]** Certificate chain has 4 certificates - **[PASS]** Certificate uses modern signature algorithm - **[PASS]** Certificate covers 6 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 (A+ — 100/100) *All 3 new-tab link(s) carry rel=noopener* - **[PASS]** All 3 new-tab link(s) carry rel=noopener ### CSP Inline-Style Readiness (C — 75/100) *12 inline style attribute(s) detected* - **[WARNING]** 12 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. 12 inline style(s) is moderate. Affected element types include: path, section. 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 (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 2 candidate URL(s))* - **[PASS]** No source maps accessible across 2 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, 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 (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+ — 100/100) *69 KB transferred, 7 requests* - **[PASS]** Page weighs 156 KB (69 KB transferred) - **[PASS]** 7 HTTP requests - **[INFO]** Estimated 0.01 g CO2 per page load ### Third-Party Impact (A+ — 100/100) *No third-party resources* - **[PASS]** No third-party resources detected ### Text Compression (A+ — 100/100) *All text resources are compressed* - **[PASS]** All text resources are compressed ### Image Optimization (A+ — 95/100) *2 images, 0 KB saveable* - **[PASS]** All images are well-optimized ### JS Execution Cost (B — 80/100) *984ms total JS execution* - **[WARNING]** https://utkay.com/: 449ms CPU time - **[WARNING]** https://utkay.com/assets/main.js?v=42: 363ms CPU time - **[INFO]** Unattributable: 173ms CPU time ### Font Loading (A+ — 100/100) *No web fonts (system fonts)* - **[PASS]** No web fonts loaded — system fonts are fastest ### JS Bundles (A+ — 100/100) *2 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 (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+ — 100/100) *3 server-response signal(s) detected* - **[PASS]** `Cache-Status` header present (RFC 9211): "Netlify Edge"; fwd=miss; fwd-status=200; stored — The page returns a `Cache-Status` header -- the standardized way for CDNs and caches to communicate per-hop cache state to debugging tools. Format: `Cache-Status: cdn-name; hit; ttl=300` (or `; fwd=miss` / `; fwd=stale`). Standard alternative to vendor-specific `X-Cache` patterns each CDN had historically. Cloudflare, Fastly, and Akamai all support emitting it. - **[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). - **[PASS]** `ETag` present -- conditional GET supported ### Page Weight Inventory (A+ — 100/100) *7 resources · 69 KB · 0 KB savings available* - **[PASS]** Within 1MB page-weight target ### Render-Blocking Resources (A+ — 100/100) *No render-blocking resources detected* - **[PASS]** No render-blocking resources detected in ### Third-Party Resources (A+ — 100/100) *No third-party resources detected* ### JavaScript Blocking (A+ — 100/100) *No render-blocking JS or document.write usage detected* - **[PASS]** No JavaScript blocking issues detected ### CSS Performance Depth (A+ — 100/100) *No CSS performance depth issues detected* - **[PASS]** No CSS performance depth issues detected --- ## Content Quality ### Links (A — 95/100) *19 links checked, 18 healthy, 1 broken* - **[WARNING]** 18 of 19 links are healthy - **[CRITICAL]** Broken link: https://www.linkedin.com/in/utkay — Found in . Returns HTTP 999. ### 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 — 90/100) *Open Graph tags are well configured for social sharing.* - **[INFO]** og:title is short (21 characters) — Ideal length is 25–60 characters for social sharing previews. - **[INFO]** Missing og:site_name — The og:site_name tag displays the website name in social previews. - **[INFO]** Missing twitter:card — Without twitter:card, Twitter falls back to Open Graph tags. Adding it gives you more control. ### 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.* ### 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): Person 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 (B — 80/100) *2 issues found across 2 images* - **[WARNING]** 1 images significantly larger than display size — Resizing to display dimensions could save approximately 35 KB. - **[INFO]** 1 below-fold images missing loading="lazy" — Lazy loading defers below-fold images, reducing initial page weight. ### Autoplay Media (A+ — 100/100) *No autoplay media on the page* - **[PASS]** No autoplay media on the page --- ## Infrastructure ### DNS Records (A+ — 95/100) *2 A records, 39 ms lookup* - **[PASS]** Resolves to 2 IPv4 address(es) - **[PASS]** Has 2 IPv6 (AAAA) record(s) - **[PASS]** 4 nameserver(s) configured - **[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: 39 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/4 IPs match cert SAN* - **[INFO]** PTR for 35.157.26.135 does not match any cert SAN: ec2-35-157-26-135.eu-central-1.compute.amazonaws.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 63.176.8.218 does not match any cert SAN: ec2-63-176-8-218.eu-central-1.compute.amazonaws.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 lookup failed for 2a05:d014:58f:6200::258: lookup 2a05:d014:58f:6200::258: 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 2a05:d014:58f:6200::259: lookup 2a05:d014:58f:6200::259: 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 37ms across 3 resolvers (spread 9ms)* - **[PASS]** Google: 34ms - **[PASS]** Cloudflare: 34ms - **[PASS]** Quad9: 43ms ### Redirect Chain (A+ — 100/100) *No redirects — direct access* - **[PASS]** No redirects — direct access ### IPv6 Readiness (A+ — 100/100) *IPv6 reachable (25 ms)* - **[PASS]** IPv6 is configured and reachable at 2a05:d014:58f:6200::258, 2a05:d014:58f:6200::259 ### Crawlability (A+ — 100/100) *robots.txt present, sitemap with 3 URLs* - **[PASS]** robots.txt is present - **[PASS]** sitemap.xml is present - **[PASS]** sitemap.xml is valid XML - **[PASS]** sitemap.xml contains 3 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) *utkay.com — via Name.com, Inc., 6 days old* - **[PASS]** Domain registered until Oct 31, 2027 (11 months remaining) - **[INFO]** Domain is only 6 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: Name.com, 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 (B — 80/100) *No consent signals detected* - **[WARNING]** No privacy policy found (page links and common paths checked) — No link matching the privacy-policy vocabulary was found in the rendered page, and the common privacy-policy paths returned nothing. A privacy policy page is recommended for transparency and may be legally required. - **[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) *All 4 hreflang tag(s) look correct* - **[PASS]** All 4 hreflang tag(s) look correct ### Internationalization Extras (A+ — 100/100) *2 i18n signal(s) detected* - **[PASS]** Mixed-language content: 2 subtree language(s) declared (en, de) — The page has elements with `lang="X"` attributes that differ from the root ``. Per WCAG 3.1.2 (Level AA), this is the correct way to mark language-of-parts: a screen reader switches pronunciation when entering a `lang="fr"` block on an English page. The catalog is informational -- presence of subtree lang attributes is a positive a11y signal. - **[PASS]** Language switcher detected (anchor tags carry `hreflang` attribute) — The page has anchor tags with `hreflang` attributes -- the standard semantic for language-switcher links. Search engines and screen readers use the hreflang attribute to know what language the linked page is in, even when the link text is in the source language (e.g. `Français` on an English page). ### 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. 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) *0 / 8 Art. 13 categories matched in homepage body* - **[INFO]** GDPR Article 13 disclosures not assessed (policy language: tr) — The privacy policy appears to be written in "tr", which this check has no disclosure patterns for (currently English, French, German and Spanish). No conclusion is drawn about the policy's completeness, and this finding is excluded from the regulatory-risk estimate. ### 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 (F — 0/100) *0 of 7 expected legal pages detected* - **[WARNING]** Privacy Policy not detected — No link matching common Privacy Policy URL patterns or link text was found. Most websites are expected to have a Privacy Policy, especially those collecting user data. - **[WARNING]** Terms of Service not detected — No link matching common Terms of Service URL patterns or link text was found. Most websites are expected to have a Terms of Service, especially those collecting user data. - **[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 Utkay Nesim Gögebakan Kalite yönetimi · Proje kal…* - **[PASS]** Copyright notice is up to date — Copyright notice is up to date: © 2026 Utkay Nesim Gögebakan Kalite yönetimi · Proje kali - **[PASS]** Copyright holder: Utkay Nesim Gögebakan Kalite yönetimi · Proje kali ### Regulatory Indicators *0 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]** No specific regulatory indicators detected — No strong signals for GDPR, CCPA, ADA, PCI, HIPAA, or COPPA were found. This does not mean these regulations don't apply — it means we didn't detect common technical indicators. ### 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 (A — 85/100) *Netlify ("Netlify Edge"; fwd=miss; fwd-status=200; stored)* - **[PASS]** Document is served via Netlify CDN - **[INFO]** CDN cache status: "Netlify Edge"; fwd=miss; fwd-status=200; stored ### HTTP Caching (B — 75/100) *public,max-age=0,must-revalidate* - **[PASS]** Cache-Control header is set - **[PASS]** ETag present — enables conditional (304) responses ### 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 — 90/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. - **[PASS]** HSTS enabled (base policy) - **[INFO]** HSTS missing includeSubDomains — Without includeSubDomains, HSTS only protects the exact domain. - **[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 (A+ — 100/100) *Cache state: Age=1s* - **[PASS]** CDN cache state observable via 1 header(s) --- ## Accessibility ### Landmark Structure (A — 85/100) *4 landmarks* - **[PASS]**
landmark present - **[PASS]** 1