StatusPage is making some changes to the way we do DNS entries and verify ownership of domains. This requires some updates to DNS entries for existing customers who had these things configured prior to January 18th (don't worry, you're not required to make any changes until April 19th). For customers who joined on or after January 18th, you'll be asked to configure these things while setting up your custom domain and custom 'from' email address.
In order to keep your custom domain and notifications 'from' address working properly, you'll need to update (and maybe add) some DNS entries that point toward our infrastructure before April 19th, 2017. Everything will behave as normal until April 19th.
In order to use a custom notifications 'from' email or a custom domain, we require proof that you own the associated domains. In order to prove ownership of the domain(s) you need to add some records to your DNS. All records must remain on your DNS. We automatically re-verify every hour.
If you set up a custom 'from' address, but it is not verified, we will still send emails, but they will not come from your domain, they will come from firstname.lastname@example.org. If only one mail provider is configured, we will only send mail from that provider. We strongly suggest configuring DKIM for both mail providers to ensure email deliverability.
1. The following TXT record is required on the domain, with a format of:
This record allows us to ensure the domain belongs to you.
All DNS providers allow for multiple records. You should check with your DNS provider for instructions on how to add multiple records. In general, multiple TXT records can be entered in a set of full quotation marks, on separate lines, like in the example below:
"Sample txt entries" "Enclose entries in quotation marks"
2. Your SPF record must include:
For help with SPF, go here.
You can only have one SPF record per domain. However, you can set multiple SPF entries within that record.
Here's a valid example:
v=spf1 include:mailgun.org include:stspg-customer.com -all
Here's an invalid example:
v=spf1 include:mailgun.org -all v=spf1 include:stspg-customer.com -all
3. Setting up a DKIM record for provider #1 (Mailgun)
Setting this up will ensure we can send mail from your domain using this provider.
Note: If you're already using Mailgun to send emails from your domain for another service, we won't be able to add that domain a second time. In this case, we recommend using a subdomain for your custom 'from' address. For example, instead of email@example.com, firstname.lastname@example.org.
4. Setting up a DKIM record for provider #2 (Sendgrid)
Setting this up will ensure we can send mail from your domain using this provider. We strongly suggest you setup DKIM for both mail providers.
What if I only configure one mail provider? If only one mail provider is configured, we will send all mail for you through the configured provider. If a provider happens to go down, we make a system-wide change to throttle all mail to the functioning provider. If that provider is not configured properly on your page, all mail notification will be sent from email@example.com until we change the system-wide setting once both mail providers are up and running. For this reason, we recommend configuring both DKIM #1 and #2 to ensure your mail is always sent from your custom 'from' address.
We require you to create a CNAME pointing to StatusPage with the following value:
status.company.com CNAME ABC123.stspg-customer.com
This will allow us to effectively route traffic to your statuspage through your custom domain.
For help with any of this, reach out to firstname.lastname@example.org.