Webopsy

This report was prepared for skytasks.pages.dev. It shows the top findings; the full report includes every issue and its fix.

92skytasks.pages.dev
100Privacy
92Security
100Legal
100Accessibility
100Design
What the scores mean
Scanned Nov 22, 2026, 9:19 AM

No change since the scan on Nov 15, 2026.

Clean bill of health since Nov 15, 2026, serial WO-2026-4848. View the certificate

Opportunities

No critical or high-severity issues. That's the bar most sites miss.

Nothing here.

Diagnostics

Worth fixing. Not an emergency.

Missing 3 security headers~15 min

Not set: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options. These defend against clickjacking, MIME sniffing, and protocol downgrade.

Security Headers _headers
# Missing on your site: Content-Security-Policy, Strict-Transport-Security, X-Frame-Options. The Content-Security-Policy below already allows Google Fonts; add the domain of anything else you load to script-src or connect-src, then re-scan.
/*
  Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
  X-Content-Type-Options: nosniff
  X-Frame-Options: SAMEORIGIN
  Referrer-Policy: strict-origin-when-cross-origin
  Permissions-Policy: camera=(), microphone=(), geolocation=()
  Content-Security-Policy: default-src 'self'; script-src 'self'; connect-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; frame-src 'none'; frame-ancestors 'self'; base-uri 'self'; form-action 'self'
Cloudflare Pages output directory. On Cloudflare in front of another origin, use a Transform Rule (Rules → Transform Rules → Modify Response Header) with the same values. Then re-scan. The Content-Security-Policy is written for what the scan saw (Google Fonts); if a script or request is blocked after deploy, the browser console names the origin to add.
No security.txt for vulnerability reports~5 min

A /.well-known/security.txt file tells researchers how to report a problem before it becomes a breach. Two lines: Contact and Expires.

RFC 9116; expected by many bug-bounty and disclosure norms.

What these findings expose you to

For scale: the security items sit under GDPR Art. 32 (up to 2% of turnover) and the FTC's security enforcement, where the real cost arrives with a breach and its mandatory notifications. In practice the first step is almost always a complaint and a notice with a deadline; the cost comes from ignoring it. These are published maximums and reported ranges, not a prediction.

GDPR / UK GDPR, security of processing · EU, EEA, UK1 finding

Maximum. Up to €10 million or 2% of worldwide annual turnover (Art. 83(4)); UK: up to £8.7 million or 2%.

Usually. Fines follow a breach, not a scan. If exposed data reaches users, breach notification to the regulator within 72 hours is mandatory and the fine considers whether the weakness was known.

Applies: Any site processing personal data of people in the EU or UK. Enforced by regulators.

FTC Act §5 (unfair or deceptive practices) and state breach laws · United States1 finding

Maximum. No fixed fine for a first violation; the FTC obtains consent orders with 20-year audit obligations, and violating an order costs over $53,000 per day. State breach-notification laws add per-resident notification costs and, in some states, per-record penalties.

Usually. Enforcement follows an incident. An exposed live key or open database is the incident waiting to happen; the practical cost is fraud on the account plus mandatory notification.

Applies: Any US company holding consumer data. Enforced by regulators.

AI design tells

No generated-design patterns detected on this page.

Full annotated page (0 labels)
Full page of skytasks.pages.dev with every design tell labeled

This report is complete and free, and true as of the scan time above. The next deploy, a tag added in Tag Manager or a redesigned footer can change it. Watch re-checks skytasks.pages.dev every day and after every deploy, emails you the moment something regresses, keeps the dated record, and gives you a trust page your customers can check.

Watch skytasks.pages.devTrust page draft

Passed audits

(11)
Privacy policy is present

A privacy policy link or page was found.

Privacy policy covers the expected disclosures

2987 words; 14 disclosure checks passed; last updated November 18, 2026.

No third-party trackers detected

None of the common analytics or marketing pixels were found in the page.

Terms of service are present

A terms page or link was found.

Public contact or business identity present

A contact email, contact page, or mailto link was found.

No secret keys in the page or its scripts

No server-side keys (Stripe secret, OpenAI, Anthropic, AWS, GitHub, Slack, SendGrid, Supabase service_role, private keys) in the page or the 1 script bundle it loads.

1 security header set

X-Content-Type-Options

No mixed content

All referenced resources use HTTPS.

Legal entity and address are shown

A company name and a postal address appear on the page.

Served over HTTPS

The final URL uses TLS.

No WCAG A/AA violations found (21 rules passed)

axe-core found no violations of the WCAG 2.2 A/AA rules it can test automatically. Automated checks cover roughly a third of WCAG; manual review is still needed for the rest.

MethodStatic fetch. JavaScript was not executed. What the browser renders after load is not visible to this scan.
SitemapRead 26 URLs from sitemap.xml.
StackCloudflare, from response headers and the page. The header fix is written for it.
Third partiesFonts: Google Fonts. These are the processors a privacy policy for this site should name.
Accessibilityaxe-core (WCAG 2.2 A/AA). 0 violation types, 21 rules passed, 1 need manual review.
Design auditImpeccable browser detector. 0 findings in 19.2 s at 1280px.
Duration20.5 s

Or a free weekly re-scan of skytasks.pages.dev. An email only when a new issue appears.

Only change alerts, unsubscribe in any email. Privacy.

Share this report.

The link is public and shows the same free view you see here; nothing about the reader is recorded.

Post on XShare on LinkedIn

The certificate.

skytasks.pages.dev holds Clean Bill of Health WO-2026-4848, last checked November 22, 2026. Open it for the seal and what it verified.

Seal for skytasks.pages.dev

Put your score on your README.

An embeddable badge that re-checks weekly. Builders use it the way they use a CI badge: proof the boring stuff is handled.

Markdown
[![Webopsy](https://webopsy.tech/badge/skytasks.pages.dev)](https://webopsy.tech/s/skytasks.pages.dev)

Webopsy badge for skytasks.pages.dev