Security report for rubans.lv
Jānis Rubans · Technology · Latvia
High risk. 12 critical or high findings in GDPR compliance, Security headers and 1 other check.
46/100
Risk levelHigh
The website rubans.lv serves as a personal portfolio for Jānis Rubans, a frontend developer based in Latvia. It primarily showcases the individual's professional identity and provides contact information for potential clients or employers. The site is minimalistic, focusing on essential information such as name, role, phone number, email, and LinkedIn profile, without additional business or corporate details. The target audience appears to be technology professionals or recruiters seeking frontend development expertise. From a technical perspective, the website uses standard web technologies including HTML5, CSS3, and JavaScript. The site is relatively simple with no detected CMS or advanced frameworks. Performance and mobile optimization are basic but adequate for the site's scope. SEO and accessibility features are minimal but present through meta tags and responsive viewport settings. Security posture is limited; no HTTPS confirmation was provided, and no security headers or policies are detected. The absence of privacy, cookie, or terms of service policies indicates low privacy compliance. No analytics or tracking scripts are present, which reduces privacy concerns but also limits marketing insights. The site does not appear to be behind any WAF or security challenge, and content is fully accessible. Overall, the website is a straightforward personal portfolio with moderate professionalism but lacks comprehensive security and privacy features. Strategic improvements in security headers, HTTPS enforcement, and privacy compliance would enhance trustworthiness and compliance.
Scanned
NIS2 and GDPR posture
- NIS2 posture
- 2/ 100 · Critical
- GDPR posture
- 10/ 100 · Critical
- Checks completed
- 7of 7
Indicative only: based on publicly visible signals, not a certification or legal assessment. NIS2 signals relate to Article 21 of Directive (EU) 2022/2555; GDPR signals to Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive.
Priority findings
12 findings rated critical or high. Fix these first.
GDPR compliance
These are the privacy signals visitors and data protection authorities look for under GDPR.
- Critical
EU business without adequate privacy measures
EU businesses are subject to strict GDPR requirements
What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures
- 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
- GDPR Art. 12
- GDPR Art. 13
- NIST PT-5: NIST SP 800-53 Rev. 5 PT-5: Privacy Notice
- 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
- GDPR Art. 7
- ePrivacy Art. 5(3)
- NIST PT-4: NIST SP 800-53 Rev. 5 PT-4: Consent
- High
Third-party services without privacy policy
Detected services: LinkedIn
What to do: Document all third-party data sharing in your privacy policy
- Critical
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"
- CWE-1021
- OWASP A06:2025
- CAPEC-103
- ASVS V3.4.6
- OWASP Secure Headers: OWASP Secure Headers Project recommends X-Frame-Options: deny
- RFC 7034
- 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';…
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching rubans.lv
This scan found 34 issues across 7 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
- Risk score drift
Email alerts on material changes and an exportable JSON history of every change.
Billed monthly. 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. Payments by EveryPay; sold by SEQ SIA, Latvia.
Results by check
Each check with its score, findings and the evidence it collected.
Technical appendix
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Business context
Business profile
Security posture
Recommendations
- Implement HTTPS with a valid SSL/TLS certificate to secure all communications.
- Add standard security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
- Publish a privacy policy and cookie policy to improve GDPR compliance and user trust.
- Include a vulnerability disclosure policy or security contact email to enhance incident response readiness.
- Consider adding basic analytics with privacy-respecting configurations to understand visitor behavior and improve the site.
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- Jānis Rubans
- Description
- Frontend developer
- Key services
- frontend development
- Content quality
- good
- Branding
- consistent
Technology
- Stack
- HTML5, CSS3, JavaScript
- Performance
- moderate
- Mobile
- basic
- Accessibility
- basic
- SEO
- basic
Security
- Observed score
- 30/100
Analytics and tracking
- Tracking level
- minimal
- Privacy compliance
- poor
Advertising
- Transparency
- poor
Site quality
- Design
- good
- User experience
- good
- Content relevance
- good
- Navigation
- good
- Professionalism
- good
- Trustworthiness
- moderate
Key observations
- Website is a simple personal portfolio for a frontend developer.
- No privacy, cookie, or terms of service policies found.
- Contact information is clearly provided including phone, email, and LinkedIn.
- No forms or data collection mechanisms present.
- No security headers or advanced security features detected.
- No analytics or tracking scripts detected.
- No advertising or affiliate marketing detected.
- Content is safe and appropriate for general audiences.
- No evidence of WAF or blocking mechanisms.
- WHOIS data missing, limiting domain legitimacy assessment.
Technical notes
Notes
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.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR and IETF Datatracker (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
Retrieved 2026-10-24
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with rubans.lv. Every review is verified by email and published after moderation.
Community rating
Loading reviews…