Skip to main content

Security report for financialtimes.com

Other · 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 currently presents a security challenge page that blocks access to its full content. This prevents extraction of meaningful business, contact, or compliance information. The domain is well-known as the Financial Times website, a major media and news organization, but the WHOIS query returned no data, indicating privacy protection or registry restrictions. The technical infrastructure shows use of strict Content-Security-Policy headers and JavaScript-based challenge scripts, typical of a Web Application Firewall (WAF) or bot mitigation service. Due to the blocking, no privacy policies, contact details, or business descriptions are accessible for analysis. Security posture is limited to header inspection and challenge detection, with no visible vulnerabilities but also no detailed security disclosures. Overall, the site is safe with no adult content detected, but the blocking significantly limits the ability to assess content quality, compliance, and business credibility.

Scanned

This is an earlier scan of financialtimes.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 financialtimes.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

Due to the WAF challenge page, no direct business intelligence data such as company details, market positioning, or services can be extracted from the site content. The domain is known to belong to a major media company, but no structured data or metadata is present in the accessible content. No partner or subsidiary domains were identified from the limited HTML. The lack of contact or policy pages reduces transparency and trust signals.

Security posture

The site employs a strict Content-Security-Policy header and JavaScript-based browser verification, indicating a mature security posture against automated threats. However, the absence of accessible security policies, incident response contacts, or vulnerability disclosure mechanisms limits the overall security transparency. The WHOIS data is unavailable, reducing domain registration trustworthiness. No SSL/TLS configuration details are visible from the content. The security score is moderate due to the presence of security headers but penalized heavily for blocking content and lack of visible compliance information.

Recommendations

  1. Work with the security provider to allow trusted scanners or users to access full site content for analysis.
  2. Publish clear privacy, cookie, and terms of service policies accessible without challenge.
  3. Provide visible contact information including security incident response channels.
  4. Ensure WHOIS data is available or provide transparency statements about domain registration.
  5. Implement and disclose a vulnerability disclosure or security.txt file to improve trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Page shows a browser verification challenge with minimal content and script loading attempts indicating a WAF or security challenge blocking full access. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor

Technology

Stack
JavaScript

Security

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

Analytics and tracking

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is blocked by a security challenge page.
  2. No meaningful content or metadata available for analysis.
  3. No privacy, cookie, or terms of service policies detected.
  4. No contact information or business details exposed.
  5. WHOIS data is unavailable or protected, limiting domain trust analysis.
  6. Security headers include a strict Content-Security-Policy.
  7. No external analytics or advertising scripts detected in the limited content.
  8. Site is safe with no adult or explicit content detected.
  9. Analysis incomplete due to WAF/security mechanisms. For accurate analysis, please contact guard@offseq.com
Technical notes

Notes

The site uses a strict Content-Security-Policy header restricting resource loading to self and data URIs, with specific hashes for styles and scripts. JavaScript is heavily used to load additional scripts dynamically, typical of anti-bot or WAF challenge pages. No CMS or hosting provider information is discernible. The site is optimized to block automated access, which impacts performance and accessibility for legitimate users and scanners. No analytics or advertising scripts are detected in the challenge page content. The technical implementation is modern but limits content availability.
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. 73/100Medium26 findingsView report
Reviews of this site

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