Everything required to go live.
Getting Started
Connect your first sending domain, establish its Firetip identity and begin the authentication process.
DNS Configuration
Understand the DNS layer and configure the records required for authenticated Firetip sending.
DKIM Authentication
Learn how cryptographic signing establishes verifiable sender identity for your messages.
SPF & Routing
Authorise Firetip infrastructure and understand how SPF controls permitted sending sources.
DMARC Protection
Define authentication alignment, enforcement and reporting for your domain.
Domain Verification
Confirm DNS, authentication and sending readiness before moving into production.
Sender Reputation
Understand how authentication, volume, engagement and recipient quality influence delivery.
Troubleshooting
Diagnose DNS, SPF, DKIM, DMARC and verification problems systematically.
Advanced Configuration
Explore advanced selectors, routing and infrastructure controls for experienced operators.
Your domain is your sending identity.
Firetip doesn't simply provide an SMTP endpoint. Your domain becomes an authenticated identity within the outbound infrastructure. Configure the DNS layer correctly and Firetip can establish the cryptographic and routing signals required for trusted delivery.
Start Domain SetupFrom domain to ready-to-send.
Connect your first domain.
Before Firetip can send communications on behalf of your organisation, you need to connect a sending domain and establish it as an authenticated sender identity.
Add your domain
Add the domain you intend to use inside Firetip. The domain becomes the identity associated with your outbound communications.
Infrastructure
Your sending identity is associated with the Firetip outbound infrastructure responsible for delivery.
Complete authentication
Publish the required DNS records, verify the domain and confirm the sender identity is ready before production delivery.
Configure your domain authentication layer.
DNS provides the public authentication and routing layer that allows receiving mail systems to establish whether Firetip is authorised to send on behalf of your domain.
Identifies the infrastructure permitted to send mail for your domain.
Allows receiving systems to verify that messages were signed by an authorised sender.
Defines how receiving systems should handle messages that fail authentication or alignment.
Establish a cryptographic sender identity.
DKIM attaches a cryptographic signature to outgoing messages. Receiving systems can retrieve the corresponding public key from DNS and verify the signature.
Firetip DKIM selectors
Firetip provisions a DKIM identity for your sending domain and associates the selector with the corresponding cryptographic key material.
firetip
The public key is published through DNS while the corresponding private signing material remains within the Firetip infrastructure.
Authorise Firetip to deliver for your domain.
Sender Policy Framework allows domain owners to publish which infrastructure is authorised to send mail using their domain.
An incorrect SPF policy can cause legitimate Firetip messages to fail authentication or affect delivery.
What SPF does
SPF publishes an authorised sender policy through your domain's DNS records. Receiving systems can compare the sending infrastructure against that policy.
Routing considerations
Avoid publishing conflicting SPF records. A domain should maintain a single SPF policy containing the authorised sending services required by your infrastructure.
Define your domain authentication policy.
DMARC builds on SPF and DKIM by allowing the domain owner to define authentication and alignment requirements and communicate how failures should be handled.
Collect authentication information without requesting enforcement.
Ask receiving systems to treat authentication failures with increased suspicion.
Request rejection of messages that fail the domain's DMARC authentication requirements.
Confirm your sending identity is ready.
Firetip verification checks the authentication layer associated with your domain before production sending begins.
Protect the reputation of your sending identity.
Authentication establishes identity. Reputation is influenced by how that identity is used over time. Responsible sending practices are essential for sustained delivery performance.
Consistent volume
Avoid sudden and unexplained changes in outbound sending volume wherever possible.
Quality recipients
Send to recipients who have a legitimate reason to receive your communications.
Control failures
Monitor bounces, complaints and authentication failures and address recurring problems quickly.
Diagnose authentication and DNS problems.
If your domain fails verification, work through the authentication layer systematically rather than changing multiple DNS records at once.
Confirm that the record has been published at the authoritative DNS provider and allow sufficient time for DNS propagation.
Check the selector, hostname and public key. Ensure the complete TXT value has been published correctly.
Check that Firetip is authorised by the domain's SPF policy and that multiple SPF TXT records have not been created.
Check alignment between the visible From domain and the authenticated SPF or DKIM identity.
Advanced domain and infrastructure controls.
Experienced operators can extend their Firetip domain configuration with advanced routing, selector and infrastructure controls.
DKIM selectors
Maintain controlled selector identities for your outbound signing configuration.
Routing
Configure infrastructure routing according to your Firetip deployment and delivery requirements.
Infrastructure
Understand the relationship between your domain identity and the Firetip outbound infrastructure.
Identity controls
Maintain consistent authentication and sender identity across your Firetip communications stack.