Skip to main content

Security report for theresnotime.co.uk

Sammy Fox · Technology · United Kingdom

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

Security score

68/100

Risk levelMedium

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

The website 'theresnotime.co.uk' serves as a personal professional portfolio and blog for Sammy Fox, a software engineer affiliated with the Wikimedia Foundation. The site targets a general audience interested in technology, open source, and community engagement, showcasing professional projects, social profiles, and personal interests. The business model is individual-centric, focusing on personal branding and community contributions rather than commercial services. Technically, the site employs modern web standards including HTML5, CSS3, JavaScript, and JSON-LD structured data. It references technologies such as Python, Node.js, and PHP through linked projects and packages. Hosting appears to be provided by Mythic Beasts, and the site uses HTTPS with strong SSL configuration. Performance and mobile optimization are good, though accessibility features are basic. SEO is well addressed through meta tags and structured data. From a security perspective, the site benefits from HTTPS and publishes a public PGP key, indicating a commitment to secure communications. However, no explicit security headers were detected, and there is no cookie consent mechanism despite the use of tracking pixels. The WHOIS data is unavailable due to domain naming rules violations, which raises questions about domain registration legitimacy but does not directly impact the website's content quality or security posture. Overall, the website is professional, trustworthy, and safe for general audiences. The main risks relate to privacy compliance and domain registration transparency. Strategic recommendations include implementing security headers, adding a cookie consent mechanism, publishing security and incident response policies, and clarifying domain registration status to enhance trust.

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

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

    • 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

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

Keep watching theresnotime.co.uk

This scan found 21 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
65
Security headers
30
Email security
75
DNS health
85
Network security
100
GDPR outside view
50
Average
68

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 represents an individual professional operating in the technology sector with a focus on software engineering and open source contributions. The market positioning is niche and community-oriented, leveraging affiliations with Wikimedia Foundation and related organizations. Revenue streams are not evident, suggesting a non-commercial or personal branding focus. The target customer segment includes technology enthusiasts, open source contributors, and the queer community. Growth indicators include active social profiles and multiple linked projects. The partnership ecosystem is broad, including Wikimedia entities and various community sites. Strategic observations highlight a strong personal brand with credible affiliations but limited commercial presence.

Security posture

The security maturity level is moderate. The site enforces HTTPS and publishes a public PGP key, which are positive indicators. However, the absence of security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options reduces the overall security posture. No forms or inputs collect sensitive data, minimizing attack surface. Privacy compliance is partial, lacking cookie consent mechanisms despite tracking pixels. Incident response and vulnerability disclosure policies are not published, indicating gaps in security governance. The WHOIS domain registration inconsistency is a concern but does not directly affect operational security. Overall, the security culture appears conscientious but could benefit from formalized policies and technical enhancements.

Recommendations

  1. Implement standard security headers including CSP, HSTS, and X-Frame-Options to enhance protection against common web attacks.
  2. Add a cookie policy and consent mechanism to comply with privacy regulations and improve user transparency.
  3. Publish a formal security policy and incident response plan to demonstrate security governance and readiness.
  4. Create and maintain a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  5. Clarify domain registration status and resolve WHOIS inconsistencies to strengthen trust and legitimacy.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Sammy Fox
Description
A 30-something, quintessentially queer software engineer at the Wikimedia Foundation.
Key services
Software engineering, Open source contributions, Blogging, Community engagement
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, FontAwesome, JSON-LD, Node.js (npm packages referenced), Python (GitHub projects), PHP (Composer package)
Platforms
Wikimedia Foundation, GitHub, Fediverse
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Public PGP key published
  • No exposed sensitive data
  • No forms collecting sensitive data

Analytics and tracking

Services
PiratePX, GoatCounter
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
piratepx.com, goatcounter.com
Transparency
basic

Site quality

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

Key observations

  1. Website is a personal professional portfolio and blog for a software engineer.
  2. No forms present that collect user data.
  3. No cookie consent mechanism detected despite tracking pixels.
  4. Multiple verified social and professional profiles linked.
  5. No explicit privacy or security policies beyond basic disclaimers.
  6. WHOIS data unavailable due to domain naming rules error.
  7. Website uses HTTPS with good SSL configuration.
  8. No security headers detected in provided data.
  9. Website includes many external links to community and partner sites.
  10. Content is safe and suitable for general audiences.
Technical notes

Notes

The website is built using modern web technologies with a clean and structured HTML5 layout. It uses CSS for styling and includes FontAwesome icons for visual enhancement. JSON-LD structured data is implemented for semantic clarity and SEO benefits. The site references multiple external domains for resources and community links, indicating a well-connected ecosystem. Hosting is likely provided by Mythic Beasts, a reputable UK hosting provider. Performance is moderate with asynchronous loading of analytics scripts. Mobile optimization is good, but accessibility could be improved with better ARIA roles and keyboard navigation support. No CMS is detected, suggesting a static or custom-built site. Overall, the technical infrastructure is solid with room for modernization in accessibility and security headers.
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 theresnotime.co.uk. 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 theresnotime.co.uk.

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.