perplexity.ai
Excellent, with 1 thing to fix
perplexity.ai scored 92/100 (grade A). The main issue is SPF is close to the 10-lookup limit. Detected senders: Google Workspace, SendGrid and Mailgun.
Checked 2026-10-04 02:14 UTC · fresh check
Reduce SPF DNS lookups
Evaluating SPF for perplexity.ai takes 8 DNS lookups including nested includes; receivers stop at 10 and fail SPF. Every include belongs to a detected provider; move some senders to a subdomain with its own SPF record. Changes: Replaced ~all with -all so mail from servers not listed is rejected.
perplexity.ai
Some DNS providers want “@” here instead of the full domain.
v=spf1 ip4:192.174.84.143 include:_spf.google.com include:mailgun.org include:sendgrid.net -all
v=spf1 ip4:192.174.84.143 include:_spf.google.com include:mailgun.org include:sendgrid.net ~all
How to apply it
- Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
- Find the existing TXT record with that name and replace its value.
- Save, then come back and re-check. DNS changes can take up to a few hours to show.
All checks
MXCan servers find your inbox?No issues foundPass
Nothing to report.
SPFWho may send as you?SPF is close to the 10-lookup limitNeeds attention
- Warning: SPF is close to the 10-lookup limit
Evaluating the SPF record for perplexity.ai needs 8 of the 10 allowed DNS lookups. Adding one more service, or a provider growing its own record, will break SPF.
How to fix this - Info: SPF ends in softfail (~all)
"~all" is common and works well with DMARC. "-all" is stricter; switch when you are sure every sender is listed.
DKIMAre your emails signed?DKIM key publishedPass
- Pass: DKIM key published
perplexity.ai publishes a DKIM key under google, s1, s2.
DMARCWhat happens to fakes?No issues foundPass
Nothing to report.
AlignmentDoes it match your From?No issues foundPass
Nothing to report.
BIMICan inboxes show your logo?No issues foundPass
Nothing to report.
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
- Info: No MTA-STS record
No MTA-STS record at _mta-sts.perplexity.ai. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.
How to fix this
TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
- Info: No TLS-RPT record
No TLS reporting record at _smtp._tls.perplexity.ai. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.
How to fix this
Other fixes
Publish the MTA-STS recordTXT
Tells sending servers that perplexity.ai publishes an MTA-STS policy at https://mta-sts.perplexity.ai/.well-known/mta-sts.txt. Change the id whenever the policy file changes.
_mta-sts.perplexity.ai
Some DNS providers want just “_mta-sts” here.
v=STSv1; id=202610040214
Host the MTA-STS policy filepolicy-file
Serve this file over HTTPS with a valid certificate for mta-sts.perplexity.ai. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.
https://mta-sts.perplexity.ai/.well-known/mta-sts.txt
version: STSv1 mode: testing mx: aspmx.l.google.com mx: alt1.aspmx.l.google.com mx: alt2.aspmx.l.google.com mx: alt3.aspmx.l.google.com mx: alt4.aspmx.l.google.com max_age: 604800
Set up a TLS report addressinstruction
Sending servers will report TLS failures when delivering to perplexity.ai, which you need before enforcing MTA-STS. The address must accept TLS reports; a DMARC report address does not necessarily do so.
Applies to: _smtp._tls.perplexity.ai
- Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@perplexity.ai, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.perplexity.ai with the value v=TLSRPTv1; rua=mailto:<that address>.