Skip to main content

Security report for haucon.com

HauCon · Other · Norway

Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

55/100

Risk levelMedium

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

HauCon is an established company with a digital presence targeting Norway, Denmark, and Finland through dedicated country-specific websites. The company appears to operate in a sector related to construction or infrastructure, inferred from branding and domain usage. The website is built on Joomla CMS with modern frontend frameworks such as UIkit and Yootheme, providing a good user experience and mobile optimization. The technical infrastructure is moderate in performance with room for improvement in security headers and DNSSEC implementation. Security posture is adequate with HTTPS enabled and cookie consent mechanisms in place, but lacks explicit security policies and incident response contacts. Overall, the website is professional and trustworthy but could benefit from enhanced transparency and security practices.

Scanned

NIS2 and GDPR posture

GDPR outside view
80/ 100 · Low
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. 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

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

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching haucon.com

This scan found 25 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. See sample alerts.

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
72
Security headers
20
Email security
55
DNS health
60
Network security
40
GDPR outside view
80
Average
55

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

HauCon maintains a regional business model with dedicated portals for Norway, Denmark, and Finland, indicating a focus on localized service delivery. The domain age of over 20 years supports a mature market presence. The absence of visible contact details on the landing page suggests a possible reliance on country-specific sites for detailed customer engagement. The company does not publicly display certifications or security policies, which could be an area for competitive differentiation. The partnership ecosystem is limited to its own country domains, with no external partners or subsidiaries identified in the provided data.

Security posture

The website demonstrates a basic to moderate security maturity level with HTTPS enforced and a cookie consent banner aligned with GDPR requirements. However, the lack of DNSSEC, security headers, and explicit security or incident response policies indicates gaps in comprehensive security management. No vulnerabilities or exposed sensitive data were detected in the content. The absence of contact channels for security incidents reduces readiness for incident response. Overall, the security posture is functional but could be significantly improved to meet higher compliance and trust standards.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish explicit security policies and incident response contact information on the website.
  4. Add visible and verified company contact information including emails and phone numbers to improve trust and compliance.
  5. Consider integrating analytics with privacy-compliant configurations to better understand user behavior and improve services.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
HauCon
Description
HauCon is a company with country-specific websites for Norway, Denmark, and Finland, offering services presumably related to construction or infrastructure, as inferred from the brand and country-specific domains.
Content quality
good
Branding
consistent

Technology

Stack
Joomla, jQuery, UIkit, Yootheme
Frameworks
Joomla
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • Client transfer prohibited domain status
  • Cookie consent banner implemented

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website uses Joomla CMS with Yootheme and UIkit for frontend.
  2. Cookie consent banner present with GDPR compliance features.
  3. No visible contact emails or phone numbers on landing page.
  4. No terms of service or explicit security policy pages found.
  5. Multiple country-specific domains linked prominently.
  6. No social media links detected in the provided content.
  7. No analytics or tracking scripts explicitly detected.
  8. No forms detected on the landing page.
  9. No security headers visible in provided data.
  10. Domain DNSSEC not enabled, which is a security improvement opportunity.
Technical notes

Notes

The website uses Joomla CMS with Yootheme and UIkit frameworks, indicating a modern but standard technology stack. The site is mobile optimized and uses lazy loading for images, contributing to moderate performance. No broken elements or errors were detected in the HTML content. The absence of advanced analytics or tracking scripts suggests a minimal data collection approach. The domain registrar is reputable, and the domain age supports a stable digital presence. However, the lack of DNSSEC and security headers points to technical debt in security hardening. Overall, the technical implementation is solid but could benefit from security and analytics enhancements.
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 haucon.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 haucon.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.