What We’re About

“Managers can add value after technical peaks, as IT work often exceeds the scope of past education.”
“When dealing with difficult notifications, resolution must extend beyond support’s role as a sandbox.”
“Knowledge of IT standards can be effectively transferred through targeted training materials.”
“Web IDs are currently being developed; common names like ‘Peter Jansen’ are not unique identifiers.”
“The Netherlands could establish an expert group to tune global IT developments.”

Regarding Web Domain and Hosting Control:

The Dutch website en.internet.nl/ provides essential to-do points for responsible parties, based on publicly accessible technical tests of their systems.
Remark 1: Due to the broad range of test topics, a critical issue may result in only a minor deduction from an otherwise near-perfect score.
Remark 2: A closed server can still achieve a score of 61% for web and 70% for email, based solely on DNS configuration—despite being inaccessible.
Remark 3: Domain naming challenges may require a country-specific approach. While the technical tools exist, political awareness is crucial. This issue could be effectively addressed under the remit of the Ministry of General Affairs, as technical experts alone are unlikely to resolve it.
Remark 4: The current “Hall of Fame” model may need to evolve toward more future-proof methods, including testing with email-based user identification.
Remark 5: As in my own tools, I recommend adopting a four-column format that presents IPv4 and IPv6 results separately, rather than combining them.
Remark 6: Receiving and sending email depends on many factors. A score of 100% is misleading here.

Bridge the gap between detecting and resolving IT issues — with clarity and direction

1. Free Domain RDAP Lookup, including DNSSEC and Domain Whois (PHP/Python/JSON, since August 15, 2021) — rdap.hostingtool.nl/modeling_domain/
2. Free Server Header Lookup (PHP/XML, since January 14, 2022) — www.hostingtool.nl/server_headers/
3. Free Domain Control Register ® (PHP/JSON, since November 30, 2024) — www.domaincontrolregister.org/
4. Free Homepage Route Overview (PHP/Python, since February 26, 2025) — www.workingornot.org/
5. Free Security Header Overview (PHP/Python, since March 18, 2025) — securityheaders.hostingtool.org/
6. Free Hosting Lookup (PHP/Python/JSON, since May 6, 2025) — lookup.hostingtool.org/
7. For a future-proof way to look up IANA data (PHP/JSON, since June 21, 2025) — rdap.hostingtool.nl/modeling_tld/

The Need for Registry and RDAP Modernization at ICANN / IANA

PostgreSQL’s JSON and JSONB field types support semi-structured identifier string properties specific to TLDs, facilitating integration of data from multiple databases. However, the current RDAP vCard array address output lacks the structure needed to reliably write and clearly read address information. This is evident in the mixing of the country code and country name in the current output. In the Netherlands, searches by postal code are performed using an indexed table field. The nesting of an entity within another entity has introduced unnecessary complexity for both machine processing and human-readable display. RDAP’s physical structure for roles should ensure role-specific visibility.

Up-to-Date PostgreSQL Registry Table Definition (Since May 31, 2025):
Developed to replace legacy registry systems and support deployment on global RDAP servers, this schema represents a crucial upgrade to the RDAP protocol—enhancing data structure clarity and ensuring long-term maintainability.

For many ccTLDs (country code top-level domains) registry data management relies primarily on input from registrars. The lack of additional authoritative guidance can impact data completeness and accuracy, underscoring the need for automated and standardized processes.

Machine-Readable IANA Root Zone Data:
My IANA root zone data is in a renewed format, to be retrieved from a designated IANA server and relying on user activity logging—including from unidentified internet users—for issue resolution, the tool avoids unnecessary traffic, reduces system overhead, and supports traceable, efficient operations.

Concerning Allowed Legacy Behavior in the .nl Domain (Netherlands)

– External SIDN whistleblowing and also contacting the Netherlands Standardisation Forum;
– SIDN could fulfill the gTLD operational requirements for .amsterdam and .politie if adequately maintained;
– The .frl root zone for the province of Friesland is maintained in England and has been updated;
– Find a final stage ccTLD domain: https://www.catchtiger.com/nl/domeinnaam-veilingen/
or for gTLD: https://www.expireddomains.net/expired-domains/

Concerning Allowed Legacy Behavior in the .fr Domain (France)

Concerning Allowed Legacy Behavior in the .de Domain (Germany)

Recommended Actions for Strengthening Digital Governance in the Netherlands

1. Establish a Governing Board
Create an independent oversight body composed of experts responsible for supervising national digital activities, policies, and strategic direction—including oversight of the .nl domain and broader digital infrastructure management. These areas involve highly complex technical challenges that require specialized expertise beyond the capabilities of most stakeholders. The board would ensure transparency, resilience, and alignment with the public interest.

2. Avoid Appointing a Minister of Digital Affairs
While appointing a dedicated minister may seem like a logical step toward centralization, it risks politicizing a domain that should remain technically focused and multi-stakeholder driven. Effective oversight requires continuity, expertise, and agility—traits often constrained within conventional ministerial structures.

3. Leverage Existing Expertise through a Think Tank
Establish a dedicated think tank under the Ministry of General Affairs, which could be called Team Digitale Zaken. This team would consolidate digital governance expertise, advise across government ministries, and ensure a cohesive, forward-looking approach to national digital policy. It could also develop operational routines and institutional memory to effectively respond to digital disturbances or incidents. This embedded expertise would strengthen the government’s ability to manage crises with agility and technical precision.

4. Designate Team Digitale Zaken as ccTLD Manager (Long-Term Vision)
Position Team Digitale Zaken to be considered as a designated manager candidate for the .nl country code top-level domain (ccTLD). This transition would require close cooperation with ICANN, recognizing that any change in management must follow its formal global approval process.

About Dutch ccTLD and geoTLD Control:

  • While the Ministry of Economic Affairs provides a legal framework until November 21, 2029, this control remains primarily a policy objective. In practice, operational responsibility for the .nl domain lies with SIDN and is expected to remain there for the foreseeable future.
  • The update to reflect SIDN B.V. as the Backend Operator—effective January 1, 2023—remains pending in the IANA database. Although still necessary, this is regarded as a technical matter and constitutes a procedural update within the IANA framework, not requiring the development of new ICANN policy.
  • The .frl top-level domain is a sponsored TLD privately managed by FRLregistry B.V.

Ministry of General Affairs:

  • Govern IT under a Cabinet Office. And dismiss unnecessary advisory bodies.
    – UK’s Cabinet Office falls under the Ministry of General Affairs. If realized in NL: “Kabinetsbureau”.
    – UK’s Government Digital Service (GDS) operates hierarchically under the Cabinet Office;
  • Generate training material for further education from the European Cloud, which is in preparation.
    – The AWS GovCloud in the United States, is managed by Amazon.
    – Organizations using GovCloud must verify that all individuals with access to the environment are U.S. citizens.
    – GovCloud cannot be used by foreign nationals or organizations, even if they have legitimate access to other AWS services;
  • Work on a Dutch or EU Digital Service for generic application software related to DNS and registries.
    – Well-considered proposals, RFC and non-RFC, could feed the IANA organization.

Ministry of Economic Affairs:

  • Include automated task costs in just one annual web domain fee;
  • Include a change in a registrar’s own data in its period costs;
  • Eliminate all registry discounts. A volume discount causes unfair competition.

Ministry of the Interior and Ministry of Justice:

  • List areas of expertise, engage specialists, ensure dynamic interaction and make decisions;
  • Make the country of the real domain user leading for country-specific Web Domain Services (WDSs).
    – For the NL, the “Stichting Inlichtingenbureau” in Utrecht could assist for a new “Webdomeindienst”;
    – WDS register data officers are confirmed by his/her director in that country;
  • Maintain IT knowledge with a long-standing EU group of stakeholders;

NL / EU / US and including generic top-level domain zones:

  • Discuss global design and programming of Registration Data Access Protocol software.
    – Introduce in RDAP an emergency entity in order to formally organize backup to get access;
  • Generate web IDs that start with the ISO2 country code, for business entities and natural persons;
  • Plan verification of web domain users indexed by web ID, starting with modeling in RDAP like mine;
  • Use the developed Domain Control Register ®, based on the real web domain user.
    – Report regarding expired HTTPS, security.txt or DANE via email. Perhaps a DCR revenue model;
  • Get custom fields approved and listed for standardization in the dynamic RDAP protocol.
    – A simple data structure has been designed for the registry details;