This report was prepared for limitry.com. It shows the top findings; the full report includes every issue and its fix.
What the scores mean
Clean bill of health since Nov 22, 2026, serial WO-2026-5218. View the certificate
Opportunities
No critical or high-severity issues. That's the bar most sites miss.
Diagnostics
Worth fixing. Not an emergency.
No postal address for the business~5 min
Sites that take money or serve EU/German users are expected to show who runs them and where. It also unblocks Stripe and app-store reviews.
GDPR Art. 13(1)(a) (controller identity); German TMG §5 Impressum; EU e-Commerce Directive Art. 5; consumer-protection rules in most countries.
What these findings expose you to
For scale: the privacy items fall under GDPR's top tier (up to 4% of turnover; small-business fines for missing notices and cookie consent have run from the low thousands of euros upward) and, for California users, CalOPPA at up to $2,500 per violation and CCPA at roughly $2,500 to $7,500 per violation once you pass its thresholds. 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, transparency and consent · EU, EEA, UK1 finding
Maximum. Up to €20 million or 4% of worldwide annual turnover, whichever is higher (Art. 83(5)); UK: up to £17.5 million or 4%.
Usually. A complaint to a data-protection authority, then a notice with a deadline to fix. Published fines against small businesses for missing notices and cookie consent have run from the low thousands of euros upward; the largest cookie-consent fines have been in the tens of millions.
Applies: Any site with users in the EU or UK, regardless of where the company is. Enforced by regulators.
AI design tells
1 pattern on this page read as AI-generated: Hairline border with wide shadow. Visitors have learned to recognize these; they read as a template and cost trust. Each one has a specific fix.
Hairline border with wide shadow1×
A hairline border paired with a wide, diffuse shadow is a recurring generated-UI signature. Commit to one — a defined edge or a soft elevation — rather than both at once.
Example: 1px border + 32px shadow blur
Full annotated page (1 labels)

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 limitry.com 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 limitry.comTrust page draftPassed audits
(11)
Privacy policy is present
A privacy policy link or page was found.
Privacy policy covers the expected disclosures
920 words; 14 disclosure checks passed; last updated 21 November 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.
4 security headers set
Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options
No mixed content
All referenced resources use HTTPS.
security.txt published
Researchers know where to report a vulnerability.
Served over HTTPS
The final URL uses TLS.
No WCAG A/AA violations found (28 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.
Share this report.
The link is public and shows the same free view you see here; nothing about the reader is recorded.
The certificate.
limitry.com holds Clean Bill of Health WO-2026-5218, last checked November 22, 2026. Open it for the seal and what it verified.
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.
[](https://webopsy.tech/s/limitry.com)