Skip to main content

Security report for oqaasileriffik.gl

Oqaasileriffik · Government · Greenland

High risk. 7 critical or high findings in Security headers and GDPR outside view.

Security score

43/100

Risk levelHigh

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

Oqaasileriffik is the official Greenlandic Language Secretariat, providing authoritative language resources, terminology, and policy information primarily for the Greenlandic language. The website serves as a central hub for language tools, dictionaries, news, and educational materials targeting Greenlandic speakers, researchers, and government stakeholders. The organization operates as a governmental or non-profit entity focused on language preservation and development. Technically, the website is built on WordPress with Elementor and several plugins, including multilingual support via WPML. The infrastructure uses Apache on Ubuntu, but suffers from critical SSL issues with an invalid certificate and no modern TLS protocols enabled, which undermines secure communications. Performance data is limited, but the site appears content-rich and mobile-optimized with basic accessibility features. Security posture is weak due to the invalid SSL certificate, lack of HSTS, missing security headers, and absence of vulnerability disclosure or security policies. Privacy compliance is minimal, with no visible privacy or cookie policies. Contact information is clearly provided, including email, phone, and physical address, along with active social media channels. Overall, the site is functional and content-rich but requires urgent improvements in SSL configuration, security best practices, and privacy compliance to enhance trust and protect users. Strategic recommendations include obtaining a valid SSL certificate, enabling modern TLS, publishing privacy and cookie policies, and implementing security headers and vulnerability disclosure mechanisms.

Scanned

NIS2 and GDPR posture

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

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 oqaasileriffik.gl

This scan found 18 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
15
Email security
75
DNS health
50
Network security
40
GDPR outside view
25
Average
43

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

Oqaasileriffik holds a unique market position as Greenland's official language secretariat, serving a niche but critical role in language preservation and policy. Its competitive advantage lies in government backing and authoritative content. The business model is non-commercial, focusing on public service and cultural preservation. Revenue streams are likely government-funded. The target customers include Greenlandic citizens, educators, linguists, and government agencies. The organization maintains partnerships with related language and mapping services, enhancing its ecosystem. Growth indicators include regular publication of news and updates. The website's multilingual support and social media presence indicate efforts to broaden reach and engagement.

Security posture

The current security maturity level is low due to the invalid SSL certificate and lack of modern TLS support, exposing users to potential interception risks. No advanced security headers or policies are implemented, and no incident response or vulnerability disclosure information is available. GDPR compliance is not evident, and cookie consent mechanisms are absent. The site does not expose sensitive data but lacks proactive security measures. Incident response readiness appears minimal, with no dedicated security contacts. The security culture seems underdeveloped, requiring significant enhancements to meet modern standards.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate from a trusted Certificate Authority to secure HTTPS connections.
  2. Enable TLS 1.2 or TLS 1.3 protocols and disable deprecated SSL/TLS versions to improve encryption strength.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements and implement a cookie consent mechanism.
  5. Add security headers such as Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
  6. Create and publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  7. Establish incident response contact channels (e.g., security@ or abuse@ email addresses).
  8. Improve DNS configuration by adding DNSSEC and CAA records to enhance domain security.
  9. Regularly audit and update plugins and libraries to avoid vulnerabilities.
  10. Enhance accessibility features and SEO optimization for better user experience and discoverability.

Contact details published on the site

Addresses
Technical notes

Notes

The website runs on a standard WordPress CMS with Elementor page builder and several plugins for multilingual support, quizzes, and enhanced navigation. The server uses Apache on Ubuntu. The tech stack is modern but lacks proper SSL/TLS configuration, which is a critical technical debt. Performance metrics are missing, but the page size and resource count suggest moderate load. The site is mobile-optimized and uses Google Fonts locally. Analytics are implemented via Google Analytics and Matomo, indicating a mature approach to user tracking. Technical risks include invalid SSL, missing DNS records, and lack of security headers, which could impact user trust and SEO rankings. Modernization opportunities include upgrading SSL, improving DNS security, and enhancing privacy compliance.
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 oqaasileriffik.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 oqaasileriffik.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.