Skip to main content

Security report for ginger.io

Digital Privacy Corporation · Healthcare · United States

Partial score · DNS & email only

75/100

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

The domain ginger.io is registered to Digital Privacy Corporation, a US-based entity founded in 2011, operating in the healthcare sector. However, the website content is currently inaccessible due to a 502 Bad Gateway error generated by Amazon CloudFront, preventing any direct analysis of the business's online presence, services, or policies. The lack of accessible content limits the ability to assess the company's market position, business model, or customer engagement strategies. Technically, the site is hosted behind Amazon CloudFront CDN, but no further technical details or technologies could be identified due to the error page. The absence of DNSSEC and security headers suggests room for improvement in domain and website security configurations. No metadata, structured data, or scripts were found, indicating either a misconfiguration or a temporary outage. From a security perspective, the site currently exhibits a low security posture due to the unavailability of content and lack of visible security best practices. The WHOIS data is consistent and publicly available, which supports legitimacy, but the lack of DNSSEC and website accessibility reduces overall trust. No privacy, cookie, or terms of service policies are detectable, which is a compliance concern. Overall, the site presents a high risk for users due to inaccessibility and lack of transparency. Strategic recommendations include resolving the server errors promptly, enabling DNSSEC, implementing security headers, and publishing comprehensive privacy and security policies to improve trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
6of 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. 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

    • 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

  2. 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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching ginger.io

This scan found 13 issues across 5 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
77
Email security
90
DNS health
75
Network security
100
GDPR outside view
50
Average
78
After the cap
75

Not counted

  • Security headers: did not complete in this scan.
  • 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

Due to the website's inaccessibility, detailed business intelligence is limited. The domain is registered to Digital Privacy Corporation, indicating a healthcare-related business likely focused on digital privacy or health technology. The domain age suggests an established presence since 2011. No information on revenue streams, partnerships, or customer segments is available from the site. The lack of accessible content and contact information hinders competitive analysis and market positioning insights.

Security posture

The current security posture is weak due to the website's inaccessibility and lack of visible security controls. The absence of DNSSEC and security headers, combined with a 502 error from CloudFront, indicates potential configuration or infrastructure issues. No incident response or vulnerability disclosure information is available. The domain registration is consistent and public, which is positive, but overall security maturity appears low. Compliance with GDPR or other regulations cannot be confirmed.

Recommendations

  1. Resolve the 502 Bad Gateway error to restore website accessibility immediately.
  2. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  3. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Publish comprehensive privacy, cookie, and terms of service policies to improve compliance and user trust.
  5. Establish and communicate incident response and vulnerability disclosure procedures to enhance security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

CloudFront detected. 502 Bad Gateway error generated by Amazon CloudFront indicating server connectivity or configuration issues. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Company
Digital Privacy Corporation
Description
No business description available due to inaccessible website content.
Content quality
poor

Technology

Security

Observed score
20/100

Analytics and tracking

Site quality

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

Key observations

  1. Website is currently inaccessible due to 502 Bad Gateway error from CloudFront.
  2. No metadata, structured data, or content available for analysis.
  3. No privacy, cookie, or terms of service policies found.
  4. No contact information or forms detected.
  5. Domain registration data is consistent and indicates a US-based company founded in 2011.
  6. Hosting is via Amazon CloudFront CDN.
  7. No security headers or SSL configuration details available from provided data.
  8. No advertising or analytics scripts detected due to lack of content.
  9. Content safety is rated safe based on absence of content.
Technical notes

Notes

The website is hosted on Amazon CloudFront CDN, but currently returns a 502 Bad Gateway error, indicating backend server connectivity or configuration issues. No CMS, frameworks, or scripts were detected due to the error page. DNSSEC is not enabled, which is a security gap. The lack of metadata and structured data suggests incomplete or misconfigured site deployment. Performance, mobile optimization, accessibility, and SEO cannot be assessed due to lack of content.
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 ginger.io. 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 ginger.io.

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.