Skip to main content

Security report for josepmartins.com

Josep Martins · Technology · Spain

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

Security score

62/100

Risk levelMedium

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

Josep Martins is an individual product designer and frontend developer based in Girona, Spain, with professional experience at notable technology companies such as GitHub, New Relic, Typeform, and currently Stripe. The website serves as a personal portfolio showcasing his design and development work, including side projects like open-source libraries and free texture archives. The site is well-structured, visually consistent, and targets a general audience interested in design and frontend development. Technically, the website is built using React and modern frontend tooling, including Webpack and Typekit fonts. It demonstrates good mobile optimization and basic accessibility features. However, there is no evidence of a CMS or hosting provider information. Performance is moderate, with no detected analytics or tracking scripts, indicating a privacy-conscious approach. From a security perspective, the site lacks visible security headers and explicit security policies. HTTPS status and SSL configuration could not be confirmed from the provided data. No privacy or cookie policies are present, and no incident response or vulnerability disclosure information is available. The WHOIS lookup failed to return domain registration data, which raises concerns about domain legitimacy and transparency. Overall, the website is a professional personal portfolio with good content quality and technical implementation but has gaps in security posture and privacy compliance. The absence of WHOIS data and lack of security policies reduce trustworthiness and compliance standing.

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

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 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 josepmartins.com

This scan found 23 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
72
Security headers
30
Email security
65
DNS health
70
Network security
100
GDPR outside view
35
Average
62

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

Josep Martins operates as an individual professional in the technology sector, focusing on product design and frontend development. His portfolio highlights experience with leading tech companies, positioning him as a skilled designer with a strong personal brand. The business model is primarily personal branding and showcasing expertise, supplemented by open-source side projects that may contribute to reputation and community engagement. The target audience includes potential employers, collaborators, and the design/development community. There is no indication of revenue streams or partnerships beyond professional affiliations. The website's clean design and external links to reputable companies enhance credibility, though the lack of formal business information and WHOIS transparency limits full business intelligence insights.

Security posture

The website demonstrates a basic security posture with no detected HTTPS enforcement or security headers in the provided data. There are no visible forms collecting sensitive data, reducing immediate risk exposure. However, the absence of privacy and cookie policies indicates non-compliance with GDPR and other privacy regulations. No incident response contacts or vulnerability disclosure mechanisms are present, which could hinder timely security issue resolution. The WHOIS data absence is a notable concern, as domain registration transparency is a key trust factor. Overall, the security maturity is low to moderate, with recommendations to implement standard security headers, privacy policies, and domain registration transparency to improve trust and compliance.

Recommendations

  1. Implement HTTPS with a valid SSL certificate and enforce secure connections site-wide.
  2. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish comprehensive privacy and cookie policies to comply with GDPR and inform users.
  4. Provide clear contact information for security incidents, including a security.txt file or dedicated email.
  5. Investigate and resolve WHOIS data availability to improve domain registration transparency and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Josep Martins
Description
I'm Josep Martins, a product designer and frontend developer based in Girona. Systems designer at GitHub. Previously at design engineer at New Relic and Typeform.
Key services
Product design, Frontend development, Design systems, Open source side projects
Content quality
good
Branding
consistent

Technology

Stack
React, Webpack, Typekit fonts
Frameworks
React
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
50/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a personal portfolio for a product designer and developer.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact phone numbers or physical addresses provided.
  4. Only one contact email found: jsp.mrtns@gmail.com (personal email, not company domain).
  5. No security headers or explicit security policies detected.
  6. No analytics or tracking scripts detected.
  7. Website uses React and modern frontend tooling.
  8. No signs of advertising or affiliate marketing.
  9. Social media presence is linked and active.
  10. No WHOIS data available, which is unusual.
Technical notes

Notes

The website is built using React with Webpack bundling and uses Typekit for fonts, indicating a modern frontend technology stack. The site loads multiple JavaScript chunks and uses lazy loading for images, which supports performance optimization. There is no CMS detected, suggesting a custom or static site approach. The site is mobile optimized with responsive design elements. However, no analytics or tracking scripts were found, which may be intentional for privacy reasons. The absence of security headers and unknown SSL status are technical risks. The site could benefit from improved accessibility features and SEO optimizations such as meta tags and structured data.
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 josepmartins.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 josepmartins.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.