Skip to main content

Security report for ricostacruz.com

Rico Sta. Cruz · Technology · Australia

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

Security score

58/100

Risk levelMedium

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

Rico Sta. Cruz is an established web developer and open-source contributor with a personal website serving as a blog and portfolio. The site targets web developers and technology enthusiasts, showcasing expertise in JavaScript, Ruby, and UI design. The business model centers on personal branding and content creation, supported by active open-source projects and social media presence. Technically, the website uses modern frameworks such as Astro and Preact, is hosted with Cloudflare DNS, and employs Google Tag Manager for analytics. The site is performant, mobile-optimized, and accessible, reflecting a mature digital infrastructure. Security posture is generally good with HTTPS enforced and domain transfer protection, but lacks DNSSEC and security headers, which are recommended for enhanced protection. Privacy compliance is weak due to the absence of privacy and cookie policies. Overall, the website is trustworthy and professional but would benefit from improved compliance and security practices.

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

10 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 ricostacruz.com

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. 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
40
DNS health
70
Network security
100
GDPR outside view
35
Average
58

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 a personal brand of a technology professional with a strong foothold in the open-source community. The market positioning is that of an individual expert and influencer rather than a corporate entity. Revenue streams are likely indirect, through reputation and community engagement rather than direct sales. The target audience includes developers and tech enthusiasts seeking knowledge and tools. The site links to multiple social platforms and open-source projects, indicating a broad partnership ecosystem within the developer community. Growth indicators include active social media follower counts and ongoing contributions to popular projects. Strategic observations suggest maintaining and expanding open-source contributions and improving compliance to enhance professional credibility.

Security posture

The website demonstrates a moderate to good security maturity level. HTTPS is properly configured, and domain registration includes clientTransferProhibited status, reducing risk of unauthorized transfers. However, the lack of DNSSEC and security headers such as Content-Security-Policy and Strict-Transport-Security represents gaps that could be exploited. No sensitive data exposure or vulnerable libraries were detected. The absence of published security policies or incident response contacts limits transparency and preparedness. Compliance with GDPR and other privacy regulations is incomplete due to missing privacy and cookie policies. Overall, the security culture appears informal but adequate for a personal site, with room for improvement in formalizing policies and technical controls.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement and publish a comprehensive privacy policy and cookie policy to improve GDPR compliance.
  3. Add security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to harden the website against common attacks.
  4. Create and publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
  5. Consider adding contact information for security or incident response to improve transparency and readiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Rico Sta. Cruz
Description
Rico Sta. Cruz is a web developer focused on JavaScript, Ruby, and UI design. He is an open-source contributor and author of multiple developer tools and libraries. The website serves as a personal blog and portfolio.
Key services
Web development insights, Open-source projects, Technical blogging
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Ruby, Cloudflare DNS, Google Tag Manager, Partytown (for script offloading)
Frameworks
Astro (static site generator), Preact (UI components)
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • clientTransferProhibited domain status

Analytics and tracking

Services
Google Tag Manager, Cloudflare Insights
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Cloudflare Insights
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 blog and portfolio for a web developer and open-source contributor
  2. No privacy or cookie policies found, which is a compliance gap
  3. No contact phone numbers or physical addresses found, only email contact
  4. Modern web technologies and frameworks used with good performance and mobile optimization
  5. Security posture is good but can be improved with DNSSEC and security headers
  6. Active social media presence with follower counts displayed
  7. No forms detected on the site for data collection
  8. No evidence of security or incident response policies published
Technical notes

Notes

The website is built using modern web technologies including Astro for static site generation and Preact for UI components, ensuring fast load times and good performance. Hosting and DNS are managed via Cloudflare, providing CDN and DNS resilience. Google Tag Manager is used for analytics, with Partytown employed to offload third-party scripts for performance optimization. The site is mobile-optimized and accessible, with semantic HTML and responsive design. No CMS is detected, indicating a custom or static site approach. Technical risks are minimal but include the absence of DNSSEC and security headers, which are recommended to mitigate DNS and web-based attacks. Overall, the technical infrastructure is modern, performant, and well-maintained.
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 ricostacruz.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 ricostacruz.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.