Bloom Apps, Inc. · Technology · United States
Low risk. No critical or high findings.
Bloom Apps, Inc. operates Bloom.io, a comprehensive SaaS platform designed to streamline business workflows and client management for professional services. The platform offers a suite of integrated tools including CRM, invoicing, payments, contracts, client portals, scheduling, and automation, positioning itself as a niche solution for service professionals seeking an all-in-one workspace. The company maintains a clear market position with a focus on usability and integration with popular payment and communication services. Technically, Bloom.io leverages modern web technologies such as React and Next.js, hosted primarily on AWS infrastructure with integrations to Firebase, Stripe, Square, and Zoom. The website demonstrates strong digital maturity with fast performance, mobile optimization, and good SEO practices, supported by structured data and comprehensive metadata. From a security perspective, the site enforces HTTPS, employs security headers, and integrates anti-bot measures like Google reCAPTCHA. While no critical vulnerabilities or exposed sensitive data were detected, the absence of a dedicated security policy or incident response information suggests room for improvement in transparency and preparedness. Overall, Bloom.io presents a professional, trustworthy, and technically sound platform with strong business credibility. Strategic enhancements in security communication and vulnerability disclosure would further strengthen its risk posture and customer trust.
Scanned
NIS2 Art. 21(2)
The NIS2 figure counts only evidence anyone can see from the internet. 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.
No critical or high findings. These medium findings are worth fixing next.
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.
No Content-Security-Policy is set, so if an attacker manages to inject a script (cross-site scripting), the browser runs it with full access to the page.
What to do: Start with "Content-Security-Policy: object-src 'none'; base-uri 'self'; frame-ancestors 'self'" and add a script-src that lists your script origins or uses nonces. Test with a Report-Only header first.
Other websites can load your pages inside an invisible frame and trick visitors into clicking buttons on them (clickjacking).
What to do: Send "Content-Security-Policy: frame-ancestors 'self'" (or X-Frame-Options: SAMEORIGIN for older browsers).
This scan found 11 issues across 5 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.
€25per month
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.
€39.90one-time
Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.
Each check with its score, findings and the evidence it collected.
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
Not counted
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.
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
Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.
Leaked records that mention bloom.io, from OffSeq Breach.
76 subdomains affected
See the 10 newest leaked credentials
A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for bloom.io.
Select it in the checkout above.
Breach keeps ingesting new leaks, so these numbers can grow between scans.
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Automated reading of the public site. Ratings are indicative.
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
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with bloom.io. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review bloom.io.