Skip to main content

Security report for sydneyn.dev

Sydney Newmark · Technology · N/a

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

Security score

67/100

Risk levelMedium

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

Sydney Newmark's website is a personal portfolio and blog focused on computer science topics, projects, and personal interests. The site targets a general audience interested in technology and programming. It serves as a digital presence for Sydney as an individual rather than a commercial business entity. The website is built using modern technologies such as Astro and includes integrations with social media platforms like GitHub, Bluesky, and Mastodon. Hosting and analytics are provided via Cloudflare and Umami, indicating a lightweight and privacy-conscious approach. From a security perspective, the site enforces HTTPS and does not expose sensitive data or include forms that collect user input, reducing attack surface. However, it lacks explicit security headers and formal privacy or cookie policies, which are recommended for compliance and enhanced security posture. No incident response or vulnerability disclosure information is present, which is typical for personal sites but could be improved for transparency. Overall, the website demonstrates good technical implementation and content quality for a personal site, with moderate security and privacy compliance. The domain registration data aligns well with the website content and owner identity, supporting legitimacy. Strategic improvements include adding privacy and cookie policies, implementing security headers, and providing contact or security incident information 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

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 sydneyn.dev

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. 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
75
Security headers
30
Email security
70
DNS health
75
Network security
100
GDPR outside view
50
Average
67

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 rather than a corporate entity, focusing on personal branding and sharing knowledge in computer science. The business model is non-commercial, centered on content sharing and portfolio presentation. The target audience includes peers, potential collaborators, and tech enthusiasts. There is no indication of revenue streams or partnerships. The site’s market position is that of a personal academic and hobbyist presence. The use of modern static site generation and minimal external dependencies suggests a focus on performance and maintainability. The absence of formal business contact information or certifications aligns with the personal nature of the site.

Security posture

The security posture is adequate for a personal website with no user data collection or e-commerce functionality. HTTPS is enforced, and no sensitive data is exposed in the HTML. However, the lack of security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security reduces defense-in-depth. No privacy or cookie policies are present, which may be a compliance gap under GDPR if visitors are from the EU. No incident response or vulnerability disclosure mechanisms are provided, limiting transparency in case of security issues. The use of third-party analytics and hosting services is minimal and privacy-conscious. Overall, the site is low risk but could benefit from standard security best practices and compliance documentation.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy to improve GDPR compliance and user trust.
  2. Add standard security headers (Content-Security-Policy, X-Frame-Options, Strict-Transport-Security) to enhance security posture.
  3. Provide contact information or a dedicated security contact channel for incident response and vulnerability reporting.
  4. Consider adding a security.txt file or vulnerability disclosure statement to improve transparency.
  5. Regularly audit third-party scripts and dependencies for vulnerabilities and update them accordingly.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Sydney Newmark
Description
Personal website of Sydney Newmark, a rising sophomore majoring in computer science, sharing projects and experiences in tech and other interests.
Key services
blogging about projects and tech experiences, showcasing projects, sharing personal interests
Content quality
good
Branding
consistent

Technology

Stack
Astro v5.7.10, KaTeX 0.16.8, Cloudflare Insights, Umami Analytics
Frameworks
Astro
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • No forms present to collect user data

Analytics and tracking

Services
Umami Analytics, Cloudflare Insights
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Umami Analytics, Cloudflare Insights
Transparency
basic

Site quality

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

Key observations

  1. Personal website focused on computer science and personal projects
  2. No commercial or business contact information provided
  3. No privacy or cookie policies found
  4. No forms or data collection mechanisms present
  5. Uses modern static site generator (Astro) and minimal external dependencies
  6. Includes social media links to GitHub, Bluesky, and Mastodon
  7. No security headers detected in provided data
  8. HTTPS enforced with Cloudflare hosting
  9. No signs of malicious or suspicious content
Technical notes

Notes

The website is built using Astro v5.7.10, a modern static site generator, ensuring fast performance and good SEO. It uses KaTeX for math rendering and integrates Umami Analytics and Cloudflare Insights for lightweight tracking and performance monitoring. The site is hosted behind Cloudflare, providing SSL termination and CDN benefits. The HTML is well-structured with appropriate meta tags including Open Graph and Twitter cards for social sharing. The site is mobile optimized and accessible with semantic HTML and ARIA attributes. No CMS or dynamic backend detected, reducing attack surface and maintenance overhead. The technical stack is modern and well-suited for a personal portfolio site.
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 sydneyn.dev. 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 sydneyn.dev.

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.