Skip to main content

Security report for mercury.com

Mercury · Finance · United States

Low risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

78/100

Risk levelLow

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

Mercury is a fintech company specializing in banking services tailored for startups and technology companies. It offers business checking and savings accounts integrated with modern financial tools and APIs, positioning itself as a leading startup banking platform in the United States. The website reflects a mature digital presence with a modern tech stack including React, Next.js, and Cloudflare CDN, ensuring fast performance and excellent mobile optimization. Security is robust with HTTPS enforcement, comprehensive security headers, and SOC 2 Type II certification, although DNSSEC is not enabled. Privacy and cookie policies are comprehensive and GDPR compliant, supporting strong privacy practices. Overall, Mercury demonstrates a high level of professionalism, trustworthiness, and technical maturity.

Scanned

NIS2 and GDPR posture

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

4 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

  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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching mercury.com

This scan found 15 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
75
Security headers
40
Email security
87
DNS health
90
Network security
100
GDPR outside view
73
Average
78

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

Mercury operates in the finance and technology sectors, targeting startups and entrepreneurs with tailored banking solutions. Its business model focuses on providing seamless banking experiences with integrated APIs and financial tools, differentiating itself from traditional banks. The company maintains partnerships with key fintech players like Stripe and Plaid, enhancing its service ecosystem. Market positioning is strong within the US startup community, supported by clear branding and consistent messaging. The company was founded in 2017 and operates as a medium-sized enterprise with no public parent or subsidiary companies. Trust signals include certifications and positive customer testimonials.

Security posture

The website exhibits a strong security posture with HTTPS, multiple security headers, and no visible vulnerabilities or exposed sensitive data. The use of Cloudflare provides additional protection against DDoS attacks. However, the absence of DNSSEC is a minor gap that could be addressed to improve DNS security. There is no dedicated security policy or incident response contact information publicly available, which could be improved to enhance transparency and readiness. No vulnerability disclosure policy or security.txt file was found, suggesting an opportunity to formalize security communication channels.

Recommendations

  1. Enable DNSSEC to strengthen DNS security and prevent spoofing.
  2. Publish a dedicated security policy page outlining security practices and commitments.
  3. Provide explicit incident response contact information such as security@ or abuse@ emails.
  4. Implement and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Continue monitoring and updating third-party libraries to avoid vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Mercury
Description
Mercury provides banking services tailored for startups and technology companies, offering business checking and savings accounts with integrated financial tools.
Key services
business checking accounts, business savings accounts, integrated financial tools, API banking
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, Tailwind CSS, Cloudflare CDN
Frameworks
Next.js
Platforms
Cloudflare
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Security headers implemented
  • No exposed sensitive data in HTML
  • Use of Cloudflare for DDoS protection

Analytics and tracking

Services
Google Analytics, Segment
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Segment
Marketing tools
HubSpot, Intercom
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 no blocking or WAF challenges.
  2. Content is rich, professional, and targeted at startup banking customers.
  3. Strong use of modern web technologies and frameworks.
  4. Security posture is strong with HTTPS and security headers.
  5. Privacy and cookie policies are present and comprehensive.
  6. No suspicious or malicious indicators detected.
  7. WHOIS data supports legitimacy and domain stability.
Technical notes

Notes

Mercury's website is built on a modern technology stack featuring React and Next.js, styled with Tailwind CSS, and served via Cloudflare CDN for performance and security. The site is well-optimized for mobile devices and accessibility, with good SEO practices evident in meta tags and structured data. The hosting and infrastructure choices support fast loading times and reliable uptime. There is no indication of legacy or vulnerable technologies. The site uses JavaScript-based tracking and analytics tools such as Google Analytics and Segment, balanced with privacy compliance measures. Overall, the technical implementation supports a professional and scalable digital presence.
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 mercury.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 mercury.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.