Package 1 · Backup MX
Secondary MX, temporary queuing during destination outages and automatic delivery on recovery. No mailbox pre-check, AntiSpam, Antivirus, content inspection or quarantine.
TECHNICAL GUIDES
Troubleshoot Backup MX TXT Ownership Verification
Check the correct DNS zone, record name and current verification token before blaming propagation.
Package 2 · Email Protection
Primary MX gateway with configurable AntiSpam, Antivirus, sender-domain checks and quarantine. Publish only gate.securawall.com and configure a separate manual receiving target. Queuing and recovery remain included.
Optional SMTP Relay add-on
Add authorized outbound delivery to either Package 1 or 2 for the same domain. Separate add-on pricing, approval, server credentials, quotas, TLS and verified SPF apply. Customer-domain DKIM signing is optional and recommended. Incoming protection remains determined by the base package.
Explore packages and add-ons
By the SecuraWall team · Updated · Operational guidance, not a delivery guarantee.
Use the current proof
Copy the value displayed by the current account or checkout order. A deleted domain or a new ownership attempt may use a different token. Publishing a previous value does not prove the current account owns the domain. Compare the exact text rather than its length or appearance.
Enter Host / Name and TXT value separately
For the DNS zone of your protected domain, use Host / Name _securawall-verify and the exact securawall-verification= token provided in the portal. DNS interfaces may append the zone automatically; do not append the domain a second time. Do not enter an MX target or SPF policy in the ownership TXT value.
Confirm that you edited the delegated zone
A record in an inactive DNS account is not enough. Check which nameservers the domain actually delegates to and compare their published answers. If authoritative servers disagree or a lookup fails, keep the problem open rather than claiming that the record is absent everywhere.
Understand cached absence
Recursive resolvers can cache a missing-record response as well as a positive answer. Correcting the DNS panel does not guarantee an immediate change at every resolver. There is no fixed five-minute worldwide propagation promise. First check whether the authoritative answers contain the current exact token.
Separate DNS match from application state
A matching public TXT is only one part of the workflow. The domain must belong to the correct account and current order, and the service state must allow activation. If public answers match but the portal does not verify, open a ticket with the domain, current order reference, time and DNS observations. Do not regenerate proof repeatedly without checking which token is expected.
Keep the proof after activation
Do not remove the ownership record when purchase completes. A missing or changed proof can pause acceptance and queued delivery; queue age continues. The free DNS tool can display a TXT record when its record name is entered, but it does not verify the current account ownership token. Review domain security in your authenticated portal for the current proof and service status.
References and service conditions
Related guides
MX Priorities and Multiple Mail Servers
Understand preference numbers, equal-priority records and secondary MX placement.
Read guide →How to Test Backup MX Safely
Validate your own domain, queue behavior and recovery without treating an open port as successful delivery.
Read guide →Backup MX Delivery Troubleshooting Checklist
Identify whether a delay comes from service state, DNS, routing, SMTP rejection or final mailbox handling.
Read guide →