Skip to main content

Security report for ft.com

Media · N/a

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

Security score

73/100

Risk levelMedium

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

The website www.ft.com is currently inaccessible due to a browser verification challenge page, likely implemented by Fastly's CDN security layer. This challenge blocks direct access to the site's content, preventing a full analysis of the website's business, privacy, and security posture. The Financial Times is a globally recognized media company, but the provided HTML content does not reveal typical business or contact information, privacy policies, or terms of service. The WHOIS data query failed to return any registrar or registrant information, likely due to querying the 'www' subdomain or privacy protections, which reduces transparency and trustworthiness from a domain registration perspective. Technically, the site uses JavaScript and enforces a Content-Security-Policy header, indicating some security best practices. Hosting is via Fastly CDN, which is consistent with a large media enterprise. However, no analytics, advertising, or tracking scripts were detected in the provided content, likely due to the blocked state. The security posture is limited by the lack of visible headers and policies, and the privacy compliance cannot be assessed. Overall, the site is safe in terms of content, with no adult or explicit material detected. However, the inability to access full content and metadata due to the WAF challenge significantly limits the analysis. The domain's WHOIS data is unavailable, which is unusual for a major media brand but may be explained by privacy or query scope. The overall risk is moderate due to these access limitations, and strategic recommendations focus on improving transparency and ensuring compliance disclosures are accessible post-challenge.

Scanned

This is an earlier scan of ft.com. View the latest report

NIS2 and GDPR posture

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

6 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"

  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

    • 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

  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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching ft.com

This scan found 18 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
62
Security headers
60
Email security
82
DNS health
85
Network security
100
GDPR outside view
50
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

The Financial Times operates in the media sector as a large enterprise with a global audience. Its business model revolves around providing premium news content, financial analysis, and subscription services. The company likely generates revenue through subscriptions, advertising, and partnerships. The use of Fastly CDN indicates a focus on performance and security for a high-traffic website. The lack of visible contact or policy information in the challenge page limits insight into customer engagement and compliance practices. The brand is well-established, but the current content access restrictions hinder competitive and operational analysis.

Security posture

The website employs a Content-Security-Policy header and uses Fastly CDN, which suggests a baseline security posture with modern infrastructure. However, the presence of a browser verification challenge indicates a strict WAF or bot mitigation strategy that blocks direct content access, which can impact user experience and analysis. No other security headers or incident response contacts are visible. The absence of privacy and cookie policies, contact information, and vulnerability disclosure mechanisms indicates gaps in transparency and compliance readiness. The WHOIS data unavailability further reduces trust signals. Overall, the security posture is moderate but could be improved by enhancing policy visibility and incident response readiness.

Recommendations

  1. Improve WHOIS transparency by ensuring domain registration data is publicly accessible or clearly justified if privacy protected.
  2. Make privacy, cookie, and terms of service policies accessible even behind security challenges to improve compliance and user trust.
  3. Publish clear contact and incident response information to support security and compliance requirements.
  4. Enhance security headers beyond Content-Security-Policy, including HSTS, X-Frame-Options, and X-Content-Type-Options.
  5. Review WAF challenge configuration to balance security with user accessibility and SEO considerations.
Site observations

Automated reading of the public site. Ratings are indicative.

Fastly detected. Page is a browser verification challenge likely from Fastly WAF or CDN security layer, blocking direct content access These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Technology

Stack
JavaScript

Security

Observed score
30/100
Good practices seen
  • Content-Security-Policy header present

Analytics and tracking

Site quality

Trustworthiness
low

Key observations

  1. Website content is inaccessible due to a browser verification challenge page
  2. No visible privacy, cookie, or terms of service policies in the provided HTML
  3. No contact information or forms detected
  4. Minimal HTML content with scripts to load further resources
  5. Security headers limited to Content-Security-Policy
  6. No analytics or advertising scripts detected in provided content
  7. No social media or external links except to Fastly CDN
  8. WHOIS data unavailable, indicating privacy or query on subdomain
  9. Site likely uses Fastly CDN with security challenge enabled
Technical notes

Notes

The website uses JavaScript and enforces a Content-Security-Policy header, indicating modern security practices. Hosting is via Fastly CDN, a reputable provider for media companies. The HTML content is minimal and serves as a browser verification challenge, blocking access to the main site content. No CMS or analytics technologies are detectable in the provided snippet. Performance and SEO optimization cannot be assessed due to content blocking. Accessibility features are unknown. The technical infrastructure appears robust but is currently limiting content availability for analysis.
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

Earlier scans of this domain

  1. 82/100 +8Low22 findingsView report
  2. 74/100Medium26 findingsView report
  3. 75/100Medium3 findings · partial scanView report
Reviews of this site

Share your experience with ft.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 ft.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.