← Back to Blog

Mega Security Analyzer: What Your Website Shows, What Needs Fixing

· Updated November 6, 2026 · 13 min read Mega Security Analyzer: What Your Website Shows, What Needs Fixing

Your website can look fine while an old plugin, a forgotten development build or a publicly readable configuration file needs attention. The hard part is knowing which warning deserves a call to your developer and which one needs more evidence.

We built the free Mega Security Analyzer to make that conversation easier. Enter a website address and we read a bounded sample of its public pages, assets and settings. The report explains what we found, what we could not establish, and where a fix belongs. You do not need an account.

This October 31 update replaces our earlier description of seven layers and confirmation with three probes. We now join public software evidence to dated vulnerability sources, show coverage limits alongside findings, and give owners a clearer report. We do not turn a public version clue into proof that someone can break into your site.

November 4, 2026 update

The Mega Analyzer and Agent Endpoint Inspector now cover more of the connections your site relies on. These additions belong to those companion tools. The Security Analyzer checks described in the October 31 update below still apply.

Linked subdomain takeover candidates. Mega Analyzer checks linked names under your domain for missing DNS destinations and signs that a hosting service is no longer claimed. A forgotten DNS alias can leave visitors pointing at a service you no longer control. The provider list covers 22 services: 18 have specific unclaimed service fingerprints, while four receive DNS checks only. A matching error page is a candidate for review, not proof that someone can claim it. Ask your developer to confirm ownership, remove unused DNS records or restore the service under your account.

Dangling script and frame hosts. A script host that no longer resolves is a high finding because someone who later controls that host could supply code to your visitors. A missing frame host receives a warning. Remove the abandoned reference or move it to a service you control, then check the affected page. An incomplete DNS answer stays unknown; it does not prove that a host has disappeared.

Form destinations. Mega Analyzer flags an HTTPS page whose form sends information over HTTP, or sends sensitive fields to another origin. That origin is the receiving site's combination of scheme, hostname and port. Known form services are named; unfamiliar recipients need review. Ask your developer to use HTTPS and verify who controls the receiving account before collecting information. The check reads the form markup without submitting it. It cannot establish account ownership or follow every submission handled by JavaScript.

Authorization discovery for AI connections. If your site offers an MCP server protected by OAuth, the Inspector, with its agent handshake box ticked, checks whether an assistant can discover the protected resource and authorization server metadata, find secure endpoints and see support for PKCE S256. It also distinguishes Client ID Metadata Documents from the older Dynamic Client Registration option. Discovery uses at most four GET requests and never asks for a token. A warning means your developer should repair the published discovery details or supported connection settings; it does not establish that an account was accessed. The Inspector update explains the July 28, 2026 protocol revision and its registration changes.

Tool descriptions need review too. With the agent handshake ticked, the Inspector looks for hidden instructions, links to other origins, invisible characters and tool names that could be confused with familiar tools. These are prompts for a person to review context, not verdicts about intent. Ask the publisher to remove unexplained instructions and clarify names and destinations. You can also pin the tool list in your browser using a SHA256 digest, a fingerprint of its definitions. Later changes to names, descriptions or argument definitions need review before you accept a new baseline.

What we check now

Known vulnerabilities and the software behind them

For supported packages we can identify, we use live OSV lookups at scan time, with dated cached answers where available. OSV includes advisories from sources such as the GitHub Advisory Database. This replaces a manually maintained list of CVEs and blanket assumptions that an older JavaScript version must be vulnerable.

We join matched CVE identifiers with CISA's Known Exploited Vulnerabilities catalog and FIRST's Exploit Prediction Scoring System. KEV tells us a vulnerability has been exploited in the wild. EPSS adds an estimate of exploitation likelihood. Neither says that your particular site has been compromised, and a missing KEV entry is not a safety certificate.

For WordPress, we check publicly identified core, plugins and themes against the dated Wordfence Intelligence feed from Defiant. Rows name the component where possible, link its advisory or vendor changelog, and retain the advisory's affected and fixed versions, source date and attribution. CVE records also carry the MITRE notice.

The wording matters. A version in a plugin asset address may be a cache label rather than the installed release. A hint that overlaps an advisory says “may be affected” and stays unknown. An exact public version can support an affected version finding, but that still does not confirm exploitation or the site's private configuration. If we cannot identify a version or reliably compare the advisory range, we say so.

Software that has reached the end of support

We use endoflife.date for supported product families including PHP, Node.js, nginx, Apache HTTP Server and WordPress, with other families covered by the scanner's software catalog. When public evidence identifies a release line whose support has ended, the report flags it and gives the support date.

There is an important hosting caveat: a vendor may provide extended support or backport security fixes without changing the public version number. We ask the owner to upgrade unless the host can confirm that coverage. A banner alone cannot tell us which private patches are installed.

Build mistakes and exposed files

We look for declared public source maps, development builds, debug output and evidence of exposed lockfiles or configuration files. Source maps can reveal original source code; lockfiles can reveal dependency versions. Neither proves that every listed dependency runs on the public site.

Sensitive file checks belong to the separate owner option below. We do not crawl an unlimited list of possible filenames, validate credentials or try to use anything we find.

Connections, browser protections, DNS and privacy clues

We check whether the measured HTTP addresses actually redirect to HTTPS, along with TLS connection and certificate evidence. A TLS connection error remains a measurement problem with its reason attached. It is not automatically an intentional block, and one negotiated protocol does not establish every protocol the server accepts.

Security headers are judged by what their values enforce. An HSTS header with no effective lifetime is different from working HTTPS enforcement. A Content Security Policy in report only mode observes problems without blocking them. Framing, referrer and permissions policies also need usable values, not merely a familiar header name.

DNS and email checks cover SPF, DMARC, sampled DKIM selectors and key size, CAA certificate issuer policy, and DNSSEC authentication evidence. The report names the domain being checked. It does not assume that the website hostname is also the business's email domain. A missing sampled DKIM selector does not prove that the business has no signing key, and an unauthenticated DNS answer does not prove that the zone has no signing records.

We also inspect observed cookie attributes and tracker references. These are clues from the sampled response and code. They do not establish every cookie a signed in visitor receives, whether a tracker actually ran, or whether the site complies with privacy law.

The owner checkbox adds specific checks, not an attack

The page offers “I own this site or have permission to test it.” Tick it and deliberately press Run or Enter to include a short, fixed list of exposed file checks. On detected WordPress sites, the conditional checks also include a public users endpoint and an XML remote procedure call that only reads data. The users check retains an account count, not names or profiles. Paths excluded by the site's robots policy are not requested.

Your choice is remembered for that site in that browser, and you can reset it. A link that fills in an address or automatically starts an ordinary scan cannot authorize owner checks, even when permission was remembered. Use the deliberate “Run the owner checks too” button when offered. Permission does not transfer to a different origin after a redirect.

If we identify a possible secret, the report shows its type, first four characters and length only, with the prefix omitted for very short values. Full secret values and raw sensitive file contents stay out of the report, exports and AI prompt. We do not try a key to see whether it works. If your developer confirms a real exposure, removing the public file is only part of the repair; the credential also needs rotation with its provider.

The boundary is the same with or without the tick:

This scan only reads what your site already shows every visitor. Anything beyond that, such as signed in scans, injection or configuration testing, or load testing, is a separate engagement. It starts only after the site owner approves it in writing and ownership is verified with a DNS record or a file on the site.

How the security information stays current

There are two update paths. Supported package lookups and EPSS requests happen at scan time, subject to their caches and availability. The larger reference feeds, including Wordfence, are maintained separately from each visitor's scan. We do not send the visitor's site or component inventory to Wordfence.

Our weekly GitHub Action can refresh validated security data separately from the website, so those updates do not need a redeploy. A failed refresh preserves the last validated data instead of replacing it with an incomplete download.

You can inspect the result in the Security data panel: source dates, live/cache/fallback mode, update provenance and “What changed this week.” Newly added Wordfence advisories and newly listed KEV entries can receive “New this week” badges. That describes the data update, not when a problem first appeared on your site. The first published snapshot has no earlier generation to compare.

Missing data or data at least eight days old gets a warning. Read that warning before treating an empty advisory list as reassuring. An unavailable source stays a coverage limitation, not a pass.

Reading the report without getting buried

The progress bar follows six stages, from reading the page and declared assets to identifying versions, joining advisories and building the report. It shows counts and offers Cancel. Pending reads are not counted as completed work.

Start with the summary card. It counts open issues by severity, suggestions, known vulnerabilities, software needing attention, build flaws, exposed files and unknowns, then lists up to three actions. A count it did not measure shows "Not run" with a short reason instead of 0. When a site has no open issues, the actions come from the suggestions. We do not compress the Security Analyzer's result into a numeric safety grade.

Use the outcome filters to work through the report:

Scroll to compare columns and rows when the table extends beyond the box.

Filter What it means
Open issues We observed something to review, rated Critical, High, Medium or Low. Read the severity and evidence; not every issue is an exploitable vulnerability.
Suggestions A low stakes improvement, such as adding a CAA record or a permissions policy header. Worth doing, but not counted as an open issue.
Unknown The evidence, version, source or coverage was insufficient for a reliable answer. Investigate what is missing.
Pass This particular check passed within the measured sample. It does not clear the whole site.
Not applicable The check does not apply to the evidence or scope of this run.

Passing groups start collapsed. You can narrow further by severity, category, known CVE, active exploitation, new advisories or owner checks. Search for a component such as PHP, a CVE number or evidence text. Clear filters to return to the full report.

Each row starts with a plain explanation. Open issues and unknowns include what to do and where to look. Expand the evidence for the version confidence, measurement time and source details. Numbered citations lead to a reference list that distinguishes measured evidence from documentation and advisory links that were not themselves retrieved during that scan.

Download the plain English report or use the printable report to save a PDF. Both keep outcome labels, coverage and references. The AI fix prompt carries the actionable observations into a reviewable work request: confirm real versions, check vendor backports, make compatible changes, test and rerun the scan. Unknowns call for investigation, not invented repairs. The prompt does not authorize deployment, and you should review it before sharing it with an assistant.

What comparing the scanner with deeper audits changed

We compared the scanner's public observations with detailed audit findings and reviewed the disagreements. That exposed mistakes worth fixing before adding more checks:

  • Email checks could judge the wrong domain. They now preserve explicit mail domain scope and the relevant DNS answers.
  • A CAA alias could be mistaken for a certificate issuer authorization record. Aliases alone no longer earn a pass.
  • Two SPF policies could slip through a presence only check. The Security Analyzer now identifies duplicate SPF policies; we also verified that Mega's existing rejection of duplicates remains intact.
  • Ordinary JavaScript property names and expressions could resemble credentials. Those expressions no longer become secret alerts; literal credential patterns still receive scrutiny.
  • Certificate and TLS failures could be labelled as intentional access blocks. They now retain the actual transport limitation.

The Mega Analyzer shares these corrected checks and presents its compact security findings with the same outcome language. Its smaller sample does not include every standalone check. Historical audit comparisons helped us find defects; they are not a claim that the scanner catches every current vulnerability.

What a clean result cannot promise

A clean result is not proof of safety. This is a passive public sample, not an authenticated inventory, penetration test or source code review. It cannot see inactive plugins, private patches, account recovery settings, backup quality or every page on your site.

The collection limits include up to five declared scripts, two declared source maps and thirty additional target URLs shared across the optional checks. A declared WordPress theme stylesheet and feed can supply useful version evidence, but we do not read every theme or feed. Redirects and permitted fallback attempts are counted separately. Byte limits, missing versions, unavailable sources and skipped requests remain visible.

Use the report to start a specific conversation: “Is this the installed version, does this advisory apply, and can we verify the repair?” That is more useful than treating a green row as a guarantee or a red row as proof of a breach.

Fact check notes and sources

The October 31, 2026 descriptions remain tied to that release and its recorded acceptance results. The November 4, 2026 additions were checked against the new release results and the live companion pages on November 4, 2026 at 18:24 UTC. See the public security release changelog, the Security Analyzer scope and notices, Mega Analyzer and Agent Endpoint Inspector. Feed dates and observation times belong to each individual scan.

Related reading

This post is informational, not security consulting, legal or compliance advice. Third party names identify the sources; no affiliation is implied. Only scan sites you own or have permission to test.

← Back to Blog

Accessibility Options

Text Size
High Contrast
Reduce Motion
Reading Guide
Link Highlighting
Accessibility Statement

J.A. Watte is committed to ensuring digital accessibility for people with disabilities. This site conforms to WCAG 2.1 and 2.2 Level AA guidelines.

Measures Taken

  • Semantic HTML with proper heading hierarchy
  • ARIA labels and roles for interactive components
  • Color contrast ratios meeting WCAG AA (4.5:1)
  • Full keyboard navigation support
  • Skip navigation link
  • Visible focus indicators (3:1 contrast)
  • 44px minimum touch/click targets
  • Dark/light theme with system preference detection
  • Responsive design for all devices
  • Reduced motion support (CSS + toggle)
  • Text size customization (14px–20px)
  • Print stylesheet

Feedback

Contact: jwatte.com/contact

Full Accessibility Statement • Privacy Policy

Last updated: April 2026