unesco.org

unesco.org · Last checked 2026-10-04 02:13 UTC

unesco.org

Good, with 3 things to fix

unesco.org scored 76/100 (grade B). The main issues are DKIM key shorter than 2048 bits and DMARC: subdomain policy is weaker than the domain policy, plus 1 more. Detected senders: Microsoft 365.

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

1 passed3 need attention0 failing4 for informationDetected senders: Microsoft 365
Fix this firstThe change with the biggest effect

Strengthen the DMARC policy

Rejects mail that fails DMARC, the strongest protection against spoofing. Changes: Subdomains move one step, from sp=none to sp=quarantine.

TypeTXT
Name / Host
_dmarc.unesco.org

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=reject; sp=quarantine; rua=mailto:3ac163cfde@rua.easydmarc.eu; adkim=r; aspf=r
Replaces
v=DMARC1;p=reject;sp=none;pct=100;rua=mailto:3ac163cfde@rua.easydmarc.eu;ruf=mailto:3ac163cfde@ruf.easydmarc.eu;ri=86400;fo=1

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 unesco.org goes to unesco-org.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 has too many lookups that return nothingNeeds attention
  • Warning: SPF has too many lookups that return nothing

    Checking mail from unesco.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.

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

    selector1 (1024-bit), s2 (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

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

DMARCWhat happens to fakes?Subdomain policy is weaker than the domain policyNeeds attention
  • Warning: Subdomain policy is weaker than the domain policy

    sp=none is weaker than p=reject, so attackers can spoof any subdomain of unesco.org (for example billing.unesco.org) even though the main domain is protected.

    How to fix this
AlignmentDoes it match your From?SPF alignment is unknownInfo
  • Info: SPF alignment is unknown

    The SPF record of unesco.org can pass for some senders (those matched before the failing part), but another evaluation path ends in a permanent error (spf.void-lookups). 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.unesco.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.unesco.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 unesco.org publishes an MTA-STS policy at https://mta-sts.unesco.org/.well-known/mta-sts.txt. Change the id whenever the policy file changes.

TypeTXT
Name / Host
_mta-sts.unesco.org

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

Value
v=STSv1; id=202610040213

Host the MTA-STS policy filepolicy-file

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

Set up a TLS report addressinstruction

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

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