Skip to main content

Security report for ffconf.org

Left Logic · Technology · United Kingdom

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

Security score

57/100

Risk levelMedium

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

FFConf is a well-established UK-based web development conference organized by Left Logic, a small Brighton development company specializing in Node.js and front-end technologies. The conference focuses on curated sessions about the future of the web, targeting web developers and technology enthusiasts. The website reflects a professional and consistent brand with a clear event history dating back to 2009. The business model centers on event organization, community engagement, and content dissemination through talks, articles, and job listings. Technically, the website is custom-built without a CMS, leveraging modern web standards including HTML5, CSS3, and JavaScript. It uses Plausible Analytics for privacy-conscious visitor tracking and is hosted behind Cloudflare DNS and CDN services. The site is mobile optimized, accessible, and performs well with good SEO practices. However, some security enhancements such as DNSSEC and security headers are missing. From a security perspective, the site enforces HTTPS and uses domain transfer protection, but lacks explicit security headers and cookie consent mechanisms, indicating partial GDPR compliance. No direct contact emails or phone numbers are provided, limiting direct communication channels. No vulnerability disclosure or incident response policies are publicly available. Overall, the security posture is moderate with room for improvement. The overall risk assessment is low given the nature of the site as an informational and event platform with no sensitive transactions. Strategic recommendations include enabling DNSSEC, implementing security headers, adding cookie consent for GDPR compliance, and publishing security and incident response policies to enhance trust and compliance.

Scanned

NIS2 and GDPR posture

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

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

    • 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 ffconf.org

This scan found 27 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
52
Security headers
30
Email security
40
DNS health
70
Network security
100
GDPR outside view
50
Average
57

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

FFConf occupies a niche market as a UK web development conference with a strong community focus and a history spanning over a decade. Its competitive advantage lies in curated, high-quality sessions and a loyal audience of web professionals. The business model is event-driven with ancillary content offerings such as articles, job postings, and scholarships. Revenue likely derives from ticket sales and sponsorships. The target customers are web developers and tech enthusiasts primarily in the UK. The partnership ecosystem includes Left Logic as the organizing company. Growth indicators include consistent annual events and expanding digital content. The company operates as a small entity with a focused market presence.

Security posture

The security maturity level is moderate. HTTPS is enforced and domain transfer protection is enabled, which are positive indicators. However, the absence of DNSSEC and security headers such as Content-Security-Policy and Strict-Transport-Security reduces the overall security posture. No explicit privacy or cookie consent mechanisms are present, which may impact GDPR compliance. The lack of published incident response or vulnerability disclosure policies suggests limited formal security governance. Data collection is minimal and privacy-conscious via Plausible Analytics and a spam-protected newsletter form. No critical vulnerabilities or exposed sensitive data were detected.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to harden the website against common attacks.
  3. Add a clear cookie consent banner or mechanism to comply with GDPR and enhance user privacy transparency.
  4. Publish a security policy and vulnerability disclosure program to improve trust and incident response readiness.
  5. Provide direct contact information such as a security or abuse email address to facilitate communication and transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Left Logic
Description
FFConf is a one-day web development conference in Brighton, UK, featuring eight curated sessions on the future of the web.
Key services
Annual web development conference, Curated talks and sessions, Community articles and posts, Job listings, Scholarships and inclusion initiatives
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, Plausible Analytics
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • Spam bot detection on newsletter form

Analytics and tracking

Services
Plausible Analytics
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Plausible Analytics
Marketing tools
Newsletter subscription form
Transparency
basic

Site quality

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

Key observations

  1. Website is a well-established UK web development conference site.
  2. Content is rich with historical event data and community resources.
  3. No explicit privacy or cookie consent banners found, indicating partial GDPR compliance.
  4. No direct company contact emails or phone numbers found; contact via form only.
  5. No security.txt or vulnerability disclosure policy detected.
  6. Use of Plausible Analytics indicates privacy-conscious analytics choice.
  7. No suspicious or malicious content detected.
  8. Website is mobile optimized and accessible with skip links and semantic HTML.
Technical notes

Notes

The website is custom-developed with modern web technologies and good performance characteristics. It uses Cloudflare for DNS and likely CDN services, enhancing availability and speed. The tech stack includes HTML5, CSS3, JavaScript, and Plausible Analytics for privacy-focused tracking. The site is mobile responsive and accessible with semantic HTML and skip links. No CMS or frameworks were detected, indicating a bespoke solution. Technical risks include missing DNSSEC and security headers, which could be addressed to reduce attack surface. Overall, the infrastructure is solid with opportunities for security and compliance improvements.
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. 57/100Medium36 findingsView report
Reviews of this site

Share your experience with ffconf.org. 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 ffconf.org.

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.