Skip to main content

Security report for unencumberedbyfacts.com

Technology · N/a

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

63/100

Risk levelMedium

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

Unencumbered by Facts is a personal technology blog primarily focused on open source webmail client development and related software topics. The site is authored by Jason Munro and hosted on WordPress.com, leveraging standard WordPress technologies such as PHP, JavaScript, and CSS. The blog features detailed posts about software projects, personal anecdotes, and technical insights, targeting developers and technology enthusiasts interested in open source email clients and related protocols. The website has a consistent branding and good content quality, though it lacks formal business contact information and privacy policies.

Scanned

NIS2 and GDPR posture

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

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

    • High

      No DMARC record found

      DMARC provides email authentication and reporting

      What to do: Add DMARC record: "v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com"

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

Keep watching unencumberedbyfacts.com

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. 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
42
Security headers
30
Email security
65
DNS health
85
Network security
100
GDPR outside view
58
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 website operates as a small personal blog without a formal business model or commercial services. It serves a niche audience of open source developers and hobbyists. The blog's market position is modest, with a focus on sharing knowledge and project updates rather than monetization. There are no evident partnerships or subsidiaries linked to the domain. The content is regularly updated with technical posts, indicating active engagement with the community. The lack of formal business contact details and policies suggests a primarily personal or hobbyist operation rather than a commercial enterprise.

Security posture

The site uses HTTPS and is hosted on WordPress.com, providing a baseline of security. However, the absence of security headers such as Content-Security-Policy and X-Frame-Options reduces the overall security posture. No privacy or cookie policies are present, which is a compliance gap. There is no visible incident response or vulnerability disclosure information, limiting transparency. The site does not expose sensitive data or use vulnerable libraries based on the HTML content. Overall, the security posture is moderate but could be improved by implementing security best practices and compliance documentation.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy to improve compliance and user trust.
  2. Add security headers like Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to enhance protection against common web attacks.
  3. Provide clear contact information and incident response channels to improve transparency and user confidence.
  4. Regularly audit and update all plugins and themes to mitigate potential vulnerabilities.
  5. Consider enabling DNSSEC for the domain to strengthen DNS security.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
A personal blog focused on software development, particularly open source webmail client development, and personal anecdotes.
Key services
Blog content, Open source project updates
Content quality
good
Branding
consistent

Technology

Stack
WordPress, PHP, JavaScript, CSS, HTML5
Frameworks
Gutenberg, Jetpack
Platforms
WordPress.com
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML

Analytics and tracking

Services
WordPress.com Stats
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
WordPress.com Stats
Transparency
basic

Site quality

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

Key observations

  1. Website is a personal blog focused on open source webmail client development and personal tech stories.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. No explicit contact information such as emails or phone numbers found.
  4. Site uses WordPress.com hosting and standard WordPress technologies.
  5. No security headers detected in the HTML content.
  6. No evidence of vulnerability disclosure or security incident response information.
  7. Content is safe and suitable for general audiences.
  8. Site includes a poll widget and social interaction features via WordPress.com.
  9. No advertising networks detected beyond WordPress.com native features.
  10. Analytics usage limited to WordPress.com stats tracking.
Technical notes

Notes

The website is built on WordPress.com using PHP, JavaScript, and CSS with Gutenberg and Jetpack plugins. The hosting provider is WordPress.com, ensuring reliable infrastructure and HTTPS support. The site performance is moderate with good mobile optimization and basic accessibility features. SEO optimization is basic with proper meta tags but no advanced structured data beyond Open Graph tags. The site uses standard WordPress.com analytics and tracking pixels. There is no evidence of technical debt or outdated technologies, but security headers and compliance documentation are lacking, representing modernization opportunities.
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 unencumberedbyfacts.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 unencumberedbyfacts.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.