Punktum dk’s sandbox environment is a test environment where integrations can be developed and tested without affecting real .dk domain names or production data. The environment can be used to test technical flows, system changes, and new versions of Punktum dk’s services.
The full technical specification for the sandbox environment is available on Punktum dk’s GitHub.
What is the sandbox environment?
The sandbox environment is a separate test version of Punktum dk’s technical services. It is isolated from the production environment and makes it possible to test integrations in a controlled environment.
The environment supports several of Punktum dk’s services, including EPP, DAS, the Registrar Portal, and WHOIS. This means that key parts of a technical integration can be tested before they are used in production.
Why is the sandbox environment important?
The sandbox environment makes it possible to develop and troubleshoot integrations safely before they go live. This reduces the risk of errors affecting real .dk domain names and makes it easier to validate that the relevant flows are handled correctly in the integrated systems.
This is particularly important when developing EPP integrations, where registration, changes, transfers, and other automated actions need to work reliably.
For major updates, including XSD updates, changes are released in the sandbox environment first. This provides an opportunity to test and adapt the integration before the changes are deployed to the production environment. As a general rule, XSD updates are released to production three months after they are made available in the sandbox environment.
What can the sandbox environment be used for?
The sandbox environment can be used for the development, testing, and validation of technical integrations. This includes:
- developing and testing EPP clients
- testing registration and transfer flows
- testing contact and verification flows
- validating system changes
- testing new service versions before production
The sandbox environment should therefore be a natural part of both onboarding and ongoing integration maintenance.
Testing before production
The sandbox environment is separate from the production environment. Actions performed in the sandbox therefore do not affect real .dk domain names or production data.
The environment can be used to develop and test integrations before they are used in production. This includes testing EPP clients, domain registration, name server management, and the handling of poll messages.
Any service-specific considerations are described in the technical specification on GitHub.
