HOW.IS
?

How is rakuten.co.jp?

Looks fine risk 0/100

Registered 30 years ago, on no blocklists we checked, valid HTTPS, the site did not answer (timed out).

Why

02050100
finecarefulhigh risk
  • ·Nothing in the checks added risk.

Rule-based: domain age, blocklists, TLS. A heuristic, not a guarantee.

Site
down
timed out
HTTPS
159 d
left on a DigiCert Inc certificate
Age
30 years
registered 1997-02-07
Blocklists
0
listings across 5 lists

Everything we looked at

DNS records4 record types
A133.237.182.225
MX0 rakuten-co-jp.mail.protection.outlook.com
NSns02.rakuten.co.jp
ns06.rakuten.co.jp
ns02.rakuten.ad.jp
ns01.rakuten.ad.jp
TXTv=spf1 include:spf01.rakuten.co.jp include:spf02.rakuten.co.jp ~all
jjh5xgsjhfkfv2p1c4pnw695wt2d1b6m
_b6ls5cifmj3tlp051i6dr0ipvvl1d6i
_a23mdvjjysoqfsda5syosc3y3g8dixv
google-site-verification=jEVlUFe4ObKQwKXSMwI8eHSxbSurL8iVFJjjTgDWU0k
6c62zsshdj6rx8rchn06f5996q5449zl
42n2gr6qxm8zrk7zn6353mc1kh76xtn0
crk3qs7nrs2gw6ns59glnk3kpg34yb96
google-site-verification=SqqGXNFfgMep3bc91Z3f7RLBgYf-H-Fy5bF184JY56k
apple-domain-verification=UeLEhRNLNKOofIvN
google-site-verification=jfLP2TbPbqJSVvxptWAbrLvNNVLjpww-_Ra0KyD65EQ
google-site-verification=HB8QvSCuaOINaXr1P_gtW8S9ijT9a13u-YAiBMPBokg
google-site-verification=MMXQSgt7rmd8Qi1qW8vK1usn1zCT5V-d-I7UUr5gCEQ
_ab59puqfo49ja7egf36yhx1ceczcjt0
pardot1107312=6d02f8a191b3fa3cb2a63a0f8896b6b178977a6f295ef9bce9c81c2e76bbd512
dk81fmlb8ts78g53lrq4dv43z6dprl6x
Registrationregistrar not reported
registered1997-02-07
expires2027-02-28
last changed2026-07-15
ownerRakuten Group, Inc.
nameserversns02.rakuten.co.jp
ns06.rakuten.co.jp
ns01.rakuten.ad.jp
ns02.rakuten.ad.jp
statusConnected (2027/02/28)
registered 1997-02-07expires 2027-02-28
HTTPS certificate159 days left
validyes
issuerDigiCert Inc
covers*.rakuten.co.jp, rakuten.co.jp
protocolTLSv1.3
issued 2026-09-18expires 2027-04-04
DNSSECinsecure

Domain is not signed with DNSSEC

. → jp → co.jp → rakuten.co.jp
Email authenticationgood
SPFpass v=spf1 include:spf01.rakuten.co.jp include:spf02.rakuten.co.jp ~all
DMARCpass policy reject
DKIMnone of 1 common selectors

Whether mail claiming to be from this domain can be checked as genuine.

Security scoregrade B · 160/205
Basic Security
20/40missing: DNSSEC Enabled
Record Security
30/45missing: CAA Records, DKIM Presence
Advanced Security
15/25missing: Mail Server Configuration, IPv6 Support
Domain Reputation
50/50
Threat Detection
45/45missing: Domain Age Check
Blocklists0 listings · 5 lookups
SURBL MultidomainURIBL MultidomainSpamCop133.237.182.225Barracuda133.237.182.225UCEPROTECT Level 1133.237.182.225

Green: clean. Red: listed. Grey: the list did not answer.

Ask it yourself

Agents get this as data. Bought through the API, the checks behind this page cost $0.070: profile $0.025 + trust $0.020 + screenshot $0.020 + site status $0.005.

curl "https://how.is/v1/domain/trust?domain=rakuten.co.jp" \ -H "Authorization: Bearer $HOWIS_KEY" # or pay per call in USDC (x402), no key: the 402 tells your agent the price curl -i "https://how.is/v1/domain/profile?domain=rakuten.co.jp"

MCP: add https://how.is/mcp to Claude, Codex or Cursor (one-line install) and ask for domain_trust on rakuten.co.jp. Reference: /llms.txt.

Watch rakuten.co.jp. DNS read at the source every 5 minutes; certificate, blocklists and expiry every 6 hours. You get an email only when something changes.

Watch — $1 / 30 days