include:stspg-customer.com – Atlassian Statuspage

Short answer: include:stspg-customer.com lets Atlassian Statuspage's mail servers pass SPF for your domain. It costs 1 of the 10 DNS lookups SPF allows (checked live).

v=spf1 ip4:23.253.182.103 ip4:23.253.183.145 ip4:23.253.183.146 ip4:23.253.183.147 ip4:23.253.183.148 ip4:23.253.183.150 ip4:166.78.68.221 ip4:167.89.46.159 ip4:167.89.64.9 ip4:167.89.65.0 ip4:167.89.65.53 ip4:167.89.65.100 ip4:167.89.74.233 ip4:167.89.75.33 ip4:167.89.75.126 ip4:167.89.75.136 ip4:167.89.75.164 ip4:192.237.159.42 ip4:192.237.159.43 ip4:159.112.242.162 ip4:159.135.228.10 ip4:198.244.56.107 ip4:198.244.56.108 ip4:198.244.56.109 ip4:198.244.56.111 ip4:198.244.56.112 ip4:198.244.56.113 ip4:198.244.56.114 ip4:198.244.56.115 ip4:204.220.181.105 ~all

Do you need it?

Only if Atlassian Statuspage sends mail with your domain in the envelope sender (Return-Path). Many services use their own bounce domain, and then this include does nothing for SPF or DMARC – DKIM does the work. Send a test email through Atlassian Statuspage to see which domain SPF is checked for.

Who uses it

In our scan of top websites on 23 Oct 2026:

• 53 of the 2,214 world's top-3,000 sites that publish SPF (2.4%)
• 1 of the 1,961 India's top-3,000 sites that publish SPF (0.1%)
• 0 of the 428 Indian government sites that publish SPF (0.0%)

Add it the right way

1. Keep one SPF record per domain: v=spf1 include:stspg-customer.com ~all, plus your other senders in the same record – SPF generator.
2. Stay under 10 lookups in total; every include counts, nested ones too.
3. SPF alone isn't enough for Gmail, Yahoo and Outlook: turn on DKIM and publish DMARC.

Check your domain

After the fix, send a test email to see SPF, DKIM and DMARC pass on a real message, then keep an eye on it: free DMARC monitoring shows every service that sends mail as your domain and which ones fail, in plain English.

Other includes

All 47 SPF includes