What's newin WebScore

Every release, now on the public hub

New

New — The whole release history — all 71 versions back to 2.0.0 — now sits on the public changelog hub next to the feedback board and the status page. You can link someone to a single release, or subscribe by RSS and stop checking the site to find out what changed. This page stays the place releases are written; the hub mirrors it.

v2.1.62 — released August 17, 2026

Feedback in the open, plus live status

New

New — Feedback now goes to a public board instead of a private email to us. You can see what other people have already asked for, add your voice to it rather than filing the same thing again, and follow what happens next. The button sits bottom-right on every page inside the app, and there's a Feedback link in the site footer. If you're signed in, your name and email come along, so all you write is the idea itself.

New — A "What's new" badge on the public site opens the release notes in place, and shows a dot when there's something you haven't read yet. It stays out of the app itself — inside your dashboard the only thing floating is the feedback button.

New — The site footer now carries live uptime for the last 30 days, and links through to a full status page. If a scan ever fails on you, you can check in one glance whether it's us.

v2.1.61 — released August 17, 2026

TLS 1.3 detection that doesn't depend on the weather

Fixed

Fixed — Scans run from our servers could report "TLS 1.3 not enabled" for sites that have it — the check parsed openssl's console output, whose format differs between systems and often omitted the line we read for TLS 1.3 connections. The scan now asks the TLS connection itself, which gives the same correct answer everywhere. If your security report claimed TLS 1.3 was missing, re-scan — it wasn't.

v2.1.60 — released August 16, 2026

The SSL checker stops penalizing TLS 1.3

Fixed

Fixed — The free SSL checker flagged sites on TLS 1.3 with "weak cipher strength: 0 bits" and docked their grade — the newest, strongest protocol scored worse than the old one. The cipher strength is now read correctly for TLS 1.3 suites, so a modern setup gets the clean A it deserves. The full scan and dashboard were unaffected.

v2.1.59 — released August 16, 2026

DKIM detective work, and a fix for freshly added websites

ImprovedFixed

Improved — The scan now discovers custom DKIM selectors instead of only checking a fixed list: names derived from your own domain (a real user's key lived at yourdomain._domainkey), rotation years like s2025, and your email providers' conventional selectors on their sending subdomains — with a wildcard-DNS guard so guessing can never produce a false positive. Found keys also report their strength, so a 1024 to 2048-bit upgrade shows up as exactly that. Thanks to the bepublish.com report that drove this.

Improved — Your AI assistant can verify any selector directly: the MCP email check accepts a dkimSelector parameter and reports precisely whether that name answers.

Fixed — Websites added in the last few days could fail their first scan with "Page not found for this website" — adding a site stopped registering its home page behind the scenes. New sites are created correctly again, and any affected site repairs itself automatically on its next scan.

v2.1.58 — released August 15, 2026

Get updates by email

An email when WebScore ships something new, and nothing else. Unsubscribe any time.