Skip to content
EUID Audit service & seal, Home
DE
Get your website audited

This translation has not been editorially reviewed yet. The German version is authoritative. German version

Software currency

Libraries, visible version details and valid HTML, purely passive

Every subtopic leads to its checkpoints, every checkpoint to its article with explanation, examples and sources.

  • State of the art · GDPR Art. 32
  • 36 articles
Seal Implementation & technology

Subtopics

  • LibrariesIntegrated libraries with manufacturer maintenance instead of with maintenance end.1article
  • Versions are hiddenCMS, plugin and server versions are not in the source code and not in the headers.3articles
  • Valid HTMLThe source code passes W3C validation; Browsers don’t have to guess anything.1article

What is measured

This audit area rates from findings and measured values, not from a countable set of rules. That is why this page lists which signals are collected.

  • Detected system

    Which CMS or shop system is delivered and whether a version is visible to the outside – read from generator data, paths and headers.

  • Extensions

    Recognizable plugins and themes including version, as far as they result from the loaded files.

  • Libraries without producer maintenance

    Built-in front-end libraries that the manufacturer has discontinued maintenance — compared to the published end-oflife.date. Recognized from script paths and, where the library is bundled, from the version details it reveals at runtime. A proven fact, not a statement of vulnerability.

  • Visible versions in headers

    Version specifications in HTTP responses. They are not a hole, but they facilitate mass attribution.

  • Purely passive

    No scan, no login attempt, no additional retrieval – only what the page delivers anyway is evaluated.

Frequent questions about Software currency

Is this a security scan or penetration test?

No, definitely not. We do not try paths, do not look for configuration or backup files, do not try to log in and do not check for vulnerabilities. Only what the page delivers during normal retrieval is evaluated.

Are you telling me if my website is vulnerable?

No – and whoever claims this from a distance exceeds his data. We report two things: that an integrated library is no longer maintained by the manufacturer (a proven fact) and that versions are visible to the outside (which makes it easier for attackers to assign). Whether a concrete installation is vulnerable, only a view from the inside clarifies.

Why is a visible version number a problem at all?

It is not a hole, but an invitation: attackers search the web en masse for pages reporting a certain vulnerable version. Those who do not name their version do not appear in these lists. This does not replace an update — it reduces the attack surface.

What if you know nothing?

Then we say exactly that: “no system recognizable” – and expressly that this is not proof of a current state. An empty examination is never considered a carte blanche.

Does this audit area additionally burden my server?

No. It evaluates the same delivery that is retrieved for the indexing check anyway — not a single additional access.

Questions about the audit? See frequent questions

Good to know

  • Purely passive: no scan, no access, no additional access.
  • We report missing manufacturer care and visible versions — not vulnerability.
  • If nothing is recognized, this explicitly means "no proof" - no carte blanche.

To the service page “Software currency”

  • Seal Digitale Barrierefreiheit
  • Seal Daten & Recht
  • Seal Technische Qualität
  • Seal Digital Excellence
  • Seal Cyberversicherung

Audited. For a better digital future.euid.com