How to Apply for an .ac.uk Domain: Requirements and Steps

An .ac.uk domain is a restricted academic name, not a standard retail domain that any training business can buy through a checkout. Jisc manages the namespace and assesses eligibility and naming. Approval depends on the organisation and proposed name meeting the relevant policy.

An application needs the correct institutional route, eligibility evidence and technical owner. Begin with the institution’s IT or governance team and Jisc’s current domain registry guidance. Do not assume a hosting supplier is an approved .ac.uk registrar unless that status has been verified.

1. Confirm the institution’s eligibility

Read the current .ac.uk eligibility policy linked from Jisc’s domain registry page. It covers education, research and specified related organisations. The correct category must fit the applicant; describing a commercial course as educational does not automatically make its provider eligible.

Jisc distinguishes domain eligibility from connection to the Janet Network. Its current guidance includes routes for organisations connected to Janet and approved registrars acting for eligible organisations outside that connection. Do not use eligibility for one service as proof of eligibility for the other.

Prepare a short explanation identifying the relevant policy category and the evidence supporting it. If the organisation’s position is uncertain, ask through the official route before commissioning a public identity around the name.

2. Check the proposed name and its purpose

The organisation and the name both need consideration. Use a name that accurately relates to the institution, project or eligible purpose. Review acronyms, potential confusion and existing registrations. A lookup showing that a string is unused is not an approval decision.

For a project spanning institutions, identify who is responsible and how the project meets the policy. A new standalone domain may not be necessary when an appropriate subdomain of an existing institutional name would serve the task. Agree that choice with the institution rather than creating an independent identity informally.

Keep a written approval of the exact spelling. Domain migrations can affect email, research references and public links, so a name decision should include the people responsible for those dependencies.

3. Use the correct application route

Jisc’s domain registry guidance says requests are accepted through approved registrars unless the organisation is currently connected to Janet. Jisc members and approved registrars use the registry portal for relevant requests. Follow the current access instructions published by Jisc.

If an approved registrar is applying, agree who supplies the evidence and who responds to questions. If the institution uses its Janet route, work through its authorised technical contacts. Avoid sending an application to an unrelated hosting sales mailbox and assuming it reaches the naming process.

Keep domain registration separate from website hosting. An institution may choose appropriate hosting for its public pages after the registration route is established, subject to its own procurement, security and data requirements.

4. Prepare evidence and authorised contacts

Use the current form or portal requirements rather than a copied letter addressed to another country’s registry. The application should explain the applicant, the proposed name, the eligibility basis and the intended use. Supply the evidence requested for the actual category.

Identify an authorised institutional contact and a technical contact. Use stable organisational details and a contact route that works before the new domain is active. Keep a record of who can approve naming, DNS and later changes, so the application does not depend on one temporary project member.

Where a consortium or research project is involved, explain the participating organisations and governance. Supply supporting information through the approved channel and limit personal information to what is required. Do not attach student records or unrelated identity material to make an application appear more substantial.

5. Confirm fees and wait for an actual decision

Ask Jisc or the approved registrar to confirm the charges and renewal arrangement for the specific membership and application route. Distinguish registry administration from registrar services, DNS and hosting. Jisc’s public page describes several service categories, so one isolated fee should not be presented as universal.

Retain the submitted version, reference and correspondence. Respond to requests for clarification with consistent evidence. Payment or a supplier’s order acknowledgement does not establish that Jisc has approved the name.

Plan a launch with room for review and technical setup. Use the actual review process and the completeness of the application to plan timing. If the request is refused, obtain the reason and review a suitable alternative without publishing a name you do not control.

6. Prepare DNS, certificates and services

After approval, confirm the registration and authoritative DNS arrangements. Prepare the records required for the public website, mail and verification services. A delegated domain does not automatically include a finished website, mailbox or learning platform.

Keep a recoverable record of the zone and coordinate changes with the technical owner. Configure certificates for the names actually used and test from outside the institution’s own network. Check both web and mail where they are part of the launch.

If moving an existing site, map old URLs and plan redirects. Preserve research links, publications and account-recovery dependencies. Avoid running two unsynchronised copies of a transactional application while DNS answers are changing.

7. Maintain governance after launch

Record the registrant, registrar or Jisc route, authorised contacts and technical owner. Protect access and establish a handover process when staff or project roles change. A domain can remain important long after the original website project ends.

Monitor the applicable renewal and continued-eligibility arrangements. If the organisation or project changes, review the policy and notify the responsible service where required. Do not assume approval remains unaffected by every later change in purpose or status.

Give content and accessibility responsibilities named owners. Public academic pages should be accurate and usable; applications handling personal information need the appropriate security and privacy review. The extension does not certify every service placed beneath it.

Protect existing references during a change

Academic names can appear in publications, research repositories, partner systems and long-lived email addresses. Inventory those references before adopting a new domain. Identify which can be updated and which need a lasting redirect or contact plan.

Coordinate the announcement with technical validation. Test a sample of old links, downloads and external references after cutover. Keep a named owner for remaining corrections so the institution does not lose useful access simply because the new homepage is working.

A useful internal application brief

Before completing the official process, assemble a concise internal record covering these points. This is a preparation checklist, not a substitute application or a guarantee of acceptance.

A well-prepared .ac.uk request explains why the institution and name qualify, then connects approval with careful technical administration. Start from Jisc’s current guidance and retain institutional control throughout the process. That gives the resulting name a dependable foundation for the services and publications it will support.