who.int

who.int · Last checked 2026-10-04 02:07 UTC

who.int

Poor, with 2 things to fix

who.int scored 59/100 (grade D). The main issues are SPF needs more than 10 DNS lookups and DKIM key shorter than 2048 bits, plus 1 more. Detected senders: Microsoft 365 and Salesforce.

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

1 passed1 needs attention1 failing5 for informationDetected senders: Microsoft 365, Salesforce
Fix this firstThe change with the biggest effect

Reduce SPF DNS lookups

Evaluating SPF for who.int takes 11 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: _spfincludes.who.int. Changes: Added include:_spf.salesforce.com for Salesforce.

TypeTXT
Name / Host
who.int

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

Value
v=spf1 ip4:158.232.12.0/24 include:spf.protection.outlook.com include:_spfincludes.who.int include:_spf.salesforce.com -all
Replaces
v=spf1 ip4:158.232.12.0/24 include:spf.protection.outlook.com include:_spfincludes.who.int -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?Only one MX hostInfo
  • Info: Only one MX host

    All mail for who.int goes to who-int.mail.protection.outlook.com. Most hosted providers make that one name highly available; if you run your own server, consider a backup MX.

SPFWho may send as you?SPF needs more than 10 DNS lookupsFailing
  • Fail: SPF needs more than 10 DNS lookups

    Evaluating the SPF record for who.int needs more than 10 DNS lookups (counting nested includes). Receivers stop at 10 with a permanent error, so SPF fails. Remove unused includes or replace them with IP ranges.

    How to fix this
  • Warning: SPF has no "all" term

    Without a closing "all" term, mail from unlisted servers gets a neutral result. End the record with "-all" or "~all".

DKIMAre your emails signed?DKIM key shorter than 2048 bitsNeeds attention
  • Warning: DKIM key shorter than 2048 bits

    selector1 (1024-bit) uses an RSA key below 2048 bits. Short keys can be factored and some receivers treat them as weak. Rotate to a 2048-bit key at your sending provider.

  • Pass: DKIM key published

    who.int publishes a DKIM key under selector1.

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 who.int can pass for some senders (those matched before the failing part), but another evaluation path ends in a permanent error (spf.lookups.over-limit). 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 BIMI recordInfo
  • Info: No BIMI record

    No BIMI record at default._bimi.who.int. BIMI is optional: it shows your logo next to your mail in supporting inboxes once DMARC is enforced.

    How to fix this
MTA-STSIs mail to you encrypted?No MTA-STS recordInfo
  • Info: No MTA-STS record

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

TypeTXT
Name / Host
_mta-sts.who.int

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

Value
v=STSv1; id=202610040207

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.who.int. 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.who.int/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: who-int.mail.protection.outlook.com
max_age: 604800

Set up a TLS report addressinstruction

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

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

Prepare BIMIinstruction

BIMI shows your logo next to messages in supporting inboxes, but only for mail that passes DMARC under an enforced policy.

Applies to: default._bimi.who.int

  1. Enforce DMARC first: p=quarantine or p=reject at 100% (no pct below 100). 2. Convert your logo to an SVG Tiny PS file and host it over HTTPS, for example https://who.int/bimi/logo.svg. 3. For Gmail and Apple Mail, obtain a VMC or CMC certificate for the logo. 4. Publish a TXT record at default._bimi.who.int with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.