Skip to main content

Security report for dryjuly.com

Dry July Foundation · Non-profit · Australia

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

Security score

73/100

Risk levelMedium

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

Dry July Foundation operates a well-established non-profit fundraising campaign encouraging participants to abstain from alcohol in July to raise funds for cancer support services. The website is professionally designed, mobile-optimized, and rich in content, providing clear calls to action, participant leaderboards, and fundraising resources. The technical infrastructure leverages modern analytics, marketing, and payment technologies including Google Tag Manager, Facebook Pixel, Braintree, and Apple Pay, hosted via Amazon CloudFront CDN. Security posture is strong with HTTPS, secure form validations, and CSRF protections, though explicit cookie consent mechanisms and vulnerability disclosure policies are absent. WHOIS data is missing or unavailable, which slightly reduces domain trustworthiness but does not detract from the legitimacy of the campaign as evidenced by the website content and external references.

Scanned

NIS2 and GDPR posture

GDPR outside view
65/ 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

5 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 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

  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 dryjuly.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
30
Email security
90
DNS health
80
Network security
100
GDPR outside view
65
Average
73

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 dryjuly.com, from OffSeq Breach.

Total records
128
Employees
0
Customers
128
Third parties
0
Weak passwords
10%

3 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 dryjuly.com.

Select it in the checkout above.

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

Technical appendix

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

Business context

Business profile

Dry July Foundation targets individuals and teams motivated to support cancer patients by fundraising through alcohol abstinence. The campaign has a strong market position in the non-profit sector with significant fundraising achievements and community engagement. Revenue streams are primarily donations collected via the platform. The organization uses partnerships with payment processors and marketing platforms to enhance user experience and fundraising effectiveness. The website's clear navigation, comprehensive content, and social media presence support growth and outreach efforts.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, secure password policies, CSRF tokens, and no visible sensitive data exposure. Use of reputable third-party analytics and marketing scripts is balanced with security best practices. However, the absence of a published vulnerability disclosure policy and incident response contact information represents a compliance gap. Cookie consent mechanisms are not evident, which may impact GDPR compliance. Overall, the site is secure but could improve transparency and user privacy controls.

Recommendations

  1. Implement a visible cookie consent banner to comply with GDPR and enhance user privacy transparency.
  2. Publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  3. Provide clear incident response contact information, such as a security or abuse email address.
  4. Add or verify Content-Security-Policy headers to mitigate cross-site scripting and related attacks.
  5. Regularly audit and update third-party scripts to minimize risk from vulnerable dependencies.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Dry July Foundation
Description
Dry July is a free fundraiser that challenges participants to go alcohol-free in July to raise funds for people affected by cancer. The funds raised improve comfort, care, and wellbeing for cancer patients and their families.
Key services
Fundraising platform for individuals and teams, Donation collection and management, Fundraising resources and support, Community engagement via Inspiration Wall and leaderboards
Content quality
excellent
Branding
consistent

Technology

Stack
Google Tag Manager, Google Analytics, Facebook Pixel, TikTok Pixel, LinkedIn Insight Tag, Hotjar, Braintree Payment Gateway, Apple Pay SDK, jQuery, Parsley.js (form validation), Bootstrap (CSS framework), Cloudinary (image hosting), Intercom (customer messaging)
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Secure password requirements on sign-up
  • Use of CSRF tokens in forms
  • No exposed sensitive data in HTML
  • Use of reputable third-party security and analytics scripts

Analytics and tracking

Services
Google Analytics, Facebook Pixel, TikTok Pixel, LinkedIn Insight Tag, Hotjar
Tracking level
extensive
Privacy practices
basic

Advertising

Ad networks
Google Ads, LinkedIn Ads, Facebook Ads, TikTok Ads, Reddit Ads, Yahoo Ads, AdsWizz
Tracking pixels
Facebook Pixel, TikTok Pixel, LinkedIn Insight Tag, Hotjar, AdsWizz
Marketing tools
Intercom
Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is a well-established non-profit fundraising platform for cancer support.
  2. Content is rich, professionally designed, and mobile optimized.
  3. Strong use of third-party analytics and marketing tools.
  4. No direct contact emails or phone numbers found on the main pages.
  5. WHOIS data is missing or domain appears unregistered in the raw WHOIS output.
  6. No explicit cookie consent banner detected despite tracking scripts.
  7. Security posture is strong with HTTPS and secure form validations.
  8. No vulnerability disclosure or incident response information publicly available.
Technical notes

Notes

The website is built on a modern technology stack likely including Ruby on Rails, with extensive use of JavaScript libraries and third-party services for analytics, marketing, and payments. Hosting via Amazon CloudFront CDN ensures fast content delivery. The site is mobile responsive and accessible, with good SEO practices evident in meta tags and structured content. Form validations use Parsley.js for client-side checks. Performance is fast with no broken elements detected. Opportunities exist to enhance security headers and privacy compliance 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 dryjuly.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 dryjuly.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.