Skip to main content

Security report for arqana.com

Arqana · Other

Partial score · DNS & email only

75/100

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

The website demonstrates a solid foundation in network security, SSL/TLS configuration, and email security, scoring 100/100 in these critical areas. However, significant gaps exist in the implementation of security headers, with a notably low score of 20/100, exposing the site to risks such as clickjacking, content injection, and cross-site scripting attacks. Missing key headers like Strict-Transport-Security and Content-Security-Policy increase vulnerability to man-in-the-middle attacks and code injection. Additionally, the failure to meet GDPR and NIS2 compliance requirements introduces legal and regulatory risks that could impact business operations and reputation. DNS security is moderately strong but can be improved by enabling DNSSEC and configuring CAA records to prevent certificate mis-issuance. Overall, while core protections are in place, addressing these header and compliance issues is critical to safeguard customer data, maintain trust, and avoid regulatory penalties.

Scanned

NIS2 and GDPR posture

NIS2 outside view
Not assessed
GDPR outside view
Not assessed

Both readouts depend on the site's pages, which could not be loaded in this scan.

Priority findings

3 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';…

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

Keep watching arqana.com

This scan found 10 issues across 3 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
100
Security headers
20
Email security
100
DNS health
85
Network security
100
Average
81
After the cap
75

Not counted

  • GDPR outside view: 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.

Technical notes

Notes

Critical security headers are missing, notably Strict-Transport-Security, X-Frame-Options, and Content-Security-Policy, resulting in exposure to man-in-the-middle attacks, clickjacking, and cross-site scripting threats. The absence of X-Content-Type-Options and X-XSS-Protection headers further weakens content handling and client-side protection. GDPR and NIS2 compliance failures indicate potential gaps in data protection and operational security controls, risking regulatory violations. DNSSEC is not enabled, and CAA records are not configured, which could allow DNS spoofing and unauthorized certificate issuance respectively. Despite these issues, SSL/TLS and email security measures are properly implemented, providing a strong baseline for secure communications.
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 arqana.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 arqana.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.