How is rakuten-sec.co.jp?

Looks fine risk 0/100

Registered 22 years ago, on no blocklists we checked, valid HTTPS, the site answered 200 in 2473 ms.

Why

02050100

finecarefulhigh risk

·Nothing in the checks added risk.

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

The home page, rendered by how.is in a sandboxed browser. Nothing on it is clickable here.

Site

200

2473 ms · ends at www.rakuten-sec.co.jp

HTTPS

176 d

left on a DigiCert Inc certificate

Age

22 years

registered 2004-05-20

Blocklists

listings across 5 lists

Everything we looked at

DNS records4 record types

A	184.29.45.19 23.55.209.102
MX	20 cluster1a.us.messagelabs.com 10 cluster1.us.messagelabs.com
NS	ns002-ckhchk566p6qqq16.c.d-53.net ns002-ckhchk566p6qqq16.c.d-53.jp ns002-ckhchk566p6qqq16.c.d-53.info
TXT	google-site-verification=c0ajnwwEqIZQdJeIOnLEMw6bvdHp0AVcUQHVVu74KMA google-site-verification=cxOGi-BwtG4PxoNPL6ISvZWNkL2UgXMQXdeUOgb5at0 nulab-verification-code=j7c3NsrgoVaYQJGvlevwdRONUnZ8oWSeyN5MV7SjzDlduMzjPe8sZ94U4ikwzQEl spf2.0/mfrom ip4:124.215.210.0/25 ip4:125.29.56.75/32 ip4:202.144.241.0/24 ip4:202.131.202.80/29 ~all v=spf1 include:spf.mta.hdems.com include:spf.messagelabs.com include:cust-spf.exacttarget.com include:_spf.salesforce.com include:_spf.rakuten-sec.co.jp include:spf.e-shishobako.ne.jp include:spf01.rakuten.co.jp ~all MS=ms71322580 3colh245esfbq044pr4hor8he4 b4cl9v2e2mhvc435bk6n5ejesd d7eb5vabhrldtk90u7p25hhkm5 m20bbdsfkv0bse1nau56a2a5dj muot6n2bl77fmd37loq4md43mu nkanblkebro8hndpkvfg554tel u1kkva5h3t4mlqnru6rlrmg2qv _6ktx68pbcc5rikmp7lsyh9wr2dy6yjj _mjigvkf8rdalwmykc21e79qfagd17nq asv=004367d23fd2f93156f25b1f1f23aa6c facebook-domain-verification=nsvqpwfu7fqhrupndd5b8ipoiniyce google-site-verification=MrCVQV9cCpk1EohSN2kEFOf6UycqQDckTAxMb7e8_TA

Registrationregistrar not reported

registered	2004-05-20
expires	2027-05-31
last changed	2026-06-01
owner	Rakuten Securities, Inc.
nameservers	ns002-ckhchk566p6qqq16.c.d-53.jp ns002-ckhchk566p6qqq16.c.d-53.net ns002-ckhchk566p6qqq16.c.d-53.info
status	Connected (2027/05/31)

registered 2004-05-20expires 2027-05-31

HTTPS certificate176 days left

valid	yes
issuer	DigiCert Inc
covers	www.rakuten-sec.co.jp, rakuten-sec.co.jp
protocol	TLSv1.3

issued 2026-10-08expires 2027-04-24

DNSSECinsecure

Domain is not signed with DNSSEC

. → jp → co.jp → rakuten-sec.co.jp

Email authenticationexcellent

SPF	pass `v=spf1 include:spf.mta.hdems.com include:spf.messagelabs.com include:cust-spf.exacttarget.com include:_spf.salesforce.com include:_spf.rakuten-sec.co.jp include:spf.e-shishobako.ne.jp include:spf01.rakuten.co.jp ~all`
DMARC	pass policy reject
DKIM	found: selector1, s1, s2

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

Security scoregrade B · 165/205

Basic Security

20/40missing: DNSSEC Enabled

Record Security

30/45missing: CAA Records, DKIM Presence

Advanced Security

20/25missing: IPv6 Support

Domain Reputation

50/50

Threat Detection

45/45missing: Domain Age Check

Blocklists0 listings · 8 lookups

SURBL MultidomainURIBL MultidomainSpamCop23.55.209.102Barracuda23.55.209.102UCEPROTECT Level 123.55.209.102SpamCop184.29.45.19Barracuda184.29.45.19UCEPROTECT Level 1184.29.45.19

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-sec.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-sec.co.jp"

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

Watch rakuten-sec.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