Skip to main content

Security report for gdata.es

Other · N/a

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

Security score

64/100

Risk levelMedium

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

The website www.gdata.es is currently inaccessible, returning a 403 Forbidden error with minimal HTML content served by nginx. This indicates that access is restricted, possibly by IP-based access control or server configuration. Due to this, no business information, metadata, or contact details are available for analysis. The WHOIS data is also unavailable because Red.es restricts WHOIS queries to authorized IP addresses only, preventing extraction of registrar, registrant, and domain status information. This lack of transparency and accessibility significantly limits the ability to assess the company's market position, services, or security posture. From a technical perspective, the site lacks any detectable technologies, scripts, or frameworks due to the blocked content. No security headers or HTTPS enforcement details are available, suggesting a basic or misconfigured hosting environment. The absence of privacy, cookie, or security policies further indicates a low level of digital maturity and compliance readiness. Security-wise, the site’s inaccessibility and lack of visible content or metadata prevent a thorough evaluation. However, the 403 Forbidden response and WHOIS access restrictions raise concerns about transparency and user accessibility. No explicit vulnerabilities or malicious indicators are detected, but the overall security posture is weak due to missing standard protections and policies. Overall, the website’s current state poses a high risk for trust and credibility. Strategic recommendations include resolving access restrictions to allow public viewing, enabling HTTPS with proper SSL certificates, publishing comprehensive privacy and security policies, and improving WHOIS transparency. These steps will enhance user trust, compliance, and security posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
15/ 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 gdata.es

This scan found 22 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
82
Security headers
30
Email security
70
DNS health
85
Network security
100
GDPR outside view
15
Average
64

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention gdata.es, from OffSeq Breach.

Total records
233
Employees
0
Customers
233
Third parties
0
Weak passwords
38%

2 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for gdata.es.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

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

Business context

Business profile

Due to the complete inaccessibility of the website and lack of WHOIS data, no meaningful business intelligence can be derived. The domain appears to be registered under the .es TLD with restricted WHOIS access, which is common for Spanish domains but limits transparency. No information about market positioning, competitive advantages, or business model is available. There is no evidence of partnerships, subsidiaries, or revenue streams. The lack of accessible content suggests either a misconfigured or restricted site rather than an active business presence.

Security posture

The security posture of www.gdata.es is currently poor due to the lack of accessible content and absence of security headers or HTTPS enforcement. The 403 Forbidden error indicates restrictive access controls, which may be intentional but reduce usability and transparency. The inability to access WHOIS data further complicates trust verification. No incident response contacts, vulnerability disclosures, or security policies are published. This suggests low security maturity and potential compliance gaps with GDPR and other regulations. Immediate improvements are needed to enable secure access, publish security documentation, and enhance transparency.

Recommendations

  1. Resolve the 403 Forbidden error to allow legitimate users and search engines to access the website content.
  2. Implement HTTPS with a valid SSL certificate to secure data in transit and improve trust.
  3. Publish comprehensive privacy and cookie policies to demonstrate GDPR compliance and transparency.
  4. Enable WHOIS data visibility or provide alternative domain ownership verification to improve legitimacy.
  5. Add security headers and conduct a security audit to identify and remediate vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Website returns a 403 Forbidden error with minimal HTML content served by nginx, indicating access is blocked or restricted. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
inconsistent

Technology

Performance
slow
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
10/100

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 completely inaccessible, returning HTTP 403 Forbidden error.
  2. No metadata, scripts, forms, or external links are present in the HTML content.
  3. WHOIS data is unavailable due to Red.es access restrictions, limiting domain ownership verification.
  4. No privacy, cookie, or security policies are found due to lack of accessible content.
  5. No contact information or business details are extractable from the site.
  6. No security headers or advanced configurations detected.
  7. Site appears to be either restricted by IP or misconfigured, blocking public access.
  8. No evidence of adult or explicit content.
  9. Overall website quality and security posture are poor due to inaccessibility.
Technical notes

Notes

The website currently serves only a minimal 403 Forbidden HTML page via nginx, indicating restrictive server configuration or IP-based access control. No CMS, frameworks, or scripts are detectable. The absence of metadata, Open Graph tags, or structured data points to a lack of SEO and digital marketing optimization. Performance and mobile optimization cannot be assessed due to inaccessible content. Hosting provider details are not discernible. Overall, the technical infrastructure appears basic or misconfigured, with significant modernization and configuration improvements required.
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 gdata.es. 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 gdata.es.

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.