Skip to main content

Business Domain and Email: What a Professional Website Really Needs

Website, business domain and professional email are separate services. See what a small business actually needs for a professional start.

Published: · Updated:

Business Domain and Email: What a Professional Website Really Needs © Velvionix
10 min read DE

Many businesses first look for a professional email address and treat website, domain and mailbox as one package. If later only the website needs to be connected to the existing domain, individual DNS records are enough. A blanket nameserver change, or one account that holds both mail and the website, often forces a mailbox migration or a DNS rollback afterward, even though the email service was meant to stay where it is.

A clean split is enough for the start. The website needs a domain. A mailbox on that domain is not required for that. A business address under the company’s own domain is still often the more professional path.

Key takeaways

Domain, website and email are technically separate building blocks.
A website needs a domain, but not necessarily a mailbox on that domain.
A business address under the company's own domain is useful for many firms.
Domain and mailbox stay with the customer.
Existing mail DNS records should not be changed without need when the website is connected.
Mailbox first-time setup and a contact form are optional extras.

Domain, website and email are three separate building blocks

The domain is the name under which the business is reachable on the web. The website comprises the content and the application that are accessible at this address. The mailbox is a separate service. It can use the same domain but is technically separate from the website.

Mixing the three often means buying a package too early or changing too much at once.

What a business domain does for the website

Without a domain there is no stable public address for go-live. The domain remains in the company’s own account and under its ownership. That matters later if hosting, technology or the service provider changes.

If a domain already exists, Velvionix connects the website through the DNS records the site needs. Nameservers do not have to be changed as a default. Migrating the website should not unnecessarily affect either ownership of the domain or the existing email service.

A short address built from the company’s own name is easy to recognize. With many website builders, the platform name remains part of the address. That name alone does not earn a better ranking. Whether the site is found depends on its content, structure and technical discoverability.

Does a website strictly need a mailbox on its domain?

No. A website can go live with the domain even if no mailbox has been set up on that domain yet. An existing email address is enough to register the domain.

A business address on the company’s own domain is still useful for many businesses. It separates business accounts from private accounts, creates a consistent professional presence and can later be used consistently in forms, the legal notice and everyday business correspondence. That is an organisational recommendation, not a technical requirement for go-live.

Business email under your own domain: what sits behind it

Putting an email address on the website is not enough while that address is not set up. Behind it there needs to be a mailbox at the company’s mail provider. The domain’s DNS records have to be in place so messages can arrive at that address and be sent from it.

Email authentication includes records such as SPF, DKIM and DMARC. They help protect the domain against spoofed sending. Entering the address alone, without finishing the technical setup, does not yet provide reliably working business email.

When domain and email already run

This is the common case: the domain exists, mail already works, the website comes later. Then only the DNS records the website needs should change.

MX, SPF, DKIM and DMARC stay untouched if the website connection does not need them. An unnecessary nameserver change can interrupt receiving and sending even though nobody wanted to move mail.

This separation is precisely what protects the existing email service. The website is connected. Mail stays where it is.

When no domain exists yet

Then the company registers the domain itself in its own account at a registrar of its choice. Velvionix can assist with selecting and purchasing the domain and then connect the website to it.

That help and the DNS connection belong to the Starter scope of 499 EUR net. The domain itself stays with the customer. Velvionix does not transfer the domain into an agency-owned account.

Where the contact form and email meet

A contact form is different from a visible email address with a mailto: link. The Velvionix extension processes the form on the server and sends the message through the customer’s email infrastructure.

The form is a separate extra. If a suitable business mailbox for the website or contact form already exists, its technical connection is part of the form extra. If the mailbox must first be created, that first-time setup stays a separate extra. The same SMTP connection is not charged separately again afterward.

What Velvionix takes on - and what stays with the customer

In the website project: domain connection, simple help with buying a domain if none exists yet, and the website itself.

Optional: mailbox first-time setup and a contact form.

Not as an ongoing website service: the mail-provider contract and ongoing mail administration.

Ongoing mail cost stays with the customer. Existing mailboxes are not migrated by default. Device setup is not part of the website delivery unless it was agreed as a separate extra.

You can find details about the Starter offer, ongoing support and extensions on the Website Pricing page.

Do not overhaul DNS without a specific reason

Do not change nameservers when only individual website DNS records are needed.
Do not change existing MX records when email already works.
Do not overwrite SPF, DKIM or DMARC records without a specific reason.
The domain and mailbox should stay in the customer's account.
Website hosting and email hosting are separate services.
A new website does not automatically require a new mail provider.
DNS changes should be documented and limited to what the website actually needs.

Frequently asked questions

Does a website need its own domain?

Yes. The website needs a domain for go-live. It remains in the customer's account and under the company's ownership.

Does the website strictly need a mailbox on its domain?

No. The website can go live without a mailbox on that domain. An existing email address is enough to register the domain. A business address under the company's own domain is still often useful.

Can my existing business email keep running?

Yes. When the website is connected, only the website DNS records that the site needs are changed. Existing email-related DNS records remain unchanged if they do not need to be modified for the website connection.

Who owns the domain after the website project?

The company. The domain stays in the customer account. Velvionix does not transfer the domain into an agency-owned account.

Is business-email setup included in Website Starter?

No. First-time setup of new business mailboxes is a separately commissioned one-off extra. Ongoing mail cost stays with the customer.

Does a contact form need its own mailbox?

A suitable business mailbox for the website or contact form is the appropriate solution. If it already exists, connecting it is part of the form extra. If it must first be created, that setup stays a separate extra.

Bring website, domain and technical foundations together cleanly

Velvionix connects the website to your existing domain or supports a professional start with a new domain. The process is on the website creation page. A mailbox and a contact form can be added separately if needed. Starter and extras are on website pricing.

Sources

Notice: The respective providers or operators are solely responsible for the content of external links.

  1. [1]
    ICANN : "Information for Domain Name Registrants"
    https://www.icann.org/registrants
  2. [2]
  3. [3]
  4. [4]
    Bundesamt für Sicherheit in der Informationstechnik : "BSI TR-03182: E-Mail-Authentifizierung"
    https://www.bsi.bund.de/dok/TR-03182
  5. [5]
    RFC Editor / IETF : "RFC 7208: Sender Policy Framework (SPF) for Authorizing Use of Domains in Email"
    https://www.rfc-editor.org/rfc/rfc7208.html
  6. [6]
    RFC Editor / IETF : "RFC 6376: DomainKeys Identified Mail (DKIM) Signatures"
    https://www.rfc-editor.org/rfc/rfc6376.html
  7. [7]
    RFC Editor / IETF : "RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)"
    https://www.rfc-editor.org/info/rfc7489/

Related Articles

Comments

No comments yet.

Be the first to comment!

Write a comment

To write a comment, please enable the comment function in your privacy settings.