Skip to main content

Security report for fossy.us

Software Freedom Conservancy · Technology · United States

Medium risk. 5 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

57/100

Risk levelMedium

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

The website 2025.fossy.us represents the FOSSY 2025 conference, a community-oriented event focused on free and open source software, hosted by the Software Freedom Conservancy. The event is scheduled for July 31st to August 3rd, 2025, at Portland State University. The site provides information about the conference, registration, sponsorship, and related logistics, targeting open source contributors and enthusiasts. The business model is non-profit and community-driven, with a clear focus on fostering open source software development and collaboration. Technically, the website uses a modern but straightforward tech stack including Bootstrap, jQuery, FontAwesome, and Tachyons CSS. The site is mobile-optimized with good navigation and professional design. External resources are loaded from reputable CDNs, and no major performance or accessibility issues are evident. However, some improvements could be made in accessibility and SEO optimization. From a security perspective, the site uses HTTPS (implied by the URL), but no explicit security headers were detected in the provided data. There is no visible security.txt or incident response contact information. The WHOIS data is unavailable, likely due to privacy protection, which is reasonable for this type of non-profit event. No vulnerabilities or exposed sensitive data were found in the HTML content. Privacy compliance is partial, with a privacy policy linked externally but no cookie consent mechanism on the site. Overall, the website is trustworthy and professionally presented, with a moderate to good security posture and privacy compliance. Recommendations include adding security headers, implementing cookie consent, and publishing vulnerability disclosure information to enhance trust and compliance.

Scanned

NIS2 and GDPR posture

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

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

  3. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Weak SPF Policy

      SPF record has permissive policy allowing any server to send email

      What to do: Use -all or ~all qualifier for better email security

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

Keep watching fossy.us

This scan found 25 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
52
Security headers
70
Email security
70
DNS health
55
Network security
40
GDPR outside view
53
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

FOSSY 2025 is positioned as a niche community conference within the open source software ecosystem, organized by the Software Freedom Conservancy, a known non-profit entity. The business model revolves around event hosting and community engagement, with sponsorship as a revenue stream. The target audience includes open source contributors of all experience levels. The partnership with Software Freedom Conservancy strengthens credibility and provides organizational support. The website content and structure reflect a focused and professional approach, with clear calls to action for registration and sponsorship. Growth indicators include recurring event history and community involvement. The absence of phone contact and limited direct business information is typical for non-profit event sites.

Security posture

The security maturity level is moderate. The site uses HTTPS, but lacks visible security headers such as Content Security Policy or HSTS. No forms or inputs are present on the homepage, reducing attack surface. No incident response or vulnerability disclosure information is provided, which is a gap in security transparency. The WHOIS data is privacy protected, which is acceptable for this entity type. No malware or phishing indicators were found. Privacy compliance is partial, with a privacy policy linked but no cookie consent mechanism. Overall, the site demonstrates basic security hygiene but could improve in headers, incident response readiness, and privacy compliance.

Recommendations

  1. Implement HTTP security headers including Content Security Policy, HSTS, and X-Frame-Options.
  2. Add a cookie consent banner or mechanism to comply with privacy regulations.
  3. Publish a security.txt file or vulnerability disclosure policy to improve incident response transparency.
  4. Enhance accessibility features to meet WCAG standards for broader inclusivity.
  5. Verify and monitor SSL/TLS configuration regularly to maintain strong encryption standards.

Contact details published on the site

Addresses
Legal name
Software Freedom Conservancy
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Software Freedom Conservancy
Description
FOSSY 2025 is the third Free and Open Source Software Yearly conference hosted by Software Freedom Conservancy, focused on free and open source software community and contributors. The event is scheduled for July 31st - August 3rd, 2025 at Portland State University.
Key services
Conference hosting, Community engagement, Sponsorship opportunities
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, Bootstrap, jQuery, FontAwesome, Tachyons CSS
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. WHOIS data is unavailable, indicating privacy protection or registry limitations.
  3. Website content is focused on a community open source software conference.
  4. No forms detected on the homepage; registration and ticketing likely handled on subpages.
  5. No cookie consent mechanism detected despite external privacy policy link.
  6. No visible security.txt or incident response contact information.
  7. Social media presence includes Twitter and Mastodon linked in footer.
  8. No phone numbers or physical office addresses explicitly provided on homepage.
  9. External resources loaded from reputable CDNs and official domains.
  10. No advertising or tracking scripts detected.
Technical notes

Notes

The website is built with standard web technologies including HTML5, CSS3, Bootstrap framework, jQuery, and FontAwesome icons. It loads external resources from trusted CDNs, which supports performance and reliability. The site is mobile responsive and has a clear navigation structure. No CMS or backend technology is explicitly detected from the HTML content. Performance is moderate, with no heavy scripts or tracking detected. The site lacks advanced SEO features and accessibility enhancements but is overall well-structured and professional. Technical debt appears low, but improvements in security headers and privacy compliance are recommended.
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 fossy.us. 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 fossy.us.

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.