Skip to main content

Security report for digitalfreedomfestival.com

Other · N/a

Medium risk. 8 critical or high findings in Email security, Security headers and 2 other checks.

Security score

63/100

Risk levelMedium

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

The website at digitalfreedomfestival.com/lander is a minimal landing page with very limited content, primarily serving as a placeholder. The domain is newly registered in August 2023 via GoDaddy.com, LLC, indicating a recent launch or preparation phase. The site uses a JavaScript-based landing page framework (PW) and includes Google AdSense scripts for advertising. There is no visible business information, contact details, or privacy-related policies, which limits the ability to assess the business comprehensively. From a technical perspective, the site is basic with moderate performance and mobile optimization. It lacks DNSSEC and security headers, which are important for enhancing domain and website security. The SSL configuration is basic but present, ensuring HTTPS is enabled. SEO and accessibility features are minimal, and no structured data or metadata beyond basic HTML tags are present. Security posture is moderate due to HTTPS presence but weakened by missing security headers and lack of privacy and cookie policies. No forms or data collection mechanisms are detected, reducing immediate data protection concerns but also indicating limited user engagement. The absence of contact or incident response information suggests low transparency and preparedness for security incidents. Overall, the website appears to be in an early stage or a placeholder with low content and business credibility. Strategic recommendations include adding comprehensive privacy and cookie policies, implementing security headers, enabling DNSSEC, and providing clear contact and business 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

8 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

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

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

Keep watching digitalfreedomfestival.com

This scan found 24 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
77
Security headers
25
Email security
60
DNS health
75
Network security
100
GDPR outside view
40
Average
63

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 business behind digitalfreedomfestival.com appears to be either newly established or in a preparatory phase, given the recent domain registration and minimal website content. No explicit company name, legal entity, or sector information is available. The site seems targeted at a general audience possibly related to a digital freedom event or festival, but no concrete business model or services are described. The use of Google AdSense suggests a monetization strategy based on advertising. There is no evidence of partnerships, subsidiaries, or parent companies. The lack of business details and contact information limits competitive analysis and market positioning insights.

Security posture

The current security posture is basic. HTTPS is enabled, which is mandatory and provides a secure transport layer. However, the absence of DNSSEC leaves the domain vulnerable to DNS spoofing attacks. No security headers such as Content-Security-Policy, X-Frame-Options, or Strict-Transport-Security are detected, which are critical for mitigating common web vulnerabilities. No forms or input fields are present, reducing attack surface but also limiting user interaction. The lack of privacy and cookie policies indicates non-compliance with GDPR and other data protection regulations. Incident response and security contact information are missing, which is a gap in security culture and readiness. Overall, the site requires significant improvements to meet standard security best practices.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement essential security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish comprehensive privacy and cookie policies to comply with GDPR and build user trust.
  4. Add clear contact information and incident response contacts to improve transparency and security readiness.
  5. Enhance website content quality, SEO metadata, and accessibility features to improve user experience and search engine ranking.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
inconsistent

Technology

Stack
JavaScript
Frameworks
PW
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
55/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Ad networks
Google AdSense
Transparency
poor

Site quality

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

Key observations

  1. Website content is minimal and appears to be a placeholder or landing page.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact information or forms detected.
  4. Uses Google AdSense for advertising.
  5. No security headers detected; DNSSEC not enabled.
  6. Domain is newly registered with GoDaddy and has standard domain status prohibitions.
  7. No social media or external business links found except Google and hosting CDN.
  8. Website uses a JavaScript-based landing page system (PW framework).
  9. No visible business or branding information on the page.
Technical notes

Notes

The website uses a JavaScript-based landing page framework identified as 'PW' and loads scripts and styles from a wsimg.com domain, indicating use of a third-party hosting or landing page service. The domain is hosted via GoDaddy.com, LLC. The HTML content is minimal with no metadata beyond charset and viewport tags. No CMS or advanced frameworks are detected. Performance is moderate given the minimal content. Mobile optimization is basic due to viewport meta tag but no further responsive design cues. SEO is poor due to lack of meta descriptions, titles, or structured data. Accessibility is basic with no ARIA roles or landmarks. The site relies on Google AdSense for advertising, indicating some monetization but no analytics or tracking services detected. Overall, the technical implementation is minimal and could benefit from modernization and content enrichment.
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 digitalfreedomfestival.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 digitalfreedomfestival.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.