Skip to main content

Security report for oxystc.com

Other · N/a

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

Security score

66/100

Risk levelMedium

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

The analyzed URL leads to a Google CAPTCHA challenge page triggered by detection of unusual traffic from the user's network. This page is designed to verify human users and block automated bots. As such, no actual business content or website data is accessible for analysis. The domain www.google.com is a globally recognized and trusted domain owned by Google LLC, but WHOIS data is restricted by the VeriSign registry, which is standard for high-profile domains. The technical infrastructure includes Google reCAPTCHA scripts to mitigate automated abuse. Due to the blocking mechanism, no privacy, cookie, or terms of service policies are visible, and no contact or business information can be extracted. The security posture of the actual Google domain is presumed strong, but this specific page only serves as a security checkpoint. Overall, the site is safe with no adult or questionable content detected, but the analysis is limited by the access restrictions.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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

8 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

  2. 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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';…

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

Keep watching oxystc.com

This scan found 18 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. The full timeline opens with your unlock code.

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
25
Email security
83
DNS health
90
Network security
100
GDPR outside view
25
Average
66

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 www.google.com represents one of the largest technology companies globally, Google LLC. The domain is foundational to Google's search engine and related services. The CAPTCHA page is part of Google's security ecosystem to protect its services from abuse. No direct business model or revenue stream information is available from this page. The target audience for the CAPTCHA page is general internet users who trigger automated traffic detection. The domain's market position is dominant in search and online services. No partnership or subsidiary domains are referenced on this page.

Security posture

The presence of Google reCAPTCHA indicates a mature security posture focused on bot mitigation and abuse prevention. The page uses HTTPS and loads scripts from trusted Google domains. However, no additional security headers or policies are visible in the provided content. The WHOIS data is restricted, which is typical for high-profile domains to protect registrant privacy. No vulnerabilities or exposed sensitive data are detected on this page. Incident response and security policy information are not available here but are expected to be robust given Google's reputation.

Recommendations

  1. For users encountering this page frequently, investigate network behavior to reduce automated traffic triggers.
  2. Ensure that actual business websites behind CAPTCHA challenges provide clear privacy and cookie policies.
  3. Implement visible contact and incident response information on accessible pages to improve trust.
  4. Maintain updated security headers and SSL configurations on all public-facing pages.
  5. Consider user experience improvements to reduce CAPTCHA frequency while maintaining security.
Site observations

Automated reading of the public site. Ratings are indicative.

Google reCAPTCHA detected. Page is a Google CAPTCHA challenge indicating unusual traffic detected and blocking automated access. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
reCAPTCHA, JavaScript

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to Google CAPTCHA challenge page.
  2. No business or contact information is available on this page.
  3. No privacy, cookie, or terms of service policies are present on this page.
  4. The page is served by Google infrastructure and uses Google reCAPTCHA for bot mitigation.
  5. No external business-related domains or suspicious links found beyond Google domains.
  6. No analytics or advertising scripts detected beyond reCAPTCHA.
  7. WHOIS data is unavailable due to registry restrictions, typical for google.com domain.
  8. Content safety is high as no adult or questionable content is present.
  9. Overall analysis is limited due to blocked content and lack of accessible website data.
Technical notes

Notes

The page is a minimal HTML document serving a Google reCAPTCHA challenge. It loads JavaScript from Google's gstatic and google.com domains to render the CAPTCHA widget. No CMS or third-party advertising or analytics scripts are detected beyond reCAPTCHA. The hosting provider is Google, ensuring high availability and performance. The page lacks typical SEO metadata or structured data due to its nature as a security checkpoint. Accessibility and mobile optimization cannot be fully assessed but the page uses basic responsive meta tags. The technical implementation is focused solely on security verification rather than content delivery.
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 oxystc.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 oxystc.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.