HTTPS Checker

Security Tool

HTTPS, SSL & Security Report for rakuten.co.jp

This report summarizes how well rakuten.co.jp is configured for secure web delivery. It covers HTTPS availability, HTTP→HTTPS redirects, TLS/SSL certificate validity, security headers, HTTP/2 and HTTP/3 support, and mixed content. Use it to quickly spot configuration gaps and improve your site's security and trust.

SecureScore90/100Last checked: 23 Apr 2026 at 03:02 UTC
HTTPS

Enabled

HTTP → HTTPS

Yes

TLS

A · 1.2, 1.3

Security headers

0/6

Detailed checks

HTTPS availability

The site is reachable over HTTPS.

Why it matters: HTTPS encrypts traffic and protects user data.

HTTP to HTTPS redirect

Requests to HTTP are redirected to HTTPS.

TLS & CertificateA

ValidYes
IssuerC=US, O=DigiCert Inc, CN=DigiCert Global G3 TLS ECC SHA384 2020 CA1
Expires2026-05-19
Days until expiry26 days

Why it matters: A valid, non-expired certificate ensures encryption is trusted by browsers.

To improve your grade

  • •Improve: HSTS Enabled (+5 pts).
  • •Improve: Security Headers (+5 pts).
  • •For A+: add HSTS preload.
  • •For A+: add Content-Security-Policy.

Monitor this domain

We'll check SSL grade, HTTPS, redirects, and security headers automatically. Email only when something changes.

Start monitoring — freeOne-click account with Google, GitHub, or email. No password.

Free: 1 domain, weekly. Plans from €7/mo — daily checks, up to 50 domains, history & white-label PDF.

Grade breakdown4 things to improve for a higher grade →
90/100 pts
HTTPS Connection
+25/25
HTTP to HTTPS Redirect
+20/20
Valid SSL Certificate
+20/20
Certificate Not Expiring Soon
+10/10
Short Redirect Chain
+5/5
HSTS Enabled
+0/5
Security Headers
+0/5

Requires 4 of 6 headers and Content-Security-Policy (CSP).

Modern TLS (no 1.0/1.1)
+10/10

To improve your grade

  • •Improve: HSTS Enabled (+5 pts).
  • •Improve: Security Headers (+5 pts).
  • •For A+: add HSTS preload.
  • •For A+: add Content-Security-Policy.

Security headers0/6

    Score: 0 of 6 headers present. For the grade factor (5 pts), 4+ headers and Content-Security-Policy (CSP) are both required.

    HSTS (HTTP Strict Transport Security)Disabled

    • EnabledNo
    • On HSTS preload listNo
    Submit or verify on hstspreload.org

    Why it matters: HSTS tells browsers to use only HTTPS for this site. Preload allows inclusion in browsers’ built-in HSTS lists.

    We check Chromium’s built-in list. hstspreload.org checks eligibility for submission (HSTS header, redirect chain). Results may differ for domains that are preloaded but no longer meet current eligibility rules.

    HTTP/2

    Negotiated (ALPN h2)

    ALPN: h2

    HTTP/3 (QUIC)

    Not advertised

    The server does not advertise HTTP/3 (QUIC) via the Alt-Svc header.

    DNS Security

    CAA: Not set · DNSSEC: Not signedExpand
    CAANot set
    DNSSEC
    Not signed

    No CAA records. Any CA can issue certificates. Consider adding CAA to restrict issuance.

    Mixed content

    None detected

    No HTTP resources were detected on the HTTPS page.

    Redirect chain347ms total

    When you visit the site over HTTP, the server may send you through one or more redirects until you land on the final HTTPS URL. Shorter chains are faster and better for SEO.

    1. 1.http://rakuten.co.jp222ms
    2. 2.https://www.rakuten.co.jp/125ms

    Recommendations for rakuten.co.jp

    Based on this scan, here are the 4 next steps that would most improve security and SEO for rakuten.co.jp.

    1. Enable HSTS (Strict-Transport-Security)

      Recommended

      rakuten.co.jp does not send the Strict-Transport-Security header. Without it, returning visitors can still be downgraded to HTTP by an attacker on the network. One header makes browsers always use HTTPS.

      Security headers guide HSTS preload guide

    2. Add 6 missing security headers

      Recommended

      rakuten.co.jp sends 0 of 6 recommended security headers. Most take one line of server config and protect against clickjacking, MIME sniffing and data leaks.

      How to set security headers What each header does

    3. Consider HTTP/3

      Nice to have

      rakuten.co.jp supports HTTP/2 but does not advertise HTTP/3 (QUIC). HTTP/3 improves performance on lossy mobile networks. If you are behind Cloudflare or a modern CDN it is usually a toggle.

      How to enable HTTP/2 and HTTP/3 Why HTTP/3 detection tools disagree

    4. Add a CAA DNS record

      Nice to have

      rakuten.co.jp has no CAA record, so any certificate authority can issue certificates for it. A CAA record limits issuance to the CAs you actually use — a cheap defense against mis-issuance.

      What is a CAA record

    Show this badge on your site

    Let your visitors know your SSL setup is verified. The badge always shows your current grade and links to this report. Paste the snippet into your site footer:

    SSL grade badge for rakuten.co.jp← live preview, updates automatically
    <a href="https://httpsornot.com/report/rakuten.co.jp?utm_source=badge" target="_blank" rel="noopener">
  <img src="https://httpsornot.com/badge/rakuten.co.jp.svg" alt="SSL grade for rakuten.co.jp — checked by HTTPS Checker" height="20" loading="lazy" />
</a>

    Domain owner? If you want this report removed or made private, contact us.

    Check another domain