Skip to main content

Security report for recaptcha.net

Technology · N/a

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

Security score

68/100

Risk levelMedium

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

The domain recaptcha.net is a long-established domain registered since 2007 and managed by Google infrastructure, consistent with the reCAPTCHA service. However, the website content is currently inaccessible, returning a 404 error page with no substantive content, policies, or contact information. This limits the ability to assess the business operations or user engagement features. The technical infrastructure appears to be hosted on Google servers, but no active content or scripts are present on the page. Security posture cannot be fully evaluated due to lack of content and security headers. Overall, the site appears legitimate based on domain registration data but is currently non-functional or misconfigured. From a technical perspective, the site lacks any visible technologies, frameworks, or CMS indications. The minimal HTML content is a standard Google 404 error page. No tracking, analytics, or advertising technologies are detected. The site is mobile responsive at a basic level due to the simple HTML and CSS used. Security evaluation is limited by the absence of content and headers. The domain uses Google name servers but does not have DNSSEC enabled. No privacy or cookie policies are present, and no contact or incident response information is available, which is a compliance gap. The domain registration is consistent and legitimate, but the site itself is not currently serving its intended purpose. Overall risk is low from a malicious perspective but high from a usability and compliance standpoint. Strategic recommendations include restoring proper website content, adding privacy and cookie policies, implementing security headers, and providing clear contact and incident response information to improve trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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

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

  2. GDPR outside view

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

    • 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

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

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

Keep watching recaptcha.net

This scan found 19 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
70
DNS health
90
Network security
100
GDPR outside view
40
Average
68

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 recaptcha.net is associated with Google's reCAPTCHA service, a widely used technology for bot detection and spam prevention. The domain age and registrar data confirm it is a legitimate domain under Google's control. The business model revolves around providing security services to websites through CAPTCHA challenges. The target audience includes website owners and developers seeking to protect their sites from automated abuse. The domain is part of the technology sector and likely serves an enterprise-scale user base globally. No direct business content or marketing information is present on the site itself, limiting further business intelligence insights. The domain is a critical infrastructure component rather than a customer-facing marketing site.

Security posture

The current security posture cannot be fully assessed due to the lack of accessible content and security headers. The domain uses HTTPS as implied by the URL but no explicit security headers are visible in the provided data. DNSSEC is not enabled, which is a minor security gap. No privacy or cookie policies are present, indicating compliance gaps. The domain registration is managed by a reputable registrar and uses Google name servers, which is a positive trust indicator. No incident response or vulnerability disclosure information is available. Overall, the security posture is incomplete and should be improved by adding security headers, enabling DNSSEC, and publishing relevant policies.

Recommendations

  1. Restore the website content to avoid 404 errors and improve user experience.
  2. Publish comprehensive privacy and cookie policies to enhance compliance with GDPR and other regulations.
  3. Implement security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Enable DNSSEC to improve DNS security and prevent spoofing.
  5. Provide clear contact information and incident response channels for security and abuse reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor

Technology

Mobile
basic
Accessibility
basic
SEO
poor

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

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 404 error.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact or security incident response information available.
  4. Domain is well-established and managed by Google infrastructure.
  5. No scripts, forms, or tracking technologies detected in the HTML content.
  6. Page is minimal and serves only as an error message.
Technical notes

Notes

The website currently serves only a minimal 404 error page with no active scripts, forms, or tracking technologies. The domain is hosted on Google infrastructure with Google name servers. No CMS or frameworks are detected. The page is mobile responsive at a basic level due to simple CSS. SEO optimization is poor due to lack of meta tags and content. Performance is likely fast given the minimal content but cannot be fully assessed. The lack of DNSSEC and security headers indicates technical debt in security configuration. The domain registration is consistent and appropriate for the business history.
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

Earlier scans of this domain

  1. 67/100 −1Medium30 findingsView report
  2. 68/100Medium28 findingsView report
  3. 68/100Medium23 findingsView report
Reviews of this site

Share your experience with recaptcha.net. 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 recaptcha.net.

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.