Skip to main content

Security report for freshsource.org

Dan Langille · Technology · N/a

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

Security score

71/100

Risk levelMedium

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

FreshSource is a specialized project focused on tracking source code changes, primarily for the FreeBSD operating system. It offers features such as watch lists and notifications for source tree changes, targeting developers and users interested in FreeBSD ports and source updates. The website is maintained by Dan Langille and includes affiliate marketing through Amazon Associates. The site content is technical and niche, serving a small but dedicated community.

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

4 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 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. 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 freshsource.org

This scan found 22 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
85
Security headers
65
Email security
60
DNS health
60
Network security
100
GDPR outside view
53
Average
71

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 operates as a small-scale, community-driven project with a focus on open source software development. Its revenue model includes donations and affiliate marketing. The project leverages existing FreeBSD infrastructure and mailing lists to provide value to its users. The website's market position is niche, catering to FreeBSD developers and enthusiasts. There is no indication of a larger corporate structure or subsidiaries. The site maintains a consistent brand and provides validated technical content.

Security posture

The website currently lacks visible security headers and does not provide HTTPS status information in the data provided. No contact information for security incidents or policies is published. The absence of a cookie consent mechanism and limited privacy compliance features indicate room for improvement. No vulnerabilities or exposed sensitive data were detected in the content. The WHOIS data is missing, which reduces domain trustworthiness but does not necessarily indicate malicious intent. Overall, the security posture is moderate but could benefit from enhancements in HTTPS enforcement, security headers, and privacy compliance.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate and ensure all pages are served securely.
  2. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish a cookie policy and implement a consent mechanism to comply with privacy regulations.
  4. Provide clear contact information for security incidents and a published security policy.
  5. Improve WHOIS data availability or use a registrar that provides complete WHOIS information to enhance domain trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Dan Langille
Description
FreshSource is a project that allows tracking of source code changes, primarily focused on FreeBSD source trees, providing watch lists and notifications for code commits.
Key services
Source code change tracking, Watch lists for source tree portions, Commit notifications, RSS news feeds
Content quality
good
Branding
consistent

Technology

Stack
HTML 4.01, CSS, JavaScript, Google Analytics (gtag.js)
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • No forms with sensitive inputs detected
  • No exposed emails or phone numbers

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Amazon Associates
Transparency
basic

Site quality

Design
basic
User experience
basic
Content relevance
good
Navigation
good
Professionalism
basic
Trustworthiness
moderate

Key observations

  1. Website is a niche technical resource focused on FreeBSD source code tracking.
  2. Content is accessible and not blocked by WAF or security mechanisms.
  3. No contact emails or phone numbers explicitly provided on the site.
  4. Privacy policy page exists but cookie policy and terms of service are missing.
  5. Use of Google Analytics and Amazon Associates affiliate links detected.
  6. WHOIS data is unavailable, limiting domain trust verification.
  7. Website uses older HTML standards but is functional and validated.
  8. No security headers or HTTPS status information available from provided data.
Technical notes

Notes

The website uses classic HTML 4.01 and CSS with some JavaScript for Google Analytics tracking. The site is validated for HTML and CSS standards but lacks modern frameworks or CMS platforms. Performance is moderate with basic mobile optimization and accessibility features. The site structure is clear and navigation is straightforward. There is no evidence of hosting provider details or advanced technical infrastructure. The use of affiliate marketing and analytics is standard for small community sites.
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. 71/100Medium31 findingsView report
Reviews of this site

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