Web Tools

Actionable Screenshots. Resolution of Identified Issues. Management-Ready Post-Mortem Reviews.
Tools and research supporting digital trust, internet governance, authoritative data structures, and operational accountability.

  1. Sharing Cloud and Hosting Knowledge (since November 3, 2018) — webhostingtech.nl
  2. Domain Relationships, WHOIS and DNSSEC Analysis (since August 15, 2021) — relationships.hostingtool.nl/domain
  3. Testing Email Reception from a Forged Sender (PHP/SMTP, since June 25, 2022) — not publicly available
  4. Web Control (Ubuntu, Docker, Django, Python, PostgreSQL, since November 30, 2024) — control.hostingtool.org
  5. 16 Native / Cross-path Homepage Paths (PHP/Python, since February 26, 2025) — www.workingornot.org
  6. Security Header Overview (PHP/Python, since March 18, 2025) — securityheaders.hostingtool.org
  7. Native Hosting Lookup (PHP/Python, since May 6, 2025) — lookup.hostingtool.org
  8. Registry Structure (PostgreSQL, since May 16, 2025) — github.com/janwillemstegink/relationships.hostingtool.nl
  9. Top-Level Domain Structure (PHP/JSON, since June 21, 2025) — relationships.hostingtool.nl/tld
  10. Inbound Mail Flow Analysis (PHP/Python, since March 2, 2026) — analyzemx.hostingtool.org
  11. TLS Cryptographic Analysis (PHP/Python, since March 2, 2026) — analyzetls.hostingtool.org
  12. State of EU Top-Level Domains (since June 5, 2026) — analyzetlds.hostingtool.org
  13. Structured Subjects for History, PKI, E-Wallets and Alternate Handling (since June 11, 2026) — analyzesubject.hostingtool.org
  14. Self-Explanatory RDAP (since June 18, 2026) — janwillemstegink.nl/self-explanatory-rdap
  15. Browser and Mail Client Readiness (since July 6, 2026) — clientreadiness.hostingtool.org
  16. Multifold Control (Ubuntu, Docker, Django, Python, PostgreSQL, since September 8, 2026) — multifold.hostingtool.org

Internet.nl – Structural Observations and Multifold Testing

The Dutch website Internet.nl (en.internet.nl), built with Django, provides valuable technical findings and actionable information for responsible parties. Nevertheless, several structural and conceptual aspects merit further consideration.

A central principle of Multifold testing is to preserve technically distinct service paths throughout testing, storage, interpretation, and reporting, rather than reducing their findings to a single aggregate score. This enables technical problems to be assessed individually and followed through to resolution.

  1. Limitations of aggregate scoring — Internet.nl covers a broad range of technical standards. Consequently, a serious failure in one area may result in only a limited deduction from an otherwise high overall score. This can obscure operationally significant problems behind near-perfect percentages.
  2. Unreachable services can still receive substantial scores — Web or mail services that are closed or unreachable may still receive scores of approximately 61% for web or 70% for email, based on DNS-related findings, even when the actual service is unusable.
  3. Time-outs should be treated as hard failures — Although time-outs may reflect temporary conditions, they establish that a service could not be reached or assessed successfully at the time of testing. Such findings should not be treated as satisfactory outcomes merely because their underlying cause remains uncertain.
  4. Domain holder identification requires more than technical checks — Verification of domain registration holder names depends on country-specific registration policies and legal frameworks. Although many technical building blocks already exist, meaningful progress requires regulatory and institutional alignment.
  5. Reconsidering Hall of Fame criteria — The Hall of Fame provides recognition for successful technical compliance. Its long-term value could be strengthened by incorporating additional criteria for verified ownership or operational control, potentially supported by email-based identification.
  6. Email scores do not establish end-to-end reliability — Email delivery and reception depend on external systems, configurations, policies, and operational conditions. A 100% test score therefore does not guarantee successful real-world mail exchange.
  7. Public visibility of (sub)domain results — Publishing successful test results for domains and subdomains may expose contact or infrastructure information to unwanted attention. The purpose, necessity, and consequences of public presentation should therefore be considered carefully.
  8. Multifold testing and management-oriented reporting — My approach extends Internet.nl measurements by preserving individual findings and action points across IPv4, IPv6, www, and non-www service paths. This supports targeted remediation, operational accountability, independent assessment, and management-ready reporting. — Multifold Control

Notes

  1. Scope of observations — These observations primarily concern structural, conceptual, and organizational aspects rather than implementation details.
  2. Management assessment and follow-up — Responsible management should be able to explain how reported results have been independently assessed, including through sample-based verification, and how identified shortcomings are assigned, addressed, and subsequently verified.