Buy your .engineer domain today

.engineer is a natural fit for consulting engineers, structural and civil practices, mechanical and electrical designers, and individual specialists using their own name as the address.

It is also used across software engineering. The most visible site on the ending is ai.engineer, the conference and community series, which shows the word is not confined to licensed disciplines.

Yes, .engineer is an open generic top-level domain (TLD). No engineering license or professional credential is checked before the name is issued or afterwards.

ICANN classified engineering as open-entry when the extension was created, deliberately withholding the credential requirement it applied to endings like .lawyer and .doctor.

A .engineer domain sits alongside title-protection law rather than interacting with it, and no regulator anywhere has published guidance on domain names.

In most US states, in Canada and elsewhere, titles like Professional Engineer are reserved, and licensing acts usually specify how the word engineer may be used in a title. Enforcement varies between boards, and a federal court has held that describing yourself as an engineer outside a commercial engineering engagement can be protected speech.

What these rules govern is holding yourself out as an engineer when you offer or perform engineering services, not the characters after a dot. The practical step is to state your actual qualifications and registration number accurately on the page, and to check with your own board if you are unsure. None of this is legal advice.

Yes, a .engineer domain suits a consulting practice well, particularly a sole consultant or a named specialist, because the ending reads as a person rather than an institution.

One technical point: .engineer names must be at least two characters, so single-letter addresses do not exist. The short generic words went early, so a surname, a specialism or the two combined is the realistic route in.

.engineer reads as a person and .engineering reads as a discipline or a firm, which is usually enough to settle it. A sole consultant fits the first, a multi-discipline practice the second.

Both are open and neither verifies anything. They are run by different entities, so a name free on one is not necessarily free on the other; check both before deciding.

A .engineer domain gives no ranking advantage. Search engines treat newer endings the same as .com, so the word after the dot is not a ranking factor.

What it does is say what you do in the address itself, which helps a client scanning a shortlist or a signature block. Rankings still come from case studies, technical writing and the organizations that link to you.

A .engineer domain is inexpensive in its first year and renews at several times that, so budget on the standing rate rather than the introductory price.

Rates differ between registrars for the same name. Since a professional address is something you keep for years, compare renewals and consider a multi-year registration.

Yes, a .engineer domain supports custom email, so a consultant could use an address such as hello@ or projects@ on their own name.

For an independent practice this does quiet work, because a proposal from your own domain looks like a practice rather than a side project. Configure SPF, DKIM and DMARC so proposals and drawings are not filtered by a client's corporate mail system.

No, .engineer verifies nothing, and it is worth knowing that some professional endings do. That difference is a registry choice rather than an ICANN rule.

.law, for example, limits registration to a qualified lawyer or an authorized legal institution and checks the license against the regulator's records before issuing a name. No engineering extension does anything comparable.

The practical consequence is that the address proves nothing about your credentials to a visitor. If being chartered or licensed is part of why a client should hire you, publish the registration number on the page, because the ending will not say it for you.