Skip to main content

Security report for uzwei.com

Other · Germany

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

75/100

Risk levelMedium

0–100, higher is better. How it is calculated

This website is a Google consent management page used to handle user privacy and consent preferences, particularly related to Google Maps and associated services. It is part of Google's infrastructure to comply with privacy regulations such as GDPR. The page itself does not contain typical business content but serves as a gateway for user consent management. The technical infrastructure is robust, leveraging Google's global hosting and security capabilities. However, the page is a security challenge or consent gate, limiting direct content access and business information visibility. Security posture is strong with HTTPS and CSP usage, but explicit security headers are not visible in the provided data. Privacy compliance indicators are minimal on this page alone, as it is a functional consent interface rather than a full website. Overall, the page is legitimate and trustworthy as part of Google's ecosystem but cannot be fully analyzed for business or compliance details due to its nature as a consent gate.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

4 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

Need hands-on remediation? Email guard@offseq.com

Keep watching uzwei.com

This scan found 17 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
75
Security headers
35
Email security
83
DNS health
90
Network security
100
GDPR outside view
68
Average
75

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The domain is a subdomain of google.com, owned by Google LLC, a global technology enterprise. This subdomain is dedicated to consent management, indicating a focus on privacy compliance and regulatory adherence. The business model behind this page is service-oriented, supporting Google's broader ecosystem of products by managing user consent for data processing. There are no direct revenue streams or customer engagement features on this page. The target audience is end-users of Google services in the EU and other regulated regions. The page reflects Google's commitment to privacy and regulatory compliance but does not provide direct business or market positioning information. The lack of visible business contact or policy documents on this page is consistent with its role as a consent interface rather than a standalone business site.

Security posture

The security posture of this page is strong, leveraging HTTPS and Google’s secure infrastructure. The presence of Content Security Policy scripts and enforcement of consent mechanisms indicate adherence to security best practices. However, explicit security headers like HSTS, X-Content-Type-Options, or X-Frame-Options were not detected in the provided data, which could be improved. The page does not expose sensitive data or vulnerable libraries. The main security concern is the page acting as a WAF or consent gate, which restricts content access but is a legitimate security measure. No vulnerabilities or compliance gaps were identified on this page. Incident response and security policy information are not present, which is typical for such a service page.

Recommendations

  1. Implement and explicitly expose security headers such as HSTS, X-Content-Type-Options, and X-Frame-Options to enhance security posture.
  2. Provide direct links or access to comprehensive privacy and cookie policies on or near the consent interface for better transparency.
  3. Include clear business contact information or links to support channels to improve trust and compliance visibility.
  4. Enhance accessibility features to improve user experience for all users, including those with disabilities.
  5. Maintain and regularly audit consent mechanisms to ensure ongoing compliance with evolving privacy regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. The page is a Google consent/security challenge page that restricts access to the actual content. It contains scripts and UI elements related to consent management, indicating a WAF or security mechanism blocking direct content access. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
basic
Branding
consistent

Technology

Stack
JavaScript, XMLHttpRequest, Google APIs
Frameworks
Material Design Components (MDC)
Platforms
Google Consent UI
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Content Security Policy (CSP) usage

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
poor
Navigation
poor
Professionalism
basic
Trustworthiness
high

Key observations

  1. The page is a Google consent management interface, not a typical business website.
  2. Content is minimal and focused on user consent and privacy compliance.
  3. No direct business contact information or policies are present on this page.
  4. The page is served by Google infrastructure with strong HTTPS and security practices.
  5. WHOIS data for the subdomain is not available, consistent with it being a Google subdomain.
  6. The page is likely part of a WAF or consent gateway, blocking direct content access.
Technical notes

Notes

The page uses modern JavaScript, XMLHttpRequest, and Google APIs to manage consent UI dynamically. Material Design Components (MDC) are used for UI styling and interaction. The hosting is on Google infrastructure, ensuring high availability and security. Performance is moderate due to the complexity of scripts and dynamic content loading. Mobile optimization is good, but accessibility and SEO optimizations are basic. The page is a functional consent gateway rather than a content-rich website, limiting content analysis. No CMS or third-party hosting providers were detected. The technical stack is mature and consistent with Google's standards but could benefit from enhanced accessibility and SEO features.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with uzwei.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review uzwei.com.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.