public company · JP

Rakuten

Rakuten Group, Inc.

Japanese e-commerce, card and banking group; point and card lures.

Primary official domain
rakuten.co.jp
Reviewed official domains
4 (directory review; organization has not verified)
Directory source
DomainSpoof directory · Suggest a correction
Matching domains, 30 days
5
registrable domains containing the brand; source date or last feed observation
First source-reported, 30 days
0
domains first source-reported within 30 days
First observed, 30 days
5
domains first observed by DomainSpoof in feeds
Email policy (primary domain)
DMARC reject
SPF ~all · 2/10 lookups · Mail: Not checked · checked 2026-10-18 · published policy

What we watch for

Hostnames in phishing feeds and certificate logs are matched on these brand tokens; feed target labels are matched on the aliases. Generated spellings (typos, lure words, look-alike characters, other top-level domains) are derived from the official domains and tokens and checked against feeds, certificate logs and DNS.

Brand tokens
rakuten
Label aliases
Rakuten
Official domains
rakuten.co.jp · rakuten-bank.co.jp · rakuten-card.co.jp · rakuten.com (all)
Generated spellings
400 tracked · 0 observed somewhere · 400 not observed (all)

Official domains and email policies

Domains reviewed as belonging to Rakuten. DMARC helps receivers check the From domain; lookalike domains remain possible. Published policies cannot confirm actual mail configuration or receiver behavior.

DomainRelationshipEvidenceDMARC policyPolicy sourceSPFReportingMailDKIMMTA-STSLast check
rakuten.co.jp
primaryReviewed 2026-10-18
DomainSpoof directory (curated)rejectDirect~all · 2/10 lookupsAggregate reports requested (rua)Not checkedUnknown (no known selector)
Not checkedNot checked
2026-10-18 22:58 UTC
Records and check details

Published records

DMARC (_dmarc.rakuten.co.jp)
v=DMARC1; p=reject; rua=mailto:…@rx.rakuten.co.jp
SPF (rakuten.co.jp)
v=spf1 include:spf01.rakuten.co.jp include:spf02.rakuten.co.jp ~all
MX (rakuten.co.jp)
Not checked
DKIM
Unknown (no known selector). DKIM use requires a known selector or message to assess; a published key alone cannot confirm signing, and no key at the probed common selectors proves nothing.
MTA-STS (_mta-sts.rakuten.co.jp)
Not checked
TLS-RPT (_smtp._tls.rakuten.co.jp)
Not checked

Interpretation

  • p=reject: receivers are asked to reject failing mail.
  • Relaxed DKIM alignment (default).
  • Relaxed SPF alignment (default).
  • ~all (softfail): unlisted hosts are marked suspicious; this is not +all and does not by itself bypass DMARC.
  • 2 DNS-querying terms (include, a, mx, ptr, exists, redirect), counted recursively; the limit is 10.
  • Static check of the published record: syntax, every referenced include/redirect record, the DNS-lookup count and a/mx/exists targets (resolved to count void lookups). It does not evaluate SPF for any particular sending host.

DMARC discovery (RFC 9989 tree walk)

  1. _dmarc.rakuten.co.jp: ok, 1 DMARC record

Recent checks

  • 2026-10-18 22:58 UTC: DMARC reject; SPF ~all

Assessment posture-v2. DNS lookup failures leave the policy unknown.

rakuten-bank.co.jp
subsidiaryReviewed 2026-10-18
DomainSpoof directory (curated)quarantineDirectCould not fully evaluate (sender-specific macros)Aggregate reports requested (rua)Not checkedUnknown (no known selector)
Not checkedNot checked
2026-10-18 22:58 UTC
Records and check details

Published records

DMARC (_dmarc.rakuten-bank.co.jp)
v=DMARC1; p=quarantine; rua=mailto:…@mpub.ne.jp,mailto:…@rx.rakuten.co.jp
SPF (rakuten-bank.co.jp)
v=spf1 include:spf.protection.outlook.com include:spf02.rakuten.co.jp +ip4:220.213.233.48/30 +ip4:211.128.109.64/26 +ip4:211.130.191.128/25 +ip4:211.128.110.192/27 +ip4:219.99.189.128/27 +ip4:220.213.225.0/24 +ip4:219.99.179.64/26 include:spf-bma.mpme.jp include:axol.jp include:spf.humanage.co.jp include:_spf.salesforce.com -all
MX (rakuten-bank.co.jp)
Not checked
DKIM
Unknown (no known selector). DKIM use requires a known selector or message to assess; a published key alone cannot confirm signing, and no key at the probed common selectors proves nothing.
MTA-STS (_mta-sts.rakuten-bank.co.jp)
Not checked
TLS-RPT (_smtp._tls.rakuten-bank.co.jp)
Not checked

Interpretation

  • p=quarantine: receivers are asked to treat failing mail as suspicious.
  • Relaxed DKIM alignment (default).
  • Relaxed SPF alignment (default).
  • Could not fully evaluate: the record uses sender-specific macros (for example %{i}) whose targets depend on each sending host, so a static check cannot evaluate them and this is not reported as a valid record.
  • -all: unlisted hosts fail SPF.
  • At least 8 DNS-querying terms (include, a, mx, ptr, exists, redirect), counted recursively; the limit is 10.

Observations

  • SPF (sender-specific): _spf.salesforce.com: exists:%{i}._spf.mta.salesforce.com uses a sender-dependent macro

DMARC discovery (RFC 9989 tree walk)

  1. _dmarc.rakuten-bank.co.jp: ok, 1 DMARC record

Recent checks

  • 2026-10-18 22:58 UTC: DMARC quarantine; SPF could not fully evaluate

Assessment posture-v2. DNS lookup failures leave the policy unknown.

rakuten-card.co.jp
subsidiaryReviewed 2026-10-18
DomainSpoof directory (curated)rejectDirect~all · 4/10 lookupsAggregate reports requested (rua)Not checkedUnknown (no known selector)
Not checkedNot checked
2026-10-18 22:58 UTC
Records and check details

Published records

DMARC (_dmarc.rakuten-card.co.jp)
v=DMARC1; p=reject; rua=mailto:…@rx.rakuten.co.jp
SPF (rakuten-card.co.jp)
v=spf1 include:spf-bma.mpme.jp include:spf01.rakuten-card.co.jp include:spf02.rakuten-card.co.jp include:spf03.rakuten-card.co.jp ~all
MX (rakuten-card.co.jp)
Not checked
DKIM
Unknown (no known selector). DKIM use requires a known selector or message to assess; a published key alone cannot confirm signing, and no key at the probed common selectors proves nothing.
MTA-STS (_mta-sts.rakuten-card.co.jp)
Not checked
TLS-RPT (_smtp._tls.rakuten-card.co.jp)
Not checked

Interpretation

  • p=reject: receivers are asked to reject failing mail.
  • Relaxed DKIM alignment (default).
  • Relaxed SPF alignment (default).
  • ~all (softfail): unlisted hosts are marked suspicious; this is not +all and does not by itself bypass DMARC.
  • 4 DNS-querying terms (include, a, mx, ptr, exists, redirect), counted recursively; the limit is 10.
  • Static check of the published record: syntax, every referenced include/redirect record, the DNS-lookup count and a/mx/exists targets (resolved to count void lookups). It does not evaluate SPF for any particular sending host.

DMARC discovery (RFC 9989 tree walk)

  1. _dmarc.rakuten-card.co.jp: ok, 1 DMARC record

Recent checks

  • 2026-10-18 22:58 UTC: DMARC reject; SPF ~all

Assessment posture-v2. DNS lookup failures leave the policy unknown.

rakuten.com
subsidiaryReviewed 2026-10-18
DomainSpoof directory (curated)rejectDirect~all · 6/10 lookupsAggregate reports requested (rua)Not checkedUnknown (no known selector)
Not checkedNot checked
2026-10-18 22:58 UTC
Records and check details

Published records

DMARC (_dmarc.rakuten.com)
v=DMARC1; p=reject; rua=mailto:…@rx.rakuten.co.jp
SPF (rakuten.com)
v=spf1 include:spf01.rakuten.co.jp include:spf02.rakuten.co.jp include:spf03.rakuten.co.jp include:spf.protection.outlook.com include:_spf.activegate-ss.jp include:spf.mta.hdems.com ~all
MX (rakuten.com)
Not checked
DKIM
Unknown (no known selector). DKIM use requires a known selector or message to assess; a published key alone cannot confirm signing, and no key at the probed common selectors proves nothing.
MTA-STS (_mta-sts.rakuten.com)
Not checked
TLS-RPT (_smtp._tls.rakuten.com)
Not checked

Interpretation

  • p=reject: receivers are asked to reject failing mail.
  • Relaxed DKIM alignment (default).
  • Relaxed SPF alignment (default).
  • ~all (softfail): unlisted hosts are marked suspicious; this is not +all and does not by itself bypass DMARC.
  • 6 DNS-querying terms (include, a, mx, ptr, exists, redirect), counted recursively; the limit is 10.
  • Static check of the published record: syntax, every referenced include/redirect record, the DNS-lookup count and a/mx/exists targets (resolved to count void lookups). It does not evaluate SPF for any particular sending host.

DMARC discovery (RFC 9989 tree walk)

  1. _dmarc.rakuten.com: ok, 1 DMARC record

Recent checks

  • 2026-10-18 22:58 UTC: DMARC reject; SPF ~all

Assessment posture-v2. DNS lookup failures leave the policy unknown.

“Not checked”: no check yet (mail, DKIM and MTA-STS facts were added later, so older checks show “Not checked” for them). “Lookup failed”: DNS result unknown. DKIM is probed at a fixed list of common selectors only. Report mailbox names are redacted.

Reports on official domains appear under “Official assets with reports” on the Reported matches tab.