Skip to main content

Security report for okaythis.com

Okay · Finance · Norway

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

Security score

68/100

Risk levelMedium

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

Okay is a Norway-based company founded in 2018 that provides advanced, modular authentication solutions tailored for fintechs, banks, and enterprises. Their platform focuses on balancing security, compliance, and user experience by offering identity verification, strong customer authentication, passwordless access, and compliance management services. The company positions itself as a trusted partner in the financial technology sector, emphasizing rapid deployment and regulatory adherence such as PSD2 and GDPR. Technically, the website is built using modern frameworks like Next.js and React, hosted on Vercel, and integrates analytics and consent management tools to ensure performance and privacy compliance. Security posture is strong with HTTPS enforcement and clientTransferProhibited domain status, though DNSSEC is not enabled and explicit security policies are not published. Overall, the website is professional, well-structured, and trustworthy, with comprehensive content and clear business focus.

Scanned

NIS2 and GDPR posture

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

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 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 Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  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 okaythis.com

This scan found 24 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
72
Security headers
30
Email security
75
DNS health
60
Network security
100
GDPR outside view
70
Average
68

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

Okay operates in the finance and technology sectors, targeting fintech companies, banks, and enterprises requiring secure authentication and compliance solutions. Their business model is B2B SaaS, offering SDKs and APIs for identity and access management, KYC onboarding, and fraud prevention. The company demonstrates competitive advantages through modular, rapid deployment solutions and regulatory expertise. Their partnership ecosystem includes integrations with Firebase for push notifications and use of Crystallize CMS. Growth indicators include detailed product offerings and developer resources. The company maintains a medium size with a clear market position as a security and compliance enabler in the financial industry.

Security posture

The security maturity level of Okay is good, with HTTPS enforced and domain transfer protections in place. The absence of DNSSEC is a minor gap. No exposed sensitive data or vulnerable libraries were detected in the website content. Security best practices include modular SDKs with server-side integration and use of push notifications for multi-factor authentication. However, the website lacks a published security policy, incident response contacts, and vulnerability disclosure mechanisms, which are recommended for enhanced transparency and readiness. Compliance with GDPR is indicated through privacy policies and cookie consent mechanisms. Overall, the security posture is strong but could be improved with formalized policies and disclosures.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Publish a dedicated security policy page outlining security frameworks and incident response procedures.
  3. Establish and publicize a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Implement and verify comprehensive security headers such as Content-Security-Policy and X-Frame-Options.
  5. Consider adding direct phone contact information for sales or support to improve business credibility.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Okay
Description
Okay delivers end-to-end authentication solutions that balance security, compliance, and user experience. Protect digital assets, prevent fraud, and simplify authentication with strong, future-proof security.
Key services
Identity verification, Authentication, Compliance management, Strong customer authentication (PSD2/PSD3), Passwordless authentication, Access control server (ACS), Identity and access management (IAM), KYC onboarding
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, Vercel Analytics, Vercel Speed Insights, Hotjar, Google Tag Manager, CookieFirst Consent Management, Firebase (for push notifications)
Frameworks
Next.js
Platforms
Web, iOS SDK, Android SDK, React Native
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • No DNSSEC enabled (recommend enabling)
  • Use of push notifications for 2FA
  • Modular SDKs with server-side integration

Analytics and tracking

Services
Vercel Analytics, Google Tag Manager, Hotjar
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Hotjar
Marketing tools
Hotjar, CookieFirst Consent Management
Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with rich content and no blocking mechanisms
  2. Strong focus on secure authentication solutions for fintech and enterprise clients
  3. Comprehensive product and service offerings with detailed documentation
  4. Use of modern web technologies and analytics tools
  5. Good privacy and cookie policy presence with consent management
  6. No direct phone numbers found, only email and physical address
  7. No explicit security policy or incident response contact published
  8. No vulnerability disclosure or security.txt found
  9. WHOIS data consistent and domain well maintained
Technical notes

Notes

The website leverages a modern technology stack including React and Next.js, hosted on Vercel, ensuring fast performance and scalability. Integration with analytics tools like Vercel Analytics, Google Tag Manager, and Hotjar supports data-driven insights and user experience optimization. The use of Crystallize CMS enables flexible content management. Mobile optimization is excellent, and SEO best practices are followed with proper meta tags and Open Graph data. The site uses Firebase for push notifications in its SDKs, indicating a mature approach to multi-factor authentication. Technical risks are minimal, with no visible outdated or vulnerable libraries. Opportunities exist to enhance security headers and formalize security documentation.
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 okaythis.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 okaythis.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.