snag.page

bbc.co.uk

Checked 16 Nov 2026, 20:09 UTC ยท

5 things to fix

3 medium2 low17 passed

What to fix

  1. HTTPS Browsers keep trying http:// first, where the connection can be intercepted before the redirect.

    1. Add the header below to every https:// response.
    2. Once every subdomain works over HTTPS, add includeSubDomains and preload, and submit the domain at hstspreload.org.
    Header
    Strict-Transport-Security: max-age=31536000

    About this check

  2. Headers Nothing limits where scripts can load from, so a script injected into a page would run.

    1. Send the policy below as Content-Security-Policy-Report-Only, and see what it would block.
    2. Add the sources your pages need to it.
    3. Then send it as Content-Security-Policy.
    Header
    Content-Security-Policy-Report-Only: default-src 'self'; object-src 'none'; base-uri 'none'; frame-ancestors 'self'

    About this check

  3. Headers A page elsewhere could show this one in a frame and trick visitors into clicking on it.

    1. Add frame-ancestors 'self' to the CSP, or send the header below.
    Header
    X-Frame-Options: SAMEORIGIN

    About this check

  4. Headers Browsers may guess a file's type, and run as a script a file that wasn't meant to be one.

    1. Send the header below with every response.
    Header
    X-Content-Type-Options: nosniff

    About this check

  5. DNS Answers about the domain can't be checked, so a resolver can be fed false ones.

    1. Turn on DNSSEC at your DNS host.
    2. Add the DS record it gives you at your registrar; where one company is both, it is often one switch.

    About this check

Also worth doing

  1. Headers Nothing limits what embedded content may ask for, such as the camera, microphone or location.

    1. Send the header below, turning off what the site never uses.
    Header
    Permissions-Policy: camera=(), microphone=(), geolocation=()

    About this check

  2. Headers A window this page opens, or one that opened it, keeps a handle on it that can be misused.

    1. Send the header below; use same-origin-allow-popups if the site opens sign-in or payment windows.
    Header
    Cross-Origin-Opener-Policy: same-origin

    About this check

  3. Email snag.page looked under the names most providers use; without DKIM, receivers can't check your email was signed by you.

    1. Turn on DKIM signing at your email provider.
    2. Publish the TXT record it gives you.

    About this check

  4. 9

    No MTA-STS

    Worth doing

    Email Servers sending you email may deliver it unencrypted if someone interferes with the connection.

    1. Publish a policy at https://mta-sts.bbc.co.uk/.well-known/mta-sts.txt.
    2. Then add the record below, changing its id whenever the policy changes.
    TXT record at _mta-sts.bbc.co.uk
    v=STSv1; id=1

    About this check

  5. 10

    No TLS reporting

    Worth doing

    Email Servers that can't deliver your email securely have nowhere to say so, so a broken certificate or MTA-STS policy goes unnoticed.

    1. Add the record below, with an address that can take a daily report.
    TXT record at _smtp._tls.bbc.co.uk
    v=TLSRPTv1; rua=mailto:tls-reports@bbc.co.uk

    About this check

  6. 11

    No security.txt

    Worth doing

    Security contact Someone who finds a flaw in the site has no published way to tell you.

    1. Publish the file below at /.well-known/security.txt, with your own address.
    2. Put a reminder in to renew its Expires date.
    /.well-known/security.txt
    Contact: mailto:security@bbc.co.uk
    Expires: 2027-11-16T20:09:19Z

    About this check

Quality

1 to improve1 passed

  1. 12

    No llms.txt

    Worth doing

    AI and agents An llms.txt gives AI assistants a short guide to the site and links to plain versions of its pages.

    1. Publish /llms.txt in Markdown: a heading with the site's name, a one-line summary, then links to the pages that matter.
    /llms.txt
    # Site name
    
    > What the site does, in a sentence.
    
    ## Pages
    
    - [About](https://bbc.co.uk/about): who runs it

    About this check

All checks

30

HTTPS

  • No HSTS header
  • Answers over HTTPShttps://www.bbc.co.uk/ answered 403.
  • Sends http:// to https://
  • bbc.co.uk and www.bbc.co.uk both lead to www.bbc.co.uk

Headers

DNS

  • DNSSEC is off
  • Has an IPv6 address
  • CAA limits who can issue certificatesAllowed: amazon.com, digicert.com, globalsign.com.
  • The domain is registered for over a monthUntil 2034-12-13.

Email

  • No DKIM key under the usual names
  • No MTA-STS
  • No TLS reporting
  • SPF is setv=spf1 ip4:212.58.224.0/19 ip4:132.185.0.0/16 +include:spf.sis.bbc.co.uk +include:spf.messagelabs.com ~all
  • SPF takes 4 of the 10 lookups allowed
  • DMARC is enforcedp=reject.
  • Every mail server existscluster1.eu.messagelabs.com and cluster1a.eu.messagelabs.com.

Security contact

AI and agents

Cookies

  • Sets no cookies on the home page

Exposed files

  • No exposed files found49 well-known paths checked.

Open services

  • No risky services seen openIts addresses are a CDN's, so Shodan's scans see the CDN, not the server behind it.

Reputation

Loading

  • One redirect before the page

Speed for real visitors

Passes Core Web Vitals

Loading LCP

837 ms

Good

96% good1% poor

Responsiveness INP

120 ms

Good

88% good3% poor

Visual stability CLS

0.00

Good

99% good1% poor

First content FCP

679 ms

Good

Server response TTFB

380 ms

Good

Passes Core Web Vitals

Loading LCP

779 ms

Good

97% good1% poor

Responsiveness INP

57 ms

Good

95% good2% poor

Visual stability CLS

0.00

Good

98% good1% poor

First content FCP

609 ms

Good

Server response TTFB

398 ms

Good

The 75th percentile of Chrome users' page loads at www.bbc.co.uk, 18 Oct 2026 to 14 Nov 2026.