Skip to main content

Security report for inuit.gl

inu:it A/S · Technology · Denmark

Medium risk. 5 critical or high findings in Security headers, SSL/TLS and 1 other check.

Security score

58/100

Risk levelMedium

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

The website inuit.gl is registered to inu:it A/S, a company established in 1998, likely operating in the technology sector. The site uses modern frontend technologies such as Bootstrap 5.1.3 and integrates Cookiebot for cookie consent management, indicating some level of privacy compliance effort. However, the website content is minimal, lacking explicit business descriptions, contact information, privacy policies, or terms of service pages. The domain registration data is consistent and transparent, supporting the legitimacy of the business. Technical infrastructure appears standard with hosting under inu:it A/S's own nameservers, but DNSSEC is not enabled, and security headers are not evident from the data provided.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 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

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

  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

Keep watching inuit.gl

This scan found 23 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
62
Security headers
15
Email security
80
DNS health
85
Network security
20
GDPR outside view
83
Average
58

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

inu:it A/S appears to be a small technology company with a long-standing domain registration dating back to 1998. The website's minimal content and lack of detailed business information limit insights into its market positioning or business model. The use of Cookiebot suggests awareness of privacy regulations. No social media presence or certifications were found, which could be areas for growth to enhance credibility and customer engagement. The hosting and domain registration are consistent, indicating a stable operational base.

Security posture

The website uses HTTPS, which is mandatory for secure communications. Cookie consent is managed via Cookiebot, supporting GDPR compliance. However, DNSSEC is not enabled, and no security headers were detected, which are important for mitigating common web vulnerabilities. The absence of a published security policy, incident response contacts, or vulnerability disclosure mechanisms indicates gaps in security transparency and readiness. Overall, the security posture is moderate but could be improved by implementing additional security best practices and transparency measures.

Recommendations

  1. Enable DNSSEC 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 comprehensive privacy policy and terms of service pages to improve compliance and user trust.
  4. Add clear contact information including emails and phone numbers to facilitate communication and support.
  5. Develop and publish a security policy and incident response contact details to improve security transparency and readiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
inu:it A/S
Description
No explicit business description found in content. The domain is registered to inu:it A/S, likely an IT or technology company.
Content quality
basic
Branding
moderate

Technology

Stack
Bootstrap 5.1.3, Cookiebot
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • Use of HTTPS (implied by URL https://inuit.gl)
  • Cookie consent mechanism via Cookiebot

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Cookiebot
Marketing tools
Cookiebot
Transparency
basic

Site quality

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

Key observations

  1. Website uses Bootstrap 5.1.3 for responsive design.
  2. Cookie consent is managed by Cookiebot with scripts loaded from consent.cookiebot.com.
  3. No privacy policy or terms of service pages found in the HTML content.
  4. No contact emails, phone numbers, or physical addresses found in the content.
  5. No security.txt or vulnerability disclosure information found.
  6. No social media links or business certifications detected.
  7. WHOIS data shows domain is registered to inu:it A/S since 1998 with no privacy protection.
  8. DNSSEC is not enabled, which is a security improvement opportunity.
  9. No explicit security headers detected in provided data.
  10. Website content is minimal and mostly technical with no visible business description or contact info.
Technical notes

Notes

The website leverages Bootstrap 5.1.3 for responsive design and includes Cookiebot scripts for cookie consent management. Hosting appears to be managed by inu:it A/S with dedicated nameservers. The site shows moderate performance and good mobile optimization. However, SEO and accessibility features are basic, and no CMS or advanced platforms were detected. The lack of DNSSEC and security headers represents technical risks. Overall, the technical infrastructure is stable but could benefit from modernization and enhanced security configurations.
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 inuit.gl. 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 inuit.gl.

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.