Skip to main content

Security report for fortyseven.io

Fortyseven.io · Financial services · United kingdom

Medium risk. 7 critical or high findings in Email security, Security headers and 2 other checks.

Security score

61/100

Risk levelMedium

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

Scanned

NIS2 and GDPR posture

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

7 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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';…

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

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

Keep watching fortyseven.io

This scan found 26 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
65
Security headers
15
Email security
60
DNS health
70
Network security
100
GDPR outside view
53
Average
61

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

Forty Seven operates in the competitive fintech and cryptocurrency banking sector, aiming to disrupt traditional banking by lowering entry barriers for fintech developers and integrating crypto and fiat services. Their revenue streams likely include token sales, platform fees, and loyalty programs tied to the FSBT token. The company has cultivated a broad partnership ecosystem including payment processors, software developers, and cloud providers, enhancing its market reach and technical capabilities. The ICO and token sale have attracted significant attention, supported by positive expert reviews and press coverage. Growth indicators include a detailed roadmap with licensing milestones and active community engagement. Strategic observations suggest the company is well-positioned to capitalize on the growing demand for hybrid financial services but must address regulatory and security challenges to sustain growth.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enabled and secure form handling. However, the absence of key HTTP security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options weakens its defense against common web attacks. The lack of a cookie consent mechanism and no publicly available incident response or security policy documents indicate gaps in compliance with GDPR and best practices. No vulnerabilities or exposed sensitive data were detected in the HTML content, but the WHOIS data protection reduces transparency. The use of multiple tracking pixels increases privacy risks if not properly managed. Overall, the security posture is functional but requires enhancements in headers, privacy compliance, and incident response readiness to meet industry standards.

Recommendations

  1. Implement comprehensive HTTP security headers including CSP, HSTS, X-Frame-Options, and X-XSS-Protection to mitigate common web vulnerabilities.
  2. Add a clear cookie consent banner and detailed cookie policy to comply with GDPR and enhance user privacy transparency.
  3. Publish a formal security policy and incident response plan on the website to improve trust and readiness for security events.
  4. Enhance WHOIS transparency if possible or provide clear justification for privacy protection to reduce risk perception.
  5. Conduct regular security audits and penetration testing to identify and remediate potential vulnerabilities proactively.

Contact details published on the site

Addresses
Legal name
FortySeven OÜ
Registration number
14347500
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Forty Seven
Description
Forty Seven Bank is innovative fin-tech startup aimed at uniting communities of cryptocurrency users and followers of the traditional monetary system. They build a bridge between digital assets and fiat money.
Key services
Multi-Asset Account with tied card, White label fintech applications, API access for developers, Smart contracts for businesses, Token Generation Event (ICO) and FSBT token trading
Content quality
good
Branding
moderate

Technology

Stack
HTML5, CSS3, JavaScript, jQuery 3.3.1, WebFont Loader, Facebook Pixel, Hotjar, Twitter Universal Website Tag, Google Fonts (Roboto), YouTube embedded videos, Google reCAPTCHA (commented out Drift chat)
Platforms
Ethereum (FSBT token on Ethereum platform)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
65/100
Good practices seen
  • Use of HTTPS assumed (canonical link uses https)
  • No exposed sensitive data in HTML
  • Secure forms with required email input

Analytics and tracking

Services
Hotjar, Facebook Pixel, Twitter Pixel
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Facebook Pixel, Twitter Universal Website Tag, Hotjar
Marketing tools
Facebook Pixel, Twitter Pixel, Hotjar
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content and multiple sections
  2. No WAF or blocking detected
  3. WHOIS data is unavailable or protected
  4. Privacy and terms documents are hosted externally on Google Drive
  5. No explicit cookie consent mechanism found
  6. Multiple external partnerships and press coverage indicate active marketing
  7. Use of multiple tracking and analytics tools
  8. No direct company contact emails or phone numbers found on the site
  9. Strong focus on ICO and token sale with detailed roadmap and token info
  10. No visible security headers or advanced security policies published
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 fortyseven.io. 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 fortyseven.io.

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.

fortyseven.io security report: 61/100, medium risk | Guard