Skip to main content

Security report for paddy.li

Technology · Germany

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

Security score

61/100

Risk levelMedium

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

This website represents a personal portfolio and contact hub for Patrick, known as Paddyk45, a young developer from Hamburg, Germany. The site serves primarily as a showcase of his interests, projects, and social presence, targeting fellow developers and tech enthusiasts. It includes links to various social platforms and partner sites, emphasizing community and open-source engagement. The business model is personal branding and networking rather than commercial enterprise. Technically, the site is built with modern HTML and CSS, using the new.css framework and custom fonts. It includes minimal JavaScript, notably a script from rybbit.io for analytics. The site is lightweight, fast, and mobile-optimized with good accessibility. Hosting is sponsored by Brutecat, indicating a reliable infrastructure. SEO is basic but sufficient for a personal site. From a security perspective, the site lacks formal security policies, cookie consent, and privacy statements, which are common for personal sites but represent compliance gaps. The presence of a PGP key is a positive trust indicator for secure communication. No forms collect sensitive data, reducing attack surface. However, security headers are missing, and HTTPS status is unknown, suggesting room for improvement. Overall, the site is low risk, safe for general audiences, and professionally presented for its scope. Strategic recommendations include adding privacy and cookie policies, implementing security headers, and publishing a vulnerability disclosure or security policy 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

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

  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

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

Keep watching paddy.li

This scan found 24 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
52
Security headers
15
Email security
73
DNS health
75
Network security
100
GDPR outside view
50
Average
61

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention paddy.li, from OffSeq Breach.

No leaked records found

Breach holds no records for paddy.li right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

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 functions as a personal portfolio and social hub for a young developer, focusing on community engagement and open-source contributions. It leverages partnerships with other developers and sponsors for hosting and domain support. The business model is non-commercial, centered on personal branding and networking. The target audience includes developers, tech hobbyists, and personal contacts. Growth indicators include active social links and acknowledgments of sponsors. The partnership ecosystem is small but meaningful, involving domain and hosting sponsors. The site does not monetize directly and serves as a platform for showcasing skills and projects.

Security posture

The security posture is basic but adequate for a personal website. No sensitive data collection or complex user interactions reduce risk. The publication of a PGP key is a strong positive for secure communications. However, the absence of security headers and formal policies indicates a lack of mature security practices. No incident response or vulnerability disclosure information is provided, which could hinder timely handling of security issues. GDPR compliance is not addressed, and no cookie consent mechanism is present. Overall, the site is low risk but could benefit from adopting standard security best practices and compliance measures.

Recommendations

  1. Implement HTTPS with a valid SSL certificate if not already done to ensure encrypted communications.
  2. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to improve security posture.
  3. Publish a privacy policy and cookie policy to enhance GDPR compliance and user trust.
  4. Create a vulnerability disclosure or security policy page to facilitate responsible reporting of security issues.
  5. Consider adding a cookie consent mechanism if any tracking or cookies are used to comply with privacy regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal website of Patrick (Paddyk45), a 16-year-old developer from Hamburg, Germany, showcasing personal projects, links to services, and social profiles.
Key services
Software development, Rust programming learning, Hosting personal projects and services
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, Atkinson Hyperlegible font, Rust (learning mentioned)
Frameworks
new.css
Performance
fast
Mobile
good
Accessibility
good
SEO
basic

Security

Observed score
75/100
Good practices seen
  • PGP key published for secure communication
  • No forms collecting sensitive data
  • No exposed credentials or sensitive data

Analytics and tracking

Services
rybbit.io
Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Personal developer website with clear contact methods and social links.
  2. No privacy, cookie, or terms of service policies found.
  3. No forms collecting personal data; minimal tracking via rybbit.io.
  4. Good design and navigation with consistent branding.
  5. No security policies or incident response information published.
  6. No suspicious or malicious content detected.
  7. Website hosted on a server sponsored by Brutecat.
  8. PGP key provided for secure communication.
Technical notes

Notes

The website uses a simple, modern tech stack with HTML5, CSS3, and minimal JavaScript. The new.css framework provides a clean and responsive design. The use of a custom font enhances branding. External scripts are limited to a single analytics provider (rybbit.io), minimizing performance impact. Hosting is sponsored by Brutecat, suggesting reliable infrastructure. The site loads quickly and is mobile optimized with good accessibility features. SEO is basic, with no advanced metadata or structured data detected. There is no CMS detected, indicating a static or hand-coded site. Technical debt appears low, but security enhancements are recommended.
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 paddy.li. 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 paddy.li.

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.