Dragon Domain Manager, its demonstration environment, the future .UK EPP testbed, OT&E and production serve different purposes. Before following a technical instruction, identify both the interface and the environment it describes. A portal demonstration can help a colleague learn a workflow without proving that your registration software is ready for production.
Environment status at the source review
The following is a documentation review dated 3 November 2026, not a live availability monitor. The specific .UK testbed documentation says the future EPP testbed is available and OT&E has not yet launched. The dedicated Dragon demonstration page says signup is open.
| Environment or interface | Purpose | Availability described by the source | Nature of data | Official access guidance | Checked |
|---|---|---|---|---|---|
| Current .UK Web Domain Manager | Manage current production registrations through the web interface | Current legacy service | Real registrations; actions can affect customers | Legacy .UK resources | 3 Nov 2026 |
| Dragon demonstration | Learn the new portal's workflows | Signup open | .ukdemo demonstration objects; limited functions |
Demo instructions | 3 Nov 2026 |
| Future .UK EPP testbed | Exercise future integration behaviour | Available | Fictional test data, reset daily | Specific testbed guide | 3 Nov 2026 |
| Future .UK OT&E | A production-aligned integration test environment when launched | Not yet launched according to the .UK-specific page | Test data, not a copy of live domain objects | OT&E status | 3 Nov 2026 |
| Current production EPP | Operate the live legacy .UK registry | Current platform | Real registrations | Current .UK reference | 3 Nov 2026 |
| Future production platform | Operate .UK after the confirmed transition | Scheduled, not current .UK production | Real registrations after migration | Future-state reference | 3 Nov 2026 |
Access should be arranged through the official Nominet channels. DomainSabre does not collect Nominet credentials, provide a proxy login or connect to your registrar account.
What the Dragon demonstration is useful for
Use the demonstration to examine where a task starts, which fields staff must understand and what a completion screen actually establishes. A support colleague can practise distinguishing a domain record from its contact and host information, or identify which parts of an existing training note require revision.
The dedicated demo page describes a restricted .ukdemo environment and explicitly separates it from the EPP OT&E/testbed link. It also lists functions that are outside the demonstration. If a button or scenario is absent, record the limit rather than filling the gap with an assumption about production behaviour.
A useful training record states the task, environment, result and unresolved question. “Logged into Dragon successfully” is a narrow result. It does not demonstrate customer authorisation, correct renewal handling or an end-to-end integration test.
What to test in the future EPP testbed
Select scenarios from the operations your software actually uses. The official test data includes fictional records in different states. Because the data resets, retain the observation time and the fixture identity when investigating a result; do not expect yesterday's changed object to persist indefinitely.
Prepare a test-data strategy that keeps live customer information and credentials out of a demonstration exercise. Verify the configured endpoint, accreditation and authentication method before sending commands. The EPP preparation guide provides a printable evidence table and a way to separate expected behaviour from observed behaviour.
Why a documented endpoint is not an availability announcement
Nominet's general session documentation describes the purposes and naming conventions of testbed, OT&E and production across its platform. The general EPP index also contains older transitional wording. Neither should override a more specific current .UK notice about actual availability or the formal transition date.
For this reason, the table above uses the dedicated .UK environment pages. If two current sources appear to disagree, record the conflict and seek clarification before changing an operational dependency. Do not infer that an environment is ready merely because its hostname can be constructed from a naming pattern.
A practical handover between teams
Fictional example: a support team completes a Dragon demo exercise while an engineering team completes a future-testbed transfer scenario. They record separate results. The support record explains the customer-facing steps and help-page changes; the engineering record captures the request, response, state and environment.
Before live use, both teams reconcile their instructions against the confirmed production process. This prevents a demonstration shortcut, a missing feature or fictional data assumption from becoming a customer instruction. Business approval of the procedure remains a separate responsibility.
Before moving towards production
Use the readiness checklist to check who owns the remaining work. Follow the transition checks for pending operations and reconciliation. Return to the standardisation hub for the applicable date and current-state explanation.
Keep a clear boundary between preparation and activation: a reviewed interface, successful test and published future policy are useful evidence, but each answers a different question.