Webopsy

This report was prepared for asim-group.com. It shows the top findings; the full report includes every issue and its fix.

90asim-group.com
100Privacy
92Security
98Legal
What the scores mean
Scanned Nov 22, 2026, 6:18 AM

No change since the scan on Nov 14, 2026.

Clean bill of health since Oct 2, 2026, serial WO-2026-0107. 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 4 security headers~15 min

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

Security Headers next.config.js
// next.config.js — Missing on your site: Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options. The Content-Security-Policy below already allows YouTube; add the domain of anything else you load to script-src or connect-src, then re-scan.
/** @type {import('next').NextConfig} */
const securityHeaders = [
  { key: 'Strict-Transport-Security', value: "max-age=63072000; includeSubDomains; preload" },
  { key: 'X-Content-Type-Options', value: "nosniff" },
  { key: 'X-Frame-Options', value: "SAMEORIGIN" },
  { key: 'Referrer-Policy', value: "strict-origin-when-cross-origin" },
  { key: 'Permissions-Policy', value: "camera=(), microphone=(), geolocation=()" },
  { key: 'Content-Security-Policy', value: "default-src 'self'; script-src 'self' 'unsafe-inline'; connect-src 'self'; img-src 'self' data: https: https://i.ytimg.com; style-src 'self' 'unsafe-inline'; font-src 'self' data:; frame-src https://www.youtube.com https://www.youtube-nocookie.com; frame-ancestors 'self'; base-uri 'self'; form-action 'self'" },
];

module.exports = {
  async headers() {
    return [{ source: '/:path*', headers: securityHeaders }];
  },
};
Next.js config (works on Vercel, Netlify, or a Node server). Then re-scan. The Content-Security-Policy is written for what the scan saw (YouTube); 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 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; 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, 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.

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.

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 asim-group.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 asim-group.comTrust page draft

Passed audits

(8)
Privacy policy is present

A privacy policy link or page was found.

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.

No mixed content

All referenced resources use HTTPS.

Email signup shows consent or privacy language

1 email field with consent or privacy wording on the page.

Served over HTTPS

The final URL uses TLS.

MethodRendered in scrapling StealthyFetcher. This looks like a client-rendered app, so the page was loaded in a browser and inspected after JavaScript ran.
SitemapNo sitemap.xml found.
StackNext.js on Vercel, from response headers and the page. The header fix is written for it.
Third partiesAnalytics: Vercel Analytics. Video: YouTube. These are the processors a privacy policy for this site should name.
AccessibilityNot run (no browser available).
Design auditNot run (no browser available).
Duration6.7 s

Or a free weekly re-scan of asim-group.com. 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.

asim-group.com holds Clean Bill of Health WO-2026-0107, last checked November 22, 2026. Open it for the seal and what it verified.

Seal for asim-group.com

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/asim-group.com)](https://webopsy.tech/s/asim-group.com)

Webopsy badge for asim-group.com