ted.com

ted.com · Last checked 2026-10-04 02:17 UTC

ted.com

Needs work, with 3 things to fix

ted.com scored 61/100 (grade C). The main issues are DMARC policy is none and BIMI needs an enforced DMARC policy, plus 2 more. Detected senders: Google Workspace, Zendesk and Mandrill.

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

2 passed3 need attention0 failing3 for informationDetected senders: Google Workspace, Zendesk, Mandrill
Fix this firstThe change with the biggest effect

Strengthen the DMARC policy

Quarantines 25% of mail that fails DMARC, a safe first step: check the reports for legitimate senders that fail before going further. Changes: Subdomains move one step, from sp=none to the domain policy (p=quarantine).

TypeTXT
Name / Host
_dmarc.ted.com

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=quarantine; pct=25; rua=mailto:re+ld47nrddppg@dmarc.postmarkapp.com; adkim=r; aspf=r
Replaces
v=DMARC1; p=none; pct=100; rua=mailto:re+ld47nrddppg@dmarc.postmarkapp.com; sp=none;

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 ends in softfail (~all)Info
  • 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 shorter than 2048 bitsNeeds attention
  • Warning: DKIM key shorter than 2048 bits

    google (1024-bit), k1 (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

    ted.com publishes a DKIM key under google, k1, s1, s2.

DMARCWhat happens to fakes?DMARC policy is noneNeeds attention
  • Warning: DMARC policy is none

    A none policy only monitors: mail that fails DMARC is still delivered, so anyone can spoof the domain. Once reports show your legitimate senders pass, move to quarantine and then reject.

    How to fix this
AlignmentDoes it match your From?No issues foundPass

Nothing to report.

BIMICan inboxes show your logo?BIMI record is malformedNeeds attention
  • Warning: BIMI record is malformed

    The BIMI record at default._bimi.ted.com is invalid: the l= URL must be an https URL.

  • Warning: BIMI needs an enforced DMARC policy

    Mailbox providers only show BIMI logos when the DMARC policy that applies to ted.com is quarantine or reject at pct=100; it is effectively p=none. Move DMARC to enforcement for the logo to appear.

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

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

TypeTXT
Name / Host
_mta-sts.ted.com

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

Value
v=STSv1; id=202610040217

Host the MTA-STS policy filepolicy-file

Serve this file over HTTPS with a valid certificate for mta-sts.ted.com. 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.ted.com/.well-known/mta-sts.txt
Contents
version: STSv1
mode: testing
mx: aspmx.l.google.com
mx: alt1.aspmx.l.google.com
mx: alt2.aspmx.l.google.com
mx: aspmx2.googlemail.com
mx: aspmx3.googlemail.com
max_age: 604800

Set up a TLS report addressinstruction

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

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