npr.org

npr.org · Last checked 2026-10-04 02:11 UTC

npr.org

Needs work, with 1 thing to fix

npr.org scored 68/100 (grade C). The main issues are included domain has no SPF record and SPF is close to the 10-lookup limit, plus 2 more. Detected senders: Microsoft 365, Salesforce and Mandrill.

Checked 2026-10-04 02:11 UTC · fresh check

4 passed1 needs attention0 failing3 for informationDetected senders: Microsoft 365, Salesforce, Mandrill
Fix this firstThe change with the biggest effect

Reduce SPF DNS lookups

Evaluating SPF for npr.org takes 9 DNS lookups including nested includes; receivers stop at 10 and fail SPF. No detected sending service accounts for these includes; remove each one you no longer send through: spf-0032f701.pphosted.com, prss.org, c9eb27a2d7.berenice.eoidentity.com.

TypeTXT
Name / Host
npr.org

Some DNS providers want “@” here instead of the full domain.

Value
v=spf1 include:spf-0032f701.pphosted.com include:spf.protection.outlook.com include:prss.org exists:%{i}._spf.mta.salesforce.com include:c9eb27a2d7.berenice.eoidentity.com ip4:64.124.132.59/32 ip4:66.150.167.192/27 ip4:162.242.229.170 ip4:205.153.38.0/24 ip4:205.153.36.170 ip4:40.107.0.0/16 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.0.0/16 ip4:139.60.0.0/24 ip4:139.60.1.0/24 ip4:139.60.2.0/24 ip4:139.60.3.0/24 ip4:13.111.0.0/16 ip4:136.147.135.0/24 ip4:136.147.176.0/24 ip4:136.147.182.0/24 ip4:198.245.81.0/24 ip4:199.122.123.0/24 ip4:195.66.99.135 ip4:212.227.89.57 ip4:217.160.226.166 ip4:54.194.192.132 ip4:62.75.247.44 ip4:82.165.193.1 ip4:85.25.144.9 ip4:87.79.30.25 ip4:87.79.30.30 ip4:208.86.168.7 ip4:135.84.68.123 ip4:206.152.14.54 ip4:54.240.43.16 include:_spf.salesforce.com ip4:209.144.103.186 include:spf.mandrillapp.com -all
Replaces
v=spf1 include:spf-0032f701.pphosted.com include:spf.protection.outlook.com include:prss.org exists:%{i}._spf.mta.salesforce.com include:c9eb27a2d7.berenice.eoidentity.com ip4:64.124.132.59/32 ip4:66.150.167.192/27 ip4:162.242.229.170 ip4:205.153.38.0/24 ip4:205.153.36.170 ip4:40.107.0.0/16 ip4:205.201.128.0/20 ip4:198.2.128.0/18 ip4:148.105.0.0/16 ip4:139.60.0.0/24 ip4:139.60.1.0/24 ip4:139.60.2.0/24 ip4:139.60.3.0/24 ip4:13.111.0.0/16 ip4:136.147.135.0/24 ip4:136.147.176.0/24 ip4:136.147.182.0/24 ip4:198.245.81.0/24 ip4:199.122.123.0/24 ip4:195.66.99.135 ip4:212.227.89.57 ip4:217.160.226.166 ip4:54.194.192.132 ip4:62.75.247.44 ip4:82.165.193.1 ip4:85.25.144.9 ip4:87.79.30.25 ip4:87.79.30.30 ip4:208.86.168.7 ip4:135.84.68.123 ip4:206.152.14.54 ip4:54.240.43.16 include:_spf.salesforce.com ip4:209.144.103.186 include:spf.mandrillapp.com -all

How to apply it

  1. Sign in where your domain’s DNS is managed. This is often where you bought the domain, such as Cloudflare, GoDaddy or Namecheap.
  2. Find the existing TXT record with that name and replace its value.
  3. 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 record is very longNeeds attention
  • Warning: SPF record is very long

    The SPF record is 852 characters. Long TXT answers can exceed the 512-byte UDP limit and force fallback to TCP, which some receivers do not do. Replace individual IP ranges with includes or ranges, or remove services you no longer use. (Only the total length is checked: the resolver returns the record already joined, so the 255-character limit on each individual string cannot be seen here.)

  • Warning: SPF is close to the 10-lookup limit

    Evaluating the SPF record for npr.org needs 9 of the 10 allowed DNS lookups. Adding one more service, or a provider growing its own record, will break SPF.

    How to fix this
  • Warning: SPF has too many lookups that return nothing

    Checking mail from npr.org, IPv6 clients would hit 3 void lookups (DNS queries that return no data). RFC 7208 lets receivers fail SPF after 2. Remove includes and mechanisms that point at names that no longer exist, or MX hosts without an address for that family.

  • Warning: Included domain has no SPF record

    The SPF record refers to c9eb27a2d7.berenice.eoidentity.com (include or redirect), which publishes no SPF record. Receivers treat that as a permanent error. Check the provider's current include domain or remove it.

DKIMAre your emails signed?DKIM key publishedPass
  • Pass: DKIM key published

    npr.org publishes a DKIM key under selector1, k2, k3, s1, s2.

DMARCWhat happens to fakes?No issues foundPass

Nothing to report.

AlignmentDoes it match your From?SPF alignment is unknownInfo
  • Info: SPF alignment is unknown

    The SPF record of npr.org can pass for some senders (those matched before the failing part), but another evaluation path ends in a permanent error (spf.void-lookups, spf.include.missing). Senders that reach that path fail SPF, so whether your mail aligns through SPF is unknown. Fix the error so every path evaluates.

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.npr.org. 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.npr.org. 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 npr.org publishes an MTA-STS policy at https://mta-sts.npr.org/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT
Name / Host
_mta-sts.npr.org

Some DNS providers want just “_mta-sts” here.

Value
v=STSv1; id=202610040211

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.npr.org. It lists your MX hosts and starts in testing mode; switch to mode: enforce once TLS-RPT reports show no failures.

Location
https://mta-sts.npr.org/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: mxa-0032f701.gslb.pphosted.com
mx: mxb-0032f701.gslb.pphosted.com
max_age: 604800

Set up a TLS report addressinstruction

Sending servers will report TLS failures when delivering to npr.org, 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.npr.org

  1. Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@npr.org, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.npr.org with the value v=TLSRPTv1; rua=mailto:<that address>.