nikkei.com

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

nikkei.com

Poor, with 3 things to fix

nikkei.com scored 54/100 (grade D). The main issues are no SPF record and DKIM key shorter than 2048 bits, plus 1 more.

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

1 passed2 need attention1 failing4 for information
Fix this firstThe change with the biggest effect

Publish an SPF record

No sending service was detected, so this record says no server may send as nikkei.com. If you do send mail, add your provider's include before publishing.

TypeTXT
Name / Host
nikkei.com

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

Value
v=spf1 -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. Add a new TXT record with the name and value above.
  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?Mail relies on implicit A recordNeeds attention
  • Warning: Mail relies on implicit A record

    nikkei.com has no MX records, so senders fall back to its A/AAAA address (RFC 5321 implicit MX). Publish an explicit MX record, or a null MX ("0 .") if the domain should not receive mail.

SPFWho may send as you?No SPF recordFailing
  • Fail: No SPF record

    nikkei.com publishes no TXT record starting with "v=spf1", so receivers cannot tell which servers may send mail for it. Publish one SPF record listing every service that sends as nikkei.com.

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

    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

    nikkei.com publishes a DKIM key under s1, s2.

DMARCWhat happens to fakes?DMARC policy is quarantine; consider rejectInfo
  • Info: DMARC policy is quarantine; consider reject

    Failing mail goes to spam rather than being refused. When reports show no legitimate failures, reject gives the strongest protection.

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

Nothing to report.

BIMICan inboxes show your logo?No BIMI recordInfo
  • Info: No BIMI record

    No BIMI record at default._bimi.nikkei.com. 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.nikkei.com. MTA-STS (RFC 8461) makes sending servers require TLS and a valid certificate when delivering to you, which blocks downgrade attacks.

TLS-RPTWill you hear about failures?No TLS-RPT recordInfo
  • Info: No TLS-RPT record

    No TLS reporting record at _smtp._tls.nikkei.com. TLS-RPT (RFC 8460) tells senders where to send daily reports about failed encrypted deliveries to you.

    How to fix this

Other fixes

Strengthen the DMARC policyTXT

Rejects mail that fails DMARC, the strongest protection against spoofing.

TypeTXT
Name / Host
_dmarc.nikkei.com

Some DNS providers want just “_dmarc” here.

Value
v=DMARC1; p=reject; rua=mailto:dmarc-nikkeicom@mx.nikkei.com; adkim=r; aspf=r
Replaces
v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc-nikkeicom@mx.nikkei.com

Set up a TLS report addressinstruction

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

  1. Pick an address that will receive TLS reports: a mailbox you read (for example tls-reports@nikkei.com, created first) or a TLS reporting service. 2. Publish a TXT record at _smtp._tls.nikkei.com 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.nikkei.com

  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://nikkei.com/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.nikkei.com with v=BIMI1, l= set to the logo URL and a= set to the certificate URL.