Skip to main content

Security report for rubiko.it

Rubiko Srl · Technology · San Marino

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

Security score

41/100

Risk levelHigh

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

Rubiko Srl is a small technology company based in San Marino, specializing in custom digital solutions including web development, e-commerce platforms, digital marketing, and software management systems. The company targets businesses seeking digital transformation and offers tailored services to enhance online presence and operational efficiency. The website is professionally designed using Drupal 7 and integrates various JavaScript libraries and marketing tools such as Google Analytics and Facebook SDK. However, the technical infrastructure shows signs of aging, notably the use of PHP 5.6.40 and lack of a valid SSL certificate, which significantly impacts the security posture. Security headers are partially implemented, but critical HTTPS enforcement and modern TLS protocols are missing. Privacy and cookie policies are present and appear GDPR compliant, enhancing user trust. Overall, the website is functional and informative but requires urgent security upgrades to protect user data and improve trustworthiness.

Scanned

NIS2 and GDPR posture

GDPR outside view
18/ 100 · Critical
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

6 findings rated critical or high. Fix these first.

  1. GDPR outside view

    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 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

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

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

Keep watching rubiko.it

This scan found 20 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
50
Security headers
40
Email security
50
DNS health
70
Network security
20
GDPR outside view
18
Average
41

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

Rubiko operates in the niche market of digital solutions with a focus on bespoke web and software development services. Their business model is B2B, serving clients who need tailored digital transformation projects. The company has maintained consistent domain registration since 2018, aligning with its founding year. Their market position is that of a specialized provider with a moderate online presence. The company leverages partnerships with known DNS and hosting providers but does not publicly disclose partnerships or subsidiaries. Revenue streams likely come from project-based contracts and ongoing digital marketing services. The website content and structure support clear navigation and service promotion, targeting SMEs and enterprises in need of digital innovation. The presence of GDPR-compliant policies and cookie consent mechanisms indicates awareness of regulatory requirements.

Security posture

The current security posture of the website is weak due to the absence of a valid SSL certificate and the use of an outdated PHP version, which exposes the site to multiple vulnerabilities. While some security headers like X-Content-Type-Options and X-Frame-Options are set, the lack of HTTPS and modern TLS protocols severely undermines data confidentiality and integrity. No incident response or vulnerability disclosure policies are found, which limits the company's preparedness for security incidents. The absence of domain protection locks and CAA records further increases risk. The website does not implement advanced security features such as HSTS or OCSP stapling. Overall, the site requires immediate remediation to meet basic security standards and protect user data effectively.

Recommendations

  1. Obtain and configure a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Upgrade the PHP environment to a supported and secure version to mitigate known vulnerabilities.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  4. Enable OCSP stapling and session resumption to improve TLS performance and security.
  5. Configure DNSSEC validation and add CAA records to enhance domain security.
  6. Activate domain protection locks to prevent unauthorized domain transfers.
  7. Develop and publish a security policy and incident response plan accessible on the website.
  8. Regularly audit and update third-party libraries and CMS components to reduce vulnerabilities.
  9. Enhance accessibility features to improve compliance and user experience.
  10. Consider adding terms of service and vulnerability disclosure information to increase transparency.

Contact details published on the site

Addresses
Legal name
Rubiko Srl
Registration number
COE SM 27567
Technical notes

Notes

The website is built on Drupal 7 with PHP 5.6.40, which is outdated and no longer supported, posing security risks. The hosting environment uses Apache and PleskLin, with DNS servers from Technorail and Aruba DNS. The site uses several JavaScript libraries including jQuery 1.10.2, Owl Carousel, and Colorbox for UI components. Google Fonts and FontAwesome provide typography and icons. Google Analytics and Facebook SDK are integrated for analytics and social media engagement. Performance metrics are not available, but the presence of many CSS and JS imports suggests potential for optimization. Mobile optimization is good, with responsive design and mobile-specific sliders. SEO is supported by meta tags and Open Graph data. Accessibility is basic, with skip links and some ARIA landmarks. The lack of HTTPS and modern TLS protocols is a critical technical debt that must be addressed to ensure secure communications.
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 rubiko.it. 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 rubiko.it.

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.