Skip to content
https://www.ft.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
96
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
403 Forbidden
Checks
9
6 PASS 3 REVIEW
B
DNS Records
2 A records, 31 ms lookup
REVIEW
2 A records, 31 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.5.165, 104.18.4.165
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:5a5, 2606:4700::6812:4a5
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www.ft.com.cdn.cloudflare.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 31 ms
Got: 31 ms
A104.18.5.165, 104.18.4.165
AAAA2606:4700::6812:5a5, 2606:4700::6812:4a5
CNAMEwww.ft.com.cdn.cloudflare.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 31 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
TLS Certificate Expiry & Recommendations
84 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

84
days left
0d 30d 60d 90d+

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: 9e8bbaa3bbbaf864-CDG
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e8bbaa3bbbaf864-CDG
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.ft.com

https://www.ft.com

185 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.ft.com200185 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700::6812:5a5, 2606:4700::6812:4a5
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700::6812:5a5, 2606:4700::6812:4a5 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 285 URLs
PASS
robots.txt present, sitemap with 285 URLs
Info::
robots.txt is present
Got: 1557 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 285 entries
Info::
Sitemap index with 285 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1557 B Sitemaps referenced 1 User-agents *, Bytespider, Claude-Web, ClaudeBot, Applebot-Extended, Google-Extended, anthropic-ai, omgili, omgilibot, FacebookBot, Meta-ExternalFetcher, CCBot, magpie-crawler, NewsNow, PerplexityBot, Diffbot, GoogleOther, cohere-ai, Perplexity-User, meta-externalagent Blocking No — crawling allowed
# All use of FT content is subject to the Terms & Conditions and
# Copyright Policy set out on FT.com

# We expressly prohibit any use of our content or data for any
# machine learning or artificial intelligence purposes, including
# the training or development of AI technologies or machine learning
# language models.
#
# For any licensing queries please contact content.licensing@ft.com

Sitemap: https://www.ft.com/sitemaps/index.xml

User-agent: *
Disallow: /__
Disallow: /_fs-ch
Disallow: /article/e63d8640-eeb3-4473-b0ad-aa6aec16d9fe
Disallow: /buy/
Disallow: /cancel/
Disallow: /join/
Disallow: /login
Disallow: /myft/
Disallow: /offline/
Disallow: /page-resources
Disallow: /preferences/manage-cookies
Disallow: /register/
Disallow: /search
Disallow: /signup
Allow: /__origami/
Allow: /__assets/
Crawl-Delay: 1

User-agent: CCBot
Disallow: /

User-agent: Google-Extended
Disallow: /
Allow: /*?syn-25a6b1a6=1

User-agent: GoogleOther
Disallow: /

User-agent: anthropic-ai
Disallow: /

User-agent: omgili
Disallow: /

User-agent: omgilibot
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: magpie-crawler
Disallow: /

User-agent: NewsNow
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Perplexity-User
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: meta-externalagent
Disallow: /

User-agent: Meta-ExternalFetcher
Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 285 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.ft.com/
301https://ft.com/

Preferred variant: www

HTTP → HTTPS

301http://www.ft.com/ → https://www.ft.com/

Consistent

A+
Domain Intelligence
ft.com — via CSC Corporate Domains, Inc., 31 years, 9 months old, hosted on Fastly
PASS
ft.com — via CSC Corporate Domains, Inc., 31 years, 9 months old, hosted on Fastly
Info::
Domain registered until Nov 29, 2026 (7 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: CSC Corporate Domains, Inc.
Info::
Hosting: Fastly
Got: AS54113
Domain expiry

104 days

November 29, 2026

SSL certificate

84 days

Issued by Google Trust Services

Domain age

31 years, 9 months

Registered November 30, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.66.46

Registrar

CSC Corporate Domains, Inc.

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar CSC Corporate Domains, Inc.
Created November 30, 1994 (31 years, 9 months ago)
Expires November 29, 2026 (7 months)
Last Updated November 25, 2025
Name Servers ns-1447.awsdns-52.org, ns-1984.awsdns-56.co.uk, ns-52.awsdns-06.com, ns-530.awsdns-02.net
DNSSEC Not enabled
Hosting
IP Address 151.101.66.46
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.3s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

A+
HTTP Probe Timing
Total 143 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
30 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
23 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
111 ms
Total Time Total request time from DNS lookup through full response.
144 ms

Connection waterfall

DNS Lookup 30 ms TCP Connect 16 ms TLS Handshake 23 ms Server Processing 41 ms Content Transfer 33 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback