Skip to main content

Security report for consolis.com

Manufacturing · N/a

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

Security score

69/100

Risk levelMedium

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

The website consolis.com is currently inaccessible due to a CloudFront Web Application Firewall (WAF) blocking requests, resulting in a 403 error page. This prevents any meaningful extraction of website content, metadata, or business information. The domain itself is well-established, created in 2002, and registered through a reputable registrar with consistent DNS settings, indicating a legitimate business presence. However, the lack of accessible content severely limits the ability to assess the company's digital maturity, security posture, and compliance status. From a technical perspective, the site is hosted behind Amazon CloudFront, which provides robust content delivery and security capabilities. The blocking behavior suggests either a misconfiguration or a security policy that restricts access, which should be reviewed to avoid impacting legitimate users. No information about the technology stack, CMS, or analytics tools could be determined due to the blocked content. Security-wise, the absence of visible security headers, policies, or contact information on the accessible page is a concern. While the domain registration data is trustworthy, the inability to access the site content means that critical security and privacy compliance elements cannot be verified. This represents a risk for users and partners relying on the website for information or services. Overall, the site currently presents a high risk due to inaccessibility and lack of transparency. It is recommended to resolve the WAF blocking issues promptly, publish comprehensive privacy and security policies, and ensure proper security headers and HTTPS enforcement to improve trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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

7 findings rated critical or high. Fix these first.

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

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

    • 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

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

Keep watching consolis.com

This scan found 21 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
77
Security headers
15
Email security
85
DNS health
85
Network security
100
GDPR outside view
50
Average
69

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

Due to the blocked content, detailed business intelligence is unavailable. The domain age and registrar data suggest a mature business likely operating in manufacturing, energy, or transportation sectors. The domain's longevity indicates established operations, but no direct evidence of market positioning, revenue streams, or partnerships could be extracted. The lack of accessible content limits insights into competitive advantages or growth indicators.

Security posture

The current security posture cannot be fully assessed due to the CloudFront WAF blocking access. The domain uses HTTPS as implied by CloudFront usage, but no security headers or policies are visible. No incident response or vulnerability disclosure information is available. The blocking itself may indicate a proactive security measure but also risks denying legitimate access. The absence of privacy and cookie policies suggests compliance gaps with GDPR and other regulations.

Recommendations

  1. Review and adjust CloudFront WAF rules to prevent blocking legitimate traffic and improve user accessibility.
  2. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  3. Publish clear and comprehensive privacy, cookie, and security policies on the website.
  4. Implement and verify security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Ensure HTTPS is properly configured and enforced site-wide to protect data in transit.
Site observations

Automated reading of the public site. Ratings are indicative.

CloudFront detected. Request blocked by AWS CloudFront WAF with 403 ERROR - The request could not be satisfied. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to CloudFront WAF blocking requests.
  2. No metadata, structured data, or visible content available for analysis.
  3. No contact information, policies, or business details found on the page.
  4. Domain WHOIS data is consistent and indicates a legitimate, long-standing domain.
  5. Technical and security posture cannot be fully assessed due to blocked content.
Technical notes

Notes

The website is hosted on Amazon CloudFront, a reliable CDN and security platform. However, the current WAF configuration blocks all requests, resulting in a 403 error and no content delivery. No CMS or technology stack could be identified. The domain uses name servers from cygate.fi, indicating Finnish hosting infrastructure. The lack of accessible content prevents evaluation of performance, mobile optimization, SEO, or accessibility features. Technical debt or modernization opportunities cannot be assessed.
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 consolis.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 consolis.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.