Skip to main content

Security report for wattsight.com

Volue · Technology · N/a

Partial score · DNS & email only

51/100

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

The website serves as a sign-in and registration portal for Volue Identity, a service likely related to user authentication and access management within the Volue ecosystem. The site supports authentication via Microsoft, Google, and an email-based B2C scheme, indicating integration with OAuth2/OpenID Connect protocols. The content is minimal and focused solely on login functionality without broader business or policy information. Technically, the site uses Bootstrap 4 and jQuery for UI and interaction, with responsive design elements for mobile users. Security practices include the use of modern authentication flows, but no explicit security headers or privacy policies are present in the HTML content. No contact or incident response information is provided, limiting transparency and user trust. Overall, the site is functional but lacks comprehensive compliance and security disclosures.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
Checks completed
6of 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

5 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

Keep watching wattsight.com

This scan found 16 issues across 5 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
0
Email security
50
DNS health
80
Network security
100
GDPR outside view
25
Average
51

Not counted

  • Security headers: did not complete in this scan.
  • 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

Volue appears to operate in the technology sector, providing identity and access management services as part of its broader offerings. The business model includes supporting user authentication through multiple providers, targeting users who require secure access to Volue's services. The site does not provide detailed business information, limiting insights into market positioning or company size. The use of branded logos and consistent styling suggests a professional approach to branding. Absence of privacy and cookie policies may indicate an area for improvement in regulatory compliance. No partnerships or subsidiaries are evident from the content provided.

Security posture

The security posture is moderate, leveraging OAuth2/OpenID Connect for authentication, which is a strong security practice. However, the lack of visible security headers such as Content-Security-Policy, X-Frame-Options, and others reduces the overall security robustness. No vulnerabilities or exposed sensitive data were detected in the HTML content. The absence of privacy and cookie policies, as well as incident response contacts, indicates gaps in compliance and security transparency. The site uses HTTPS for redirects, but explicit SSL configuration details are not available. Overall, the site would benefit from enhanced security headers, clear privacy disclosures, and incident response mechanisms.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy with consent mechanisms.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to improve security posture.
  3. Provide clear contact information including security incident response contacts.
  4. Ensure all external links use HTTPS and validate third-party content for security.
  5. Consider adding analytics with privacy-compliant configurations to monitor user interactions and improve user experience.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Volue
Description
Volue Identity sign-in page for user authentication and registration services.
Key services
User sign-in, User registration, Authentication via Microsoft, Email (B2C), and Google
Content quality
basic
Branding
consistent

Technology

Stack
Bootstrap 4, jQuery, SVG
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • Use of OAuth2/OpenID Connect for authentication
  • Use of HTTPS implied by redirect URIs (https://volueinsight.com)

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
basic
Navigation
basic
Professionalism
basic
Trustworthiness
moderate

Key observations

  1. Website is a sign-in portal for Volue Identity service.
  2. No privacy, cookie, or terms of service policies found on the page.
  3. No contact information or security incident contacts provided.
  4. Uses OAuth2/OpenID Connect flows for authentication with Microsoft, Google, and Email providers.
  5. No analytics or advertising scripts detected.
  6. Basic design with Bootstrap and jQuery, mobile responsive.
  7. No visible security headers or advanced security features in HTML content.
  8. No WHOIS data provided to verify domain legitimacy or age.
Technical notes

Notes

The website uses a modern front-end stack with Bootstrap 4 and jQuery, providing responsive design and basic accessibility. The authentication flows integrate OAuth2/OpenID Connect protocols with Microsoft, Google, and email providers, indicating a secure and standardized approach to user authentication. Performance is likely moderate given the use of minified CSS and JS libraries, though no explicit performance metrics are available. The site lacks advanced SEO meta tags and structured data, limiting search engine optimization. No CMS or hosting provider information is discernible from the HTML content. Technical debt appears low but opportunities exist to modernize security headers and improve compliance disclosures.
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 wattsight.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 wattsight.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.