Thomas Ricci's website is a personal portfolio showcasing his skills as a software engineer and student at WPI. The site highlights his experience with various programming languages, frameworks, and cloud platforms, along with active projects such as Pyro and Nexus. The website is well-designed, mobile-optimized, and provides clear navigation to projects, resume, and professional social profiles. Technically, it leverages modern technologies including React, HTMX, and Cloudflare Pages hosting, ensuring fast performance and good accessibility. Security-wise, the site uses HTTPS and includes standard security headers, but lacks formal privacy, cookie, and security policies. Overall, the site is trustworthy and professional, though it could improve compliance by adding privacy and cookie policies.
Scanned ·
NIS2 and GDPR posture
GDPR outside view
35/ 100 · High
Checks completed
7of 7
NIS2 Art. 21(2)
a(a) Risk analysis and security policies: Not visible from outside
b(b) Incident handling: One indicator
c(c) Business continuity, backups and crisis management: Not visible from outside
d(d) Supply chain security: Not visible from outside
e(e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
f(f) Assessing the effectiveness of security measures: Not visible from outside
g(g) Cyber hygiene and security training: Not visible from outside
h(h) Cryptography and encryption: Partly checked
i(i) HR security, access control and asset management: One indicator
j(j) Multi-factor authentication and secured communications: Not visible from outside
Partly checked
One indicator
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.
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"
This scan found 22 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
60
DNS health
80
Network security
100
GDPR outside view
35
Average
63
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 thomasricci.dev, from OffSeq Breach.
No leaked records found
Breach holds no records for thomasricci.dev right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Business context
Business profile
The website positions Thomas Ricci as an individual software engineer with a focus on cloud and open-source projects. His business model is personal branding and project showcasing, targeting potential employers, collaborators, and the tech community. The presence of multiple active projects and leadership roles in robotics indicates growth and engagement in the technology sector. The site links to multiple related domains under his control, reinforcing his personal brand. There is no indication of a larger corporate structure or subsidiaries. The site’s open-source licensing and professional presentation enhance credibility and market positioning.
Security posture
The website demonstrates a good security posture with HTTPS enforced and standard security headers present. There are no forms collecting sensitive data, reducing attack surface. No vulnerabilities or exposed sensitive information were detected in the HTML content. However, the absence of explicit security policies, incident response contacts, and vulnerability disclosure mechanisms represents a compliance gap. Privacy compliance is weak due to missing privacy and cookie policies. The site would benefit from formalizing these policies and adding a security.txt file to improve transparency and incident handling readiness.
Recommendations
Add a comprehensive privacy policy and cookie consent mechanism to improve GDPR compliance.
Publish a security policy and incident response contact information to enhance trust and preparedness.
Implement a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
Regularly audit and update third-party libraries to mitigate potential vulnerabilities.
Consider appointing or designating a data protection officer contact if handling personal data in future.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
Company
Thomas Ricci
Description
I'm a college student and software engineer currently pursuing a Bachelor's degree in Computer Science at WPI. Experienced in Java, Kotlin, Typescript, React, HTMX, Cloudflare, Google Cloud. Currently building software at Pyro and working on Nexus cloud management system.
Key services
Software development, Cloud management system (Nexus), Technical leadership and advice, Open-source projects
Content quality
excellent
Branding
consistent
Technology
Stack
Java, Kotlin, Typescript, React, HTMX, Cloudflare, Google Cloud, Material Symbols Outlined font
Frameworks
React, HTMX, Hyperscript
Platforms
Cloudflare Pages
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good
Security
Observed score
90/100
Good practices seen
HTTPS enforced
No exposed sensitive data in HTML
No forms collecting sensitive data
Use of modern libraries
No inline scripts with suspicious content
Analytics and tracking
Services
Cloudflare Pages Analytics
Tracking level
minimal
Privacy practices
poor
Advertising
Tracking pixels
Cloudflare Pages Analytics
Transparency
basic
Site quality
Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high
Key observations
Personal portfolio website of a software engineer and student.
No privacy or cookie policies found, which is a compliance gap.
No forms collecting personal data, reducing privacy risk.
Use of modern web technologies and frameworks.
Good mobile responsiveness and accessibility.
No suspicious or malicious content detected.
Clear contact email provided.
Open-source projects and professional links enhance trust.
Technical notes
Notes
The website is built using modern web technologies including React, HTMX, and Hyperscript, hosted on Cloudflare Pages which provides fast and reliable delivery. The use of Material Symbols Outlined font enhances UI consistency. The site is mobile-optimized with responsive design and good accessibility features. SEO is supported by proper meta tags and Open Graph data. No CMS is detected, indicating a custom or static site approach. Performance is fast with minimal external dependencies. Technical risks are low, but the site could benefit from adding structured data (JSON-LD) for enhanced SEO and accessibility.
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.
Reviews of this site
Share your experience with thomasricci.dev. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review thomasricci.dev.