Skip to main content

Security report for timothygu.me

Tiancheng "Timothy" Gu · Technology · N/a

Medium risk. 11 critical or high findings in Email security, Security headers and 3 other checks.

Security score

50/100

Risk levelMedium

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

The website timothygu.me is a personal site and blog for Tiancheng "Timothy" Gu, focusing on technology topics and personal experiences. It serves as a portfolio and content hub with blog posts dating back to 2014-2015. The site is hosted on GitHub Pages using a Jekyll theme, leveraging modern web technologies such as Google Fonts and Font Awesome. Analytics are implemented via Google Analytics and Tag Manager, indicating moderate user tracking. The site is mobile optimized and well-structured, providing a good user experience with clear navigation and consistent branding. From a security perspective, the site uses HTTPS and does not expose sensitive data or vulnerable libraries. However, it lacks important security headers and formal privacy or cookie policies, which reduces its compliance posture. The domain is privacy protected but consistent with the personal nature of the site and its age aligns with the content timeline. No WAF or blocking mechanisms are detected, allowing full content access. Overall, the site demonstrates good technical implementation and business credibility for a personal website but falls short on privacy compliance and security best practices. Strategic improvements in policy disclosures and security headers would enhance trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

11 findings rated critical or high. Fix these first.

  1. 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.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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';…

  3. 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

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

Keep watching timothygu.me

This scan found 30 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
62
Security headers
15
Email security
40
DNS health
50
Network security
100
GDPR outside view
35
Average
50

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

This personal website targets a general audience interested in technology and personal insights from Timothy Gu. It operates as a personal branding and content sharing platform without commercial business operations or revenue streams evident. The site leverages open source and free hosting platforms, minimizing operational costs. Its competitive advantage lies in authentic personal content and active social media presence. Growth indicators include consistent blog posts and GitHub repository availability. The partnership ecosystem is limited to social media and open source communities. The business model is non-commercial, focusing on personal expression and portfolio presentation.

Security posture

The website exhibits a basic security maturity level appropriate for a personal site. HTTPS is enforced, and no sensitive data exposure is detected. However, the absence of security headers such as Content-Security-Policy and X-Frame-Options reduces protection against common web attacks. No formal security policies or incident response contacts are published, limiting transparency and preparedness. The use of privacy protection in WHOIS is justified for personal privacy. Overall, the security posture is moderate but could be improved by adopting standard web security headers and publishing privacy and security policies.

Recommendations

  1. Implement standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against web attacks.
  2. Publish a clear privacy policy and cookie policy to improve GDPR compliance and user trust.
  3. Add a security.txt file to provide vulnerability disclosure information and incident response contacts.
  4. Enable DNSSEC on the domain to improve DNS security.
  5. Regularly review and update analytics and tracking practices to align with privacy best practices.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Tiancheng "Timothy" Gu
Description
Personal website and blog serving as a hub for all things related to Timothy Gu, including personal experiences and technology explorations.
Key services
blog posts, personal portfolio, contact and social media links
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, Google Fonts, Font Awesome 4.2.0, Google Analytics, Google Tag Manager
Frameworks
Jekyll (implied by theme source and URL structure)
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced (implied by canonical URL and Google Analytics setup)
  • No forms with password or sensitive data
  • No exposed credentials or sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Personal website and blog for Timothy Gu
  2. No privacy or cookie policies found
  3. No terms of service found
  4. Contact available via contact page and social media
  5. No security.txt or vulnerability disclosure found
  6. Uses GitHub Pages hosting and Jekyll theme
  7. Uses Google Analytics and Tag Manager for tracking
  8. No WAF or blocking detected
  9. WHOIS privacy protection used but justified
Technical notes

Notes

The website is built using a static site generator (Jekyll) hosted on GitHub Pages, ensuring reliable and fast performance. It uses modern web fonts and icon libraries, with responsive design for mobile devices. The site includes Google Analytics and Tag Manager scripts for user tracking. No CMS or server-side technologies are detected. The technical implementation is clean with valid HTML and CSS, but lacks advanced accessibility features. There is no evidence of technical debt or outdated libraries. Opportunities exist to improve security headers and privacy compliance to reduce technical risks.
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. 50/100Medium39 findingsView report
Reviews of this site

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

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.