# Titan Mail SMTP settings for a website contact form > Titan Mail SMTP settings for website forms: smtp.titan.email on 465 or 587, turning on third-party access, the EU and GoDaddy servers, and Titan’s send limits. Source: https://formsmtp.com/guides/titan-email-smtp · Last updated November 2, 2026 ## Use the right server for where you bought Titan | Where your Titan mailbox comes from | SMTP host | | --- | --- | | Most providers | `smtp.titan.email` | | Blacknight, MonoVM, DomainDiscount24, Fluccs or Domain Central (EU-hosted) | `smtp0101.titan.email` | | GoDaddy (Professional Email powered by Titan) | `smtpout.secureserver.net`; see the [GoDaddy guide](https://formsmtp.com/guides/godaddy-email-smtp) | ## 1. Turn on third-party access Titan blocks outside apps until you allow them, and FormSMTP counts as one. In Titan Webmail, click the *Settings* icon, choose **Enable Titan on Other Apps**, and confirm with the button at the end of the short tour. If you see *Configure 3rd party apps* instead, it’s already on. ## 2. Use an app password if you have 2FA With two-factor authentication on, your normal password won’t work for SMTP. Create an application password in Titan and use it below. ## 3. Create the FormSMTP project [Sign up free](https://app.formsmtp.com/#/signup) and add a project. There’s no Titan preset in the provider list, so leave it on *Custom* and type the host and port below. ## 4. Enter the settings | | | | --- | --- | | Provider | Custom | | Host | `smtp.titan.email` (or the host from the table above) | | Port | `465` with SSL on, or `587` with SSL off (STARTTLS) | | Username | Your full Titan email address | | Password | Your mailbox password, or an app password with 2FA | | From email | The same address | Click *Test connection*, then add your form. See the [HTML contact form guide](https://formsmtp.com/guides/html-contact-form), or compare every provider on the [SMTP settings page](https://formsmtp.com/smtp-settings). Titan blocks the connecting IP address after repeated failed sign-ins. Double-check the password and third-party access before you test again. ## Titan sending limits Titan counts each recipient as one email, and limits mail to other domains by plan: | Plan | To other domains | | --- | --- | | Free, and Pro or Premium trials | 50 an hour, 100 a day | | Starter | 50 an hour, 300 a day | | Pro | 200 an hour, 500 a day | | Premium | 300 an hour, 1,000 a day | | Ultra | 500 an hour, 2,000 a day | Mail to addresses on your own domain has a higher limit: 1,000 an hour and 2,000 a day on every plan. A contact form that emails `you@yourdomain.com` from `website@yourdomain.com` counts as same-domain mail. Domains new to Titan start with lower limits that rise as they build a sending history. ## Check SPF and DKIM before you go live Titan checks your domain’s DNS before it sends. If the SPF record is missing or doesn’t include Titan, it rejects the message outright rather than letting it land in spam, and a broken DKIM record is rejected too. Copy both records exactly as Titan’s control panel shows them, keep a single SPF record per domain, and allow up to six hours for a DKIM change to be picked up. Then send a test from FormSMTP and check the message headers in your inbox. ## Common errors - **Authentication failed:** third-party access is off, or 2FA is on and you need an app password. Also check the server matches where you bought Titan. - **553 5.7.1 Sender address rejected: not owned by user:** the From address isn’t the mailbox you signed in with. Use the same address. - **550 5.4.6 Recipient address rejected: Sender Hourly Quota Exceeded:** you reached your plan’s hourly limit (there’s a daily version too). Sending resumes when the window resets. - **550 5.7.5 Sender address rejected: SPF Record for your domain is not set up:** add the SPF record from Titan’s control panel to your DNS. **550 5.7.2** means your SPF record exists but doesn’t include Titan, and **550 5.7.4** means it has a syntax error or there’s more than one. - **550 5.8.1 Error in dkim public key, DKIM public key not found in dns:** the DKIM record is missing or was pasted incorrectly. Copy it again from Titan’s control panel. - **Timeouts:** try the other port and SSL combination: 465 with SSL on, or 587 with SSL off. For anything not listed here, look the code up in [SMTP error codes explained](https://formsmtp.com/guides/smtp-error-codes). Sources: [Titan on email scripts](https://support.titan.email/hc/en-us/articles/4405162224665-Configuring-Titan-on-Email-Scripts) · [Enable Titan on other apps](https://support.titan.email/hc/en-us/articles/25005307786905-Enable-Titan-on-other-apps) · [Titan in FluentSMTP (EU server)](https://support.titan.email/hc/en-us/articles/46410123025305-Add-your-Titan-email-account-on-Fluent-SMTP) · [Sending limits](https://support.titan.email/hc/en-us/articles/360038836914-How-many-emails-can-I-send-and-receive) · [Outgoing reject codes](https://support.titan.email/hc/en-us/articles/35174724822169-Understanding-Outgoing-Email-Reject-Codes). Checked November 2, 2026. ## FAQ ### What is Titan’s SMTP server? smtp.titan.email, on port 465 with SSL or 587 with STARTTLS. EU-hosted accounts bought through certain resellers use smtp0101.titan.email, and GoDaddy’s Titan mailboxes use smtpout.secureserver.net. ### Why does Titan reject my correct password? Third-party access is probably off. Turn on Enable Titan on Other Apps in Titan Webmail settings. With two-factor authentication on, use an app password. ### Why is my sending limit lower than my plan says? Domains new to Titan start with lower limits that rise as they build a good sending history. Upgrading a plan may not raise them straight away for a new domain. ### My mailbox is Titan through Hostinger. Which guide? This one: use the host Titan shows in its settings. The Hostinger guide is for Hostinger’s own email service, which uses smtp.hostinger.com. ### Why do my messages land in spam? Usually the From address isn’t on a domain you’ve verified with the provider, or the domain has no SPF and DKIM records. Verify the domain, send from an address on it, and check the Deliverability panel in FormSMTP’s Settings. ## More guides - [Use Gmail SMTP for your website contact form](https://formsmtp.com/guides/gmail-smtp-contact-form) - [Use Zoho Mail SMTP for your website contact form](https://formsmtp.com/guides/zoho-smtp-contact-form) - [Outlook & Microsoft 365 SMTP for a website contact form](https://formsmtp.com/guides/outlook-smtp-contact-form) - [Use Amazon SES SMTP for your website contact form](https://formsmtp.com/guides/amazon-ses-smtp-contact-form)