Skip to main content

Security report for hellofax.com

HelloFax, Inc. · Technology · N/A

Medium risk. 4 critical or high findings in GDPR outside view.

Security score

73/100

Risk levelMedium

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

HelloFax, Inc. operates a top-rated online fax service that enables users to send and receive faxes digitally without the need for traditional fax machines. The company targets businesses and individuals seeking a modern, paperless faxing solution integrated with popular cloud storage platforms. Their business model is subscription-based SaaS, positioning them as a leading provider in the online fax market with strong customer trust and positive user testimonials. Technically, the website leverages modern web technologies including Webflow CMS, jQuery, Google Tag Manager, and Adobe Launch for marketing and analytics. Hosting and DNS are managed via Cloudflare and AWS, ensuring fast performance and global availability. However, the SSL configuration lacks modern TLS protocol support, which is a notable security gap. Security posture is generally strong with HSTS, CSP, and X-Frame-Options headers implemented, but lacks explicit vulnerability disclosure and incident response information. Cookie consent mechanisms are absent despite tracking scripts, indicating partial privacy compliance. Overall, the website is professional, trustworthy, and well-optimized, but could improve security and privacy transparency to enhance user confidence and regulatory compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics

      What to do: Document all third-party data sharing in your privacy policy

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

Keep watching hellofax.com

This scan found 16 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
85
Security headers
60
Email security
80
DNS health
90
Network security
100
GDPR outside view
25
Average
73

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

HelloFax holds a strong market position as a leading online fax service provider, leveraging integrations with cloud platforms and document signing capabilities to differentiate itself. The company’s subscription SaaS model generates recurring revenue streams targeting SMEs and enterprises needing reliable fax solutions. Their partnership with HelloSign enhances their service ecosystem. The website’s marketing tools and tracking indicate a mature digital marketing strategy focused on user acquisition and retention. Growth potential is supported by the shift from traditional fax machines to digital solutions. However, the absence of direct contact emails or phone numbers on the main site suggests a focus on digital support channels. Strategic partnerships and integrations are key competitive advantages. The company’s operations appear medium-sized with consistent branding and good content quality.

Security posture

The security posture of HelloFax’s website is solid with implementation of key HTTP security headers such as HSTS with includeSubDomains, Content Security Policy restricting frame ancestors, and X-Frame-Options set to SAMEORIGIN. The SSL certificate is valid and not self-signed, but the lack of enabled TLS protocols (TLS 1.2 or 1.3) is a critical weakness that could expose users to downgrade attacks or insecure connections. DNSSEC is not enabled and CAA records are improperly configured, which reduces DNS security. There is no publicly visible vulnerability disclosure or incident response contact information, which limits transparency and readiness perception. Cookie consent mechanisms are missing despite use of tracking and marketing scripts, which may impact GDPR compliance. Overall, the site follows many best practices but should address protocol support and transparency gaps to improve security maturity.

Recommendations

  1. Enable TLS 1.2 and TLS 1.3 protocols on the web server to ensure secure encrypted connections.
  2. Properly configure CAA DNS records to restrict certificate issuance and enhance DNS security.
  3. Implement a visible cookie consent mechanism to comply with GDPR and enhance user privacy transparency.
  4. Publish a vulnerability disclosure policy and provide incident response contact channels to improve security transparency and trust.
  5. Review and enhance SSL certificate details to specify algorithm and ensure strong cryptographic standards.
Technical notes

Notes

The website infrastructure is modern and performant, leveraging Webflow CMS, jQuery, and third-party marketing and analytics tools such as Google Tag Manager and Adobe Launch. Hosting is via Cloudflare CDN and AWS DNS, providing global reach and fast load times. The site is mobile optimized with good SEO practices and consistent branding. However, the absence of TLS protocol support is a significant technical risk. DNSSEC is not enabled, and CAA records are misconfigured, indicating areas for DNS security improvement. The site uses multiple external domains for assets and scripts, mostly trusted partners. Performance metrics indicate fast load times though no explicit resource counts or page size data were available. Overall, the technical stack is solid but requires security protocol upgrades and DNS hardening to reduce operational risks.
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 hellofax.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 hellofax.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.