Run the check

Changelog

This page records meaningful updates to guidance, trust pages, and editorial process so parents and guardians and reviewers can see what changed, when it changed, and why it changed.

Author: Editorial team, ParentalControl.uk. Reviewed by: SSS Group editorial board. Last verified: 18 May 2026. Version tested: Release log reviewed 18 May 2026. Changelog: view updates.

Initiative funded and led by Dr Alex J. Martin-Smith, CMgr · MBA · LLM · DBA. Contact Alex directly at ams@upleashed.com or 0330 122 1223 / 07624 218080.

18 May 2026 v9.1 scanner accuracy and transparency update

  • Streaming scoring fix. The streaming sub-score now contributes to the final total. Before this fix the highest score a fully filtered home could achieve was 92/100; the maximum is now 100/100 as intended.
  • Updated statistic. Replaced an older, unsourced two-thirds line with the Ofcom Children's Passive Online Measurement figure (published 27 June 2025): 8 per cent of UK children aged 8 to 14 visited an online pornography site or app within a single month, including around 3 per cent of 8 to 9-year-olds.
  • Accuracy caveat panel. The results screen now shows a short panel explaining what the live probe tests, what it cannot see, and what to do if the score looks lower than expected.
  • Experimental DNS detection. A browser-side resolver probe has been added in parallel with the existing check. It is clearly labelled experimental in the interface. Real-world accuracy figures will be published as data accumulates.
  • New page: how we test DNS. Plain-English explanation of what the probe does, what it cannot detect, and five manual checks a parent can run in two minutes.
  • Privacy promise unchanged. No new tracking, no new cookies, no localStorage, no third-party scripts. Every probe is initiated from the browser and we still do not store the result.
  • v9.1.1 polish (same evening). Removed false-positive vector where UK ISP block-page reachability was being scored as positive ISP filter detection. These signals are now reported informationally only. The probe now positively identifies Cloudflare for Families and OpenDNS FamilyShield only. Other configurations report "none detected" honestly. Conservative scope is deliberate: zero false positives is the bar for a child-safety tool.

18 May 2026 footer legal line refresh

  • Updated the shared footer legal copy to include SearchSwitchSave and Upleashed group wording, Isle of Man company numbers, D-U-N-S, ICO registration, and the current UK trade marks.
  • Set the footer review line to 17 May 2026 and kept the visible View changelog link in place for transparency.

17 May 2026 schools briefing, mobile menus, PWA pause

  • Published KCSIE 2025 alignment for Designated Safeguarding Leads, including an eight-point evidence map, downloadable PDF briefing, and drop-in policy copy.
  • Linked the briefing from regulation, about, navigation, footer, sitemap, and llms.txt.
  • Temporarily disabled installable PWA via PCUK_PWA_ENABLED in site config. Manifest and icon files remain on disk for a later re-enable.
  • Fixed mobile and installed-app menus that stayed expanded because CSS overrode the HTML hidden attribute. Header JavaScript now resets menu state on load and outside taps.
  • Rewrote Sure (Isle of Man) and Manx Telecom setup content using current provider sources, including corrected support numbers and verified setup paths.
  • Replaced the old three-question ISP FAQ with a shared eight-question parent-facing FAQ across all /setup/<provider>/ pages, removing the visible timing-template bug.

15 May 2026 v2.0 release

ParentalControl.uk v2.0 ships the full trust and content rebuild for parents and guardians and for regulators reviewing the site. Header navigation is harmonised, the trust pages are rewritten, AI and regulation pages are fully rebuilt, setup and help content is expanded across UK and Isle of Man journeys, and the structural sweep aligns trust spine and last-reviewed signals. Schema and citation audits were completed for this release track, alongside accessibility and performance evidence capture in the v3 proof packs.

We are also keeping the 14 May 2026 incident on record in plain English. An auto-fix script wrote placeholders into source files. Recovery was handled by wiping the affected tree, restoring from a clean live baseline, and replaying changes under git with one change per commit. No bulk script now writes to source content.

14 May 2026 incident note

A failed auto-fix path inserted placeholder tokens into source files. The affected tree was archived for forensic reference, then discarded. Recovery used a clean restore from live production and a one-change, one-commit workflow to rebuild safely.

13 May 2026 v1.0 launch baseline

  • Published initial site structure, baseline guidance pages, and core navigation.
  • Shipped first release across setup, DNS, connected-device, and trust-supporting pages.