The story of Scanapse

• The XML remains a standard sitemap but is directly readable in browsers through a local CSS stylesheet without XSLT
• Logo, FR/EN markers, dates, frequencies and priorities are presented without JavaScript or third-party resources

• Indexable public pages expose a WebSite, Organization and WebPage JSON-LD graph
• HSTS preload is not automatically enabled: this remains conditional on prior verification of every subdomain

• Engine, GPTO, 2026.09.4 patterns and MariaDB schema 2.3.1 unchanged; no SQL migration

• The XML sitemap is generated from a single public route catalog and no longer duplicates a hard-coded list
• Each FR and EN URL keeps its hreflang alternatives and receives a lastmod calculated from source files
• A local sitemap.xsl stylesheet displays the Scanapse logo and a readable view without changing XML semantics

• FR/EN routing, LLM files, engine, GPTO, 2026.09.4 patterns and MariaDB schema 2.3.1 unchanged
• No SQL migration required

• English public routes use /en while French remains canonical at the root
• Legacy ?lang= URLs redirect to localized equivalents without relying on browser language
• Canonical, fr/en/x-default hreflang, Open Graph and sitemap share the same URL topology

• Added llms.txt, llms-full.txt, ai.txt and updated humans.txt
• robots.txt allows public discovery and expresses training opt-out where dedicated crawler tokens exist
• No change to the engine, 2026.09.4 patterns or MariaDB schema 2.3.1

• Sections across the eight editorial pages now use a dedicated namespace that no longer inherits the legacy Editorial grid from main.css
• Contact, Our approach, Read a domain, Records, Security, Privacy, Legal notice and History regain normal width and coherent columns
• The assets/css/editorial.css stylesheet remains separate from the homepage and report to keep future iterations safe

• Homepage, report, engine, 2026.09.4 patterns and MariaDB schema 2.3.1 unchanged
• No SQL migration required

• Priority items, legal context, useful texts and changes are grouped in a compact responsive grid
• Visible relations and open questions are brought together in a shorter complementary reading
• The domain and main title use more available width to avoid fragmented headings

• Headings, introductions and navigation revised with simpler explanatory wording
• The History page remains at /changelog and returns to the footer without returning to the header
• Homepage enriched with a mini dossier example so a former empty area becomes useful explanation
• Engine, 2026.09.4 patterns and MariaDB schema 2.3.1 unchanged

• Read a domain, Records, Our approach, Contact, Security, Privacy, Legal notice and History now use their own editorial compositions
• A dedicated editorial stylesheet isolates these pages from the homepage and report for safer future UX iterations
• The legal notice identifies Scanapse as a service operated by Koperateur Consulting, Mehdi Kachouri as service manager and publication director, and Infomaniak as hosting provider
• SEO metadata, introductions and headings are rewritten with descriptive language and no keyword stuffing

• Simplified public navigation: Read a domain, Records and Our approach
• Stronger domain identity in reports, more compact headings and empty states hidden when they add no value
• Public trajectory limited to useful changes, with volatile values such as CSP nonces normalised

• Evidence-only JSON export and evidence-only print mode
• Source icons added to evidence cards
• Engine, 2026.09.4 pattern and MariaDB schema 2.3.1 unchanged

• New S monogram built from traces, nodes and reading markers
• Observe · Connect · Understand baseline moved below the logo
• Favicon aligned with the new mark and teal, copper and violet palette

• Homepage and report enriched with constellation motifs, stronger hierarchy and functional accents
• Twelve angles retained with stronger identity without exposing more technical detail
• Evidence-first engine and MariaDB schema 2.3.1 unchanged

• The public report now follows Understand, Jurisdiction, Regulation, 12 knowledge angles and Evidence
• Technical counters become secondary information and are never presented as a global score
• Detailed evidence and technical metadata are collapsed by default to preserve progressive reading

• Public jurisdiction uses Established, Probable or To confirm states and shows reasons and limitations
• Regulatory texts are linked to observed context with relevance levels and official sources
• Scanapse produces no automatic compliance, certification or illegality verdict from an external scan

• The twelve 2.3.1 engine mappings remain unchanged but become twelve public knowledge angles
• Each angle has a distinctive SVG symbol, knowledge state, evolution and Why, How, Purpose and Limitations explanation
• The engine, rulepacks and fine-grained correlation mechanisms remain server-side

• Short header baseline replaces the version badge
• Stronger color accents while keeping light, dark and system themes
• SVG markers added to the twelve pillars with visual continuity in detail panels

• New utility-first hero with immediate scan control and knowledge-record preview
• Simplified header with direct access to Scan, Observatory, Methodology, Changelog and Contact
• Footer reorganised around product, method, resources and ecosystem

• The canonical 2.3.1 twelve pillars are shown directly on the homepage with their business question
• Statistics and latest observations remain MariaDB-backed and no demonstration number is fabricated
• No global security, trust, sovereignty or compliance score is added

• Mobile-first layout with progressive pillar grid and observation table transformed into cards on small screens
• Burger menu, keyboard focus, light/dark/system themes and progressive disclosure remain available

• Twelve fixed pillars separate public synthesis from technical collection modules
• Each pillar provides a plain explanation, associated observations, and technical details on demand
• Previous technical indicators remain available through progressive disclosure and no longer dominate the reading

• Pillar definitions, mappings, snapshots, and evidence links are persisted additively
• Every new scan produces exactly twelve snapshots, including unknown or untested states
• Source evidence remains authoritative and lack of evidence never becomes a favorable result

• GPTO can inspect definitions, mappings, and snapshots and preview the projection without modifying evidence
• The 2.3.0 to 2.3.1 migration is additive and can be imported with phpMyAdmin on Infomaniak shared hosting

• Each scan keeps its timestamp, target, trigger, engine and rule versions, coverage, and relationship to the previous measurement
• The GPTO watchlist is the only source of automatic rescans and the scheduler uses idempotent leased jobs
• Shared-hosting WebCron calls only /gpto/cron with dedicated authentication

• Declarative rulepacks can be encrypted in MariaDB with the key kept outside the database and public release
• No PHP, SQL, eval, or arbitrary network call can be supplied by a rulepack
• Public signals expose the conclusion and useful evidence without distributing private conditions

• GPTO shows the real MariaDB version, detected schema, critical tables and indexes, and a rollback transaction probe
• Public headings use natural line wrapping instead of forced one or two word fragments
• Statistics and history use 2.3 scan_runs as the primary operational memory

• Server-side URL normalization to a versioned canonical target
• Measured and versioned scan phases
• MariaDB becomes operational memory for targets, runs, changes, signals and knowledge
• Deep Scan remains reserved for 2.5 at the latest and is not enabled implicitly

Administration and knowledge

• GPTO without raw IP, persistent User-Agent, or fingerprint
• MariaDB 10.11 for metrics, messages, KM, and administration
• System, light and dark themes plus progressive explanatory reporting

Interface and method

• Intelligent dashboard with essential and expert views
• Evidence cards with method, source, reliability, and limitations
• Explanatory standards and regulatory context without compliance verdicts

Security and deployment

• Fixes the 421 Misdirected Request before local configuration is present
• Allowlist limited to scanapse.com, www.scanapse.com, almouatin.com, and www.almouatin.com
• The MariaDB schema and Evidence-first methodology remain at 2.0.0

Knowledge

• Seven explicit epistemic states, including unknown, contradictory, and untested
• Observed quality and knowledge coverage separated in the Trust Profile
• No lack of evidence automatically produces a favorable result

Monitoring

• Temporal comparison of observations with appeared, disappeared, modified, stable, or unresolved changes
• Constellation refocused on coverage, signals, unknowns, visible providers, and changes

Database and security

• Additive MariaDB 2.0.0 schema and backfill without fabricating V2 data
• Production Host allowlist, explicit HSTS, and release guard against secrets

Database

• Unique SQL parameters compatible with native MariaDB prepared statements
• Verified transactional writes for domains, reports, and dependencies
• doctor, probe, and import-files commands to verify and synchronise the database

Interface

• Return to the stable main stylesheet and isolation of telemetry, ranking, and module components
• One public result per domain, with the latest scan and total measurement count

Homepage and rankings

• Engine telemetry with indexed domains, archived scans, recent activity, best score, coverage, and visible dependencies
• Public ranking with three configurable bands: 90 to 100, 50 to 89, and 0 to 49
• Latest scan ledger with score, coverage, dependencies, change, and date
• Counters use MariaDB when available and keep signed file storage as fallback

Module catalogue

• New detailed page for all twelve modules, their signals, outputs, and affected indices
• Presentation of the collection, qualification, correlation, and reporting pipeline
• Security boundaries, network budget, and extension contract documented

Engine accuracy

• Public detection rule version: 2026.08.2
• Resources quoted in code samples or JavaScript strings no longer become fake dependencies
• Third-party WordPress, Drupal, and Joomla paths no longer suffice to attribute the technology to the scanned domain
• An isolated quoted challenge marker no longer suffices to classify a page as an active protection
• Conservative validation and normalisation of Set-Cookie lines

Validation

• Expanded regression tests for rankings, telemetry, modules, and false positives
• Typography convention automatically checked with the standard hyphen

MariaDB fixes

• Separated SQL session statements to avoid a PDO connection syntax error
• Explicit schema version check before any read or write
• Safe diagnostic codes for missing driver, host, authentication, rights, schema, and timeout issues
• New php bin/database.php doctor command without credential disclosure

Service continuity

• Signed file mode remains operational when MariaDB is expected but unavailable
• Blocking scans now requires the explicit block_on_failure option
• Health output distinguishes connection, schema, degraded mode, and blocking

Security

• No SQL secret is displayed by diagnostic commands or the health route
• The database remains protected by prepared queries and a least-privilege application account

Rankings

• Always-visible homepage table with controlled signals, trust to consolidate, and insufficient visibility
• Ranking based on Trust Index and coverage level, with history and change
• /classement and /ranking aliases to the Constellation page

Data

• Versioned MariaDB schema for domains, reports, dependencies, and migrations
• Hybrid file and MariaDB mode with automatic fallback when the optional database is unavailable
• Command to import existing signed JSON reports into MariaDB
• Optional manual domain band and public hiding without modifying the signed report

Accuracy

• Public detection rule version: 2026.08.1
• Technology detection based on resource paths, attributes, and runtime markers
• Remote protection detection weighted by structural evidence
• Sensitive cookie names recognised through complete tokens instead of generic fragments
• Removed false Fastly attribution caused by a generic Varnish header

Security and validation

• Prepared SQL parameters, schema constraints, validated prefix, least-privilege SQL account, and optional TLS
• Required MariaDB mode writes to the database before publishing the file report, and public health output hides detailed SQL errors
• Engine and rule version retained in every report and MariaDB row
• Regression tests added for false positives, rankings, hybrid storage, and titles
• Uniform typography convention using the standard hyphen throughout the project

New

• Constellation page with filters, SVG map, reading bands, and latest signals
• Enriched domain history with Trust Index curve, deltas, and snapshots
• Bilingual Changelog page powered by a structured source
• Latest-report preview on the homepage

Engine

• Two additional modules: third-party resource control and email trust
• SRI, mixed content, form destinations, iframes, and new-tab link measurement
• DNS reading extended to TLS-RPT, MTA-STS, and BIMI when email is advertised
• Report schema 1.3 and rebalanced category calculation

Security and quality

• The Constellation only publishes minimised summaries and never raw evidence
• Configurable exclusion of domains from the public wall
• Tests added for new modules, history, and public aggregation

Fixes

• Removed the conflict between the module directory and the public /modules route
• Secure cURL-to-socket transport fallback
• DNS, TLS, and HTTP errors converted into partial or minimal coverage