What's newin WebScore

Domains that send no email are graded as such

FixedImproved

Fixed — A domain deliberately set up to send and receive no email — a null MX record, an SPF record of "v=spf1 -all", a reject DMARC policy and a wildcard DKIM record with an empty key — was graded as if it were misconfigured. The wildcard DKIM record, which revokes every signing key, looked to the scanner like a DNS setup that answers every name, so DKIM came back "can't be verified". And the DMARC record was marked down for not asking for reports that a domain sending no mail has no use for. Both were false alarms and no longer appear.

Improved — The Email Authentication card now recognises a null MX record and says so: the domain is graded as a no-mail domain, DKIM shows "all selectors revoked" instead of "missing", and the fix instructions for any gap give the exact records such a domain should publish rather than a mail provider's SPF include.

Improved — The free Email Security Checker and the check_email_auth MCP tool make the same distinction, so all three give a no-mail domain the same verdict.

Improved — A DKIM record with an empty key is a revocation, not a key. It is no longer counted as DKIM being configured on a domain that does send mail, and a domain that revoked every selector while still publishing mail servers is told so, with the two ways to resolve it.

v2.1.67 — released September 8, 2026

Conversion audits tripped up by an emoji

Fixed

Fixed — A Conversion audit could fail with "The AI analysis returned an unusable result" on pages that use emoji in headings, buttons or link text. When the audit shortened that text to fit its request, it could cut an emoji in half, and the half-character made the whole request unreadable to the AI. The text is now cleaned before it is sent, so an emoji at the cut point no longer sinks the audit.

v2.1.66 — released September 4, 2026

Conversion audits that failed on the next site

FixedImproved

Fixed — Running a Conversion audit on a second website could fail straight away with a browser error ("Target page, context or browser has been closed") even though the first one had worked. The audit kept one browser open between runs to save a second, and when that browser crashed, every audit after it was handed the dead browser. Each audit now gets a fresh browser of its own, and if the browser crashes mid-capture the audit retries once before giving up.

Improved — The audit's browser now runs in the same, sturdier mode the site scanner already uses, so one heavy page can no longer take the whole browser down with it.

Improved — When the browser does crash, the audit now says so in plain words instead of showing the raw error.

v2.1.65 — released September 3, 2026

A Best Practices score of 0 that wasn't real

FixedImproved

Fixed — Some sites came back with a Best Practices score of 0 while every other module scored normally. Nothing was wrong with those sites — the audit behind that one module had failed to run, and a failed run was being written down as a score of zero. Because a site's overall score is the average of its five modules, that phantom zero quietly cost it around twenty points of overall health as well.

Improved — Best Practices is now measured through Google PageSpeed Insights, the same place the Performance score already comes from. It runs on Google's machines instead of ours, so it no longer competes with the scan's own browser for memory, and sites that turn away traffic from our server no longer turn away the audit.

Improved — When the audit genuinely can't run, the module now says so and records no score at all, instead of showing a 0 that reads like a verdict on your site. Scan again and it fills in.

v2.1.64 — released August 22, 2026

google.com is allowed again

FixedImproved

Fixed — Scanning from the homepage could answer "that host is not allowed" for perfectly ordinary sites — google.com among them. The safety check that keeps the scanner away from private, internal addresses was reading every IPv6 address as internal, so any site reachable over IPv6 was turned away before we even tried it. Sites without IPv6 were unaffected, which is why it looked arbitrary: github.com worked, google.com didn't.

Improved — The same check now understands addresses that carry an IPv4 one inside them, so it judges the address a name really points at rather than the way it happens to be written.

v2.1.63 — released August 17, 2026

Get updates by email

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