Skip to main content

Security report for freshemail.io

Freshworks · Technology · N/a

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

Security score

63/100

Risk levelMedium

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

Freshworks operates the freshemail.io domain as part of its email infrastructure supporting its suite of CX, ITSM, and CRM products. The domain is used primarily for SPF, DKIM, bounce email processing, and tracking email interactions. The website content is minimal, serving as an informational page with a clear abuse contact email. Technically, the site is hosted on AWS infrastructure using Amazon S3 and CloudFront but lacks a valid SSL certificate and modern TLS protocols, resulting in an insecure HTTP-only configuration. Security headers are minimal, and no advanced security or privacy policies are published on the site. The DNS and MX records align with legitimate email handling practices, and no subdomain takeover or DNSSEC issues are present. Overall, the site demonstrates basic technical infrastructure but lacks critical security and privacy compliance features.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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. 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';…

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

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

Keep watching freshemail.io

This scan found 21 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.

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
100
Security headers
15
Email security
40
DNS health
85
Network security
100
GDPR outside view
40
Average
63

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

Freshworks is a large technology company providing SaaS products focused on customer experience, IT service management, and CRM solutions. The freshemail.io domain supports their email communication needs, indicating a mature email infrastructure. The business model relies on delivering cloud-based software services with integrated email capabilities. The minimal website content suggests this domain is not customer-facing beyond email processing. The presence of a dedicated abuse contact email reflects a responsible approach to incident handling. No additional business information, certifications, or privacy policies are published on this domain, indicating it is a technical resource rather than a marketing or sales site.

Security posture

The security posture of freshemail.io is weak due to the absence of HTTPS and TLS support, exposing users to potential interception risks. No HSTS or OCSP stapling is configured, and no security headers beyond basic HTTP headers are present. While no known SSL vulnerabilities or subdomain takeover risks exist, the lack of encryption is a critical issue. Incident response contact is provided via abuse@freshemail.io, but no formal security policy or vulnerability disclosure program is published. The domain's DNS and MX configurations are sound, but the overall security maturity is low, requiring urgent improvements to meet modern security standards and compliance requirements.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS and protect data in transit.
  2. Enable modern TLS protocols (TLS 1.2 or 1.3) and disable insecure protocols.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Add comprehensive security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection.
  5. Publish privacy, cookie, and security policies on the domain or link clearly to corporate policies.
  6. Establish a formal vulnerability disclosure program and publish security contact information.
  7. Improve website content quality and SEO to enhance trust and user experience.
Technical notes

Notes

The freshemail.io domain is hosted on Amazon Web Services using S3 and CloudFront CDN, indicating a scalable and reliable infrastructure. DNS records include multiple A records pointing to AWS IPs and MX records configured for Google mail servers, supporting robust email delivery and processing. However, the website lacks a valid SSL certificate and does not support any TLS protocols, forcing unencrypted HTTP connections. No CMS or web frameworks are detected, and the HTML content is minimal with no forms, scripts, or analytics tools. Performance metrics are unavailable but inferred to be slow due to missing resource data. The site has basic mobile and accessibility features but lacks SEO optimization. Overall, the technical setup is functional for its purpose but requires modernization and security enhancements.
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 freshemail.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 freshemail.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.