Table of Contents
- What Are the GoDaddy SMTP Settings for Each Mailbox Platform?
- How Do I Identify Which Email Platform My GoDaddy Mailbox Uses?
- Which account signals should an administrator check?
- Which Port and Encryption Pair Should I Use?
- What Username and Password Does GoDaddy SMTP Need?
- Which password should be reset?
- Why Do Correct Microsoft 365 Settings Fail Through GoDaddy?
- Which checks separate transport from policy?
- How Do I Verify GoDaddy SMTP Settings with mailX?
- What is the testing sequence?
- How to verify it
- What Does Each GoDaddy SMTP Error Mean and How Do I Fix It?
- Which fixes belong in the application?
- Is the Legacy Relay Host Still Valid, and What Are the cPanel Sending Limits?
- What applies to cPanel-hosted mail?
- Which DNS and Setup Mistakes Break Outgoing Mail?
- Which common mistakes need separate checks?
- Frequently Asked Questions About GoDaddy SMTP
- Can port 25 be used with GoDaddy SMTP?
- Why does webmail work while the application's SMTP login fails?
- How long do DNS changes take to affect email settings?
- What changes when a mailbox moves from Titan to Microsoft 365?
Do not index
Do not index
For GoDaddy Professional Email powered by Titan and legacy Workspace Email, the outgoing server is smtpout.secureserver.net on port 465 with SSL, sign-in required, and the full mailbox address as the username; Workspace settings should be confirmed against the active plan. Microsoft 365 plans use smtp.office365.com on port 587 with STARTTLS instead.
Why can a correct mailbox password still fail? The same GoDaddy account can contain mailboxes on different platforms, and a correct password can't fix the wrong server or encryption mode.
Table of Contents
What Are the GoDaddy SMTP Settings for Each Mailbox Platform?How Do I Identify Which Email Platform My GoDaddy Mailbox Uses?Which account signals should an administrator check?Which Port and Encryption Pair Should I Use?What Username and Password Does GoDaddy SMTP Need?Which password should be reset?Why Do Correct Microsoft 365 Settings Fail Through GoDaddy?Which checks separate transport from policy?How Do I Verify GoDaddy SMTP Settings with mailX?What is the testing sequence?How to verify itWhat Does Each GoDaddy SMTP Error Mean and How Do I Fix It?Which fixes belong in the application?Is the Legacy Relay Host Still Valid, and What Are the cPanel Sending Limits?What applies to cPanel-hosted mail?Which DNS and Setup Mistakes Break Outgoing Mail?Which common mistakes need separate checks?Frequently Asked Questions About GoDaddy SMTPCan port 25 be used with GoDaddy SMTP?Why does webmail work while the application's SMTP login fails?How long do DNS changes take to affect email settings?What changes when a mailbox moves from Titan to Microsoft 365?
What Are the GoDaddy SMTP Settings for Each Mailbox Platform?
GoDaddy SMTP settings belong to the mailbox product, not the domain registrar. Professional Email powered by Titan uses the secureserver.net infrastructure, while Microsoft 365 uses Microsoft's outgoing service.
The table distinguishes current mailbox submission settings from legacy hosting relay settings. Rows marked confirm require account-specific verification before saving, particularly after a migration or product change.
GoDaddy's Microsoft 365 device setup documentation specifies smtp.office365.com, port 587, and STARTTLS. The other product-specific settings require the matching mailbox documentation, not an assumption based on the GoDaddy brand.
Plan, region, client support, and recent product changes can affect the applicable configuration. An application offering only an SSL checkbox may also interpret encryption differently from an application with separate implicit TLS and STARTTLS choices.
Website hosting and mailbox hosting may be separate purchases. Olivetree Marketing's guide to finding the right web host provides useful context when reviewing the website side of that arrangement, but the mailbox product still determines SMTP configuration.
How to verify it: Run a live SMTP connection check against the selected product's hostname. A reachable server is only the beginning, encryption and authenticated submission must also succeed.
How Do I Identify Which Email Platform My GoDaddy Mailbox Uses?
The mailbox's product name is the strongest configuration signal. A domain registered with GoDaddy doesn't establish that GoDaddy hosts its email, and an old application profile may retain settings from a previous provider.
GoDaddy's third-party SMTP instructions distinguish Titan's smtpout.secureserver.net with SSL on port 465 from cPanel-hosted mail and require outgoing sign-in with the complete mailbox address.

Which account signals should an administrator check?
- Open the Email & Office dashboard. Record the product attached to the specific mailbox, not just the subscriptions available in the account.
- Inspect the domain's MX records. Use mailX's MX Lookup to identify the currently published incoming service. Treat that as corroborating evidence, since migrations and external routing can complicate interpretation.
- Compare the sign-in destination. A Microsoft sign-in supports a Microsoft 365 identification. A cPanel or domain-hosted webmail interface supports a hosting-mail identification.
- Look up the provider profile. The SMTP Finder returns the outgoing hostname, ports, encryption choices, login guidance, and provider setup guide without requesting credentials.
- Resolve disagreements. If the dashboard and MX records disagree, confirm the intended mailbox product and migration state before editing the application.
How to verify it: Compare the dashboard product with the SMTP Finder result and published MX destination. Agreement provides a useful baseline. Disagreement calls for checking routing or migration status, not guessing passwords.
The platform determines the outgoing host and security profile before authentication begins.
Which Port and Encryption Pair Should I Use?
A supported port must be paired with its intended encryption mode. Selecting SSL and STARTTLS interchangeably can prevent the client from reaching authentication at all.
The message-submission RFC establishes port 587 for message submission rather than ordinary server-to-server delivery. The provider's product documentation determines whether that submission route is available for a particular mailbox.
With implicit TLS, the client starts the TLS handshake immediately. With STARTTLS, the client first establishes an SMTP session, requests the encryption upgrade, and sends credentials only after that upgrade succeeds.

For a product supporting both submission modes, STARTTLS works well when the application exposes it explicitly. Implicit TLS is appropriate when the client expects encryption from the first byte. Neither choice justifies disabling certificate validation.
How to verify it: Follow the diagnostic procedure to test port 587 and 465 connectivity, using only the ports supported by the mailbox product. Inspect the TLS negotiation, certificate validation, and authentication stage separately. A handshake failure isn't evidence of a bad password.
What Username and Password Does GoDaddy SMTP Need?
The SMTP username is the complete mailbox address, not the local part before the at-sign and not the GoDaddy account login. The password belongs to that mailbox.
GoDaddy's Titan client instructions document the full-address login and distinguish outgoing SMTP from incoming IMAP, including IMAP port 993 with SSL.
Which password should be reset?
If the mailbox password is unknown, reset that mailbox's password through the account dashboard. Resetting the GoDaddy account login won't necessarily change the credential used by an email application.
An application may maintain separate incoming and outgoing credentials. Correcting the incoming password alone won't repair an outdated password saved in the SMTP profile. Password managers and existing client profiles can also retain a previously valid credential.
For Microsoft 365, a password field doesn't establish that password-based SMTP authentication is permitted. The application must support the authentication method allowed by the organization.
How to verify it: Run the mailX SMTP test with the product's host and security profile, the full mailbox address, and the appropriate mailbox credential. A good result shows connection, encryption, and authentication succeeding in sequence. The checker doesn't store credentials, and a failure after successful TLS should be investigated as an identity or authentication-policy issue.
Why Do Correct Microsoft 365 Settings Fail Through GoDaddy?
Changing ports is often the wrong fix for a Microsoft 365 authentication rejection. An application can reach the correct endpoint and establish STARTTLS while the mailbox remains prohibited from using SMTP AUTH.
GoDaddy's Microsoft 365 server-settings guidance identifies smtp.office365.com on port 587 with STARTTLS. Those connection values don't override organization policies or enable authentication for an individual mailbox.
Which checks separate transport from policy?
- Resolve and connect. Confirm that the hostname resolves and the network permits an outbound connection.
- Complete STARTTLS. Require successful encryption and certificate validation before investigating credentials.
- Check the specific mailbox. Confirm that SMTP Authentication is enabled for the user, where the organization permits it.
- Check authentication compatibility. Review multi-factor authentication requirements and whether the application supports the currently permitted sign-in method.
Legacy printer and scanner workflows may require an app password under GoDaddy's documented account configuration. That route isn't universally available, and an app password can't bypass an organization's authentication restrictions.
Security-default changes deserve administrator review. Disabling a protective organization-wide policy just to make an old device send is a meaningful security trade-off, not a routine troubleshooting toggle.
The distinction between a subscription and a working client also matters outside SMTP. Blowfish Technology's discussion of why NASA's Outlook still broke offers broader operational context, not authority for changing mailbox security settings.
How to verify it: Follow the mailbox-specific workflow to verify Microsoft 365 SMTP with mailX. Re-test after an authorized authentication-policy change. If transport and STARTTLS succeed but authentication fails, investigate the mailbox policy, credential, and client compatibility rather than falling back to an unencrypted connection.
How Do I Verify GoDaddy SMTP Settings with mailX?
A useful SMTP test needs the outgoing hostname, port, encryption mode, full mailbox address, and appropriate password. Testing a hostname without authentication establishes reachability, not whether the application can submit mail.

What is the testing sequence?
- Open the diagnostic. Enter the outgoing server and supported port in the mailX SMTP test.
- Select the security mode. Match the mode to the mailbox product's documented port pairing.
- Provide authorized credentials. Use the complete address and password for a mailbox under the requester's control.
- Run and inspect. Read connection, encryption, and authentication results in that order.
- Change one setting at a time. Match the first failed stage to its likely cause before modifying the application.
The website, API, and MCP connection tests use the supplied password only to run the test. The password is redacted before the request is saved, and credentials aren't stored. Agents should obtain explicit confirmation before invoking a credentialed login check.
How to verify it
When sender and recipient addresses are explicitly supplied, the SMTP checker can also send a test message. Successful login alone doesn't prove that the service accepted a particular sender or recipient.
What Does Each GoDaddy SMTP Error Mean and How Do I Fix It?
An authentication rejection after successful TLS calls for different action than a timeout or handshake failure. Exact response wording varies by server, so the following strings are diagnostic patterns, not guaranteed GoDaddy responses.
GoDaddy's SMTP Authentication guidance confirms that SMTP Authentication may need enabling for the mailbox. An organization administrator may be required when the user cannot change that setting.
Which fixes belong in the application?
A missing authentication checkbox or incorrect security selection is usually a quick client-side correction. A disabled authentication policy, blocked outbound connection, or invalid hosting certificate requires access to the relevant administrative system.
For cPanel, a domain-based mail hostname is appropriate only when the certificate covers it. Replacing one mismatched hostname with another without checking the certificate won't solve the underlying problem.
How to verify it: Re-run the SMTP test after each change. Confirm that the previously failing stage now succeeds before returning to the application, then test submission using an authorized sender address.
Is the Legacy Relay Host Still Valid, and What Are the cPanel Sending Limits?
relay-hosting.secureserver.net is a legacy hosting relay, not a universal replacement for mailbox SMTP. Its presence in an old website configuration doesn't establish that a current Titan or Microsoft 365 mailbox should use it.
Legacy availability and permitted connection settings must be confirmed against the active hosting account's GoDaddy help documentation. Guessing a port or borrowing a mailbox password for an undocumented relay workflow can create a different failure rather than repair the original one.
What applies to cPanel-hosted mail?
GoDaddy's cPanel mail-client documentation lists a domain-based outgoing server with ports 465 or 587 and SSL/TLS, and documents 500 SMTP relays per hour for the cPanel account and a maximum of 500 relays per individual address per day.
Applications exceeding the documented allowances should use a dedicated transactional sending service rather than treating shared hosting SMTP as an unrestricted delivery channel. An application's retry behavior also matters, repeated retries won't remove a sending restriction.
How to verify it: Test each sending mailbox separately with mailX, then inspect actual message submission. A successful TCP connection doesn't prove that authentication, sender authorization, recipient acceptance, or message acceptance will succeed. A blocked address shouldn't be treated as evidence that every mailbox on the account is blocked.
Which DNS and Setup Mistakes Break Outgoing Mail?
Duplicate SPF records can break authentication even when SMTP login succeeds. SMTP authentication authorizes an application to use a server, while domain authentication helps recipients evaluate messages sent for the domain.
GoDaddy's Titan DNS instructions publish the following SPF value for the relevant product. It's a Titan-only reference, not a replacement for an existing policy authorizing additional sending services.
Which common mistakes need separate checks?
- Duplicate SPF policies. Separate records beginning with the SPF version marker can cause a permanent evaluation error. Merge legitimate senders into one effective policy, then check the published SPF policy.
- Excessive SPF lookups. SPF permits at most 10 DNS-querying terms during evaluation. Nested includes and redirects contribute to that budget, so merely counting visible includes isn't sufficient.
- Wrong DKIM selector. The selector used by the sender must identify the published key. The DKIM Checker can inspect a supplied selector and look for common selectors when it's unknown.
- Wrong record type. SPF and DMARC policies are TXT records. A CNAME isn't a substitute policy value. DKIM is different, provider-managed DKIM may legitimately use CNAME records.
Applications that add domain-based email need their own authentication requirements reviewed too. AgentStack's documentation on setting up email domains in AgentStack is relevant when that integration is part of the actual sending path, not as a reason to replace unrelated mailbox records.
How to verify it: Run the SPF and DKIM checks after saving changes. A good result shows one valid SPF policy within its lookup budget and a resolvable DKIM key for the actual sending selector.
The remaining setup mistakes are transport and credential issues: a wrong port/encryption pair prevents a secure session, while a missing required app password prevents a compatible legacy device from authenticating.
Frequently Asked Questions About GoDaddy SMTP
Can port 25 be used with GoDaddy SMTP?
Port 25 is primarily associated with server-to-server relay and is often restricted by networks or hosting providers. Ordinary mailbox submission should use the authenticated connection documented for the mailbox product. The port table distinguishes submission from relay, and legacy hosting relays require their own account-specific confirmation rather than assumptions.
Why does webmail work while the application's SMTP login fails?
Webmail doesn't exercise the same connection path as an external SMTP client. A working browser login establishes that the mailbox is accessible, but not that the application has the correct outgoing profile or permission to authenticate. Compare the application's server, security selection, full-address username, and authentication method with the mailbox product.
How long do DNS changes take to affect email settings?
DNS visibility depends on the previous record's time to live and resolver caching, so a change may take hours to appear consistently. A live SPF or DKIM lookup shows what the queried DNS path currently returns. Changing SMTP credentials is separate from DNS, and waiting won't repair an incorrect password or disabled authentication policy.
What changes when a mailbox moves from Titan to Microsoft 365?
The outgoing endpoint, submission security profile, incoming configuration, and permitted authentication workflow must all be reviewed. A partial edit can leave the application connecting to the new service with an old security or login method. Replace the complete account profile using the destination product's current documentation, then verify transport, authentication, and submission.
Run a free, no-signup check at mailX to separate a GoDaddy connection failure from an encryption, authentication, or DNS problem. mailX provides live diagnostics with plain-English fixes, so the next configuration change can address the failed stage rather than another guessed setting.
