Security - https://rakuten.com BeaverCheck Audit

F

Subresource Integrity

Action

0 of 16 external resources have SRI

FIX

0 of 16 external resources have SRI

External script from www.google-analytics.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: //www.google-analytics.com/analytics.js

External link from static.rakuten.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://static.rakuten.com/assets/ac/_next/static/css/5147e23cf8287c46.css

External script from static.rakuten.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://static.rakuten.com/assets/ac/_next/static/chunks/polyfills-c67a75d1b6f99dc8.js

External script from static.rakuten.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://static.rakuten.com/assets/ac/_next/static/chunks/webpack-9d1745088be0aa12.js

External script from static.rakuten.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://static.rakuten.com/assets/ac/_next/static/chunks/main-b1b7a9bc34dbf47a.js

External script from static.rakuten.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://static.rakuten.com/assets/ac/_next/static/chunks/pages/_app-3d08c9ea0cf0791c.js

External script from static.rakuten.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://static.rakuten.com/assets/ac/_next/static/chunks/dcaa923d-a736452b7ccfd11e.js

External script from static.rakuten.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://static.rakuten.com/assets/ac/_next/static/chunks/3424-745a98fafda91817.js

External script from static.rakuten.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://static.rakuten.com/assets/ac/_next/static/chunks/8838-eed97f3c6eeafb38.js

External script from static.rakuten.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://static.rakuten.com/assets/ac/_next/static/chunks/1468-fe0964eaede6b580.js

External script from static.rakuten.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://static.rakuten.com/assets/ac/_next/static/chunks/pages/index-7cec028592c394ad.js

External script from static.rakuten.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://static.rakuten.com/assets/ac/_next/static/7ki86u0WjShoxeU2nNM7U/_buildManifest.js

External script from static.rakuten.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://static.rakuten.com/assets/ac/_next/static/7ki86u0WjShoxeU2nNM7U/_ssgManifest.js

External script from static.rakuten.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://static.rakuten.com/assets/ac/_next/static/chunks/schemaFilter.9dcbb79e21e331f7.js

External script from www.datadoghq-browser-agent.com lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: https://www.datadoghq-browser-agent.com/datadog-logs-v3.js

External script from connect.facebook.net lacks integrity attribute

Without SRI, if this CDN is compromised, attackers could inject malicious code.

Got: //connect.facebook.net/en_US/sdk.js

SRI Coverage 0 / 16 of external resources have integrity hashes

Tag	Domain	Integrity
<script>	www.google-analytics.com	✗ Missing
<link>	static.rakuten.com	✗ Missing
<script>	static.rakuten.com	✗ Missing
<script>	static.rakuten.com	✗ Missing
<script>	static.rakuten.com	✗ Missing
<script>	static.rakuten.com	✗ Missing
<script>	static.rakuten.com	✗ Missing
<script>	static.rakuten.com	✗ Missing
<script>	static.rakuten.com	✗ Missing
<script>	static.rakuten.com	✗ Missing
<script>	static.rakuten.com	✗ Missing
<script>	static.rakuten.com	✗ Missing
<script>	static.rakuten.com	✗ Missing
<script>	static.rakuten.com	✗ Missing
<script>	www.datadoghq-browser-agent.com	✗ Missing
<script>	connect.facebook.net	✗ Missing

D

Permissions-Policy

Action

No header set

FIX

No header set

No Permissions-Policy header

Consider adding a Permissions-Policy header to restrict browser feature access from embedded content.

No Permissions-Policy header set.

Without this header, embedded iframes can request access to sensitive device features.

Suggested header

Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=()

D

security.txt

Action

No /.well-known/security.txt published

FIX

security.txt

No security.txt found at /.well-known/security.txt

C

Security Headers

Action

5 of 10 headers properly configured

REVIEW

5 of 10 headers properly configured

Strict-Transport-Security is properly configured (consider adding preload)

Got: max-age=31536000; includeSubDomains

X-Content-Type-Options is properly configured

Got: nosniff

X-Frame-Options is properly configured

Got: SAMEORIGIN

Referrer-Policy header is missing

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: strict-origin-when-cross-origin

Permissions-Policy header is missing

Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.

Expected: geolocation=(), camera=(), microphone=()

Content-Security-Policy is present

Got: script-src 'none'; object-src 'none'; default-src 'none'; base-uri 'none'; form-…

Cross-Origin-Opener-Policy header is missing

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin

Cross-Origin-Embedder-Policy header is missing

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp

X-Powered-By header is not present

Server header reveals version information

The Server header discloses the software version, aiding attackers in targeting known vulnerabilities. Remove the version number.

Got: nginx/1.28.0

Controls how much referrer information is sent with requests. Set to 'strict-origin-when-cross-origin' or stricter.

Expected: strict-origin-when-cross-origin

Why this matters

Default browser behavior leaks full URLs (including query params and tokens) to every third-party resource — set a strict policy.

Learn more ▾

Without a Referrer-Policy header, browsers send the full referring URL with images, scripts, and fonts loaded from third-party origins. URLs containing tokens, user IDs, or session params end up in third-party logs. Set `Referrer-Policy: strict-origin-when-cross-origin` (or stricter) to limit leakage.

Source: MDN / W3C

Controls which browser features (camera, microphone, geolocation) are allowed. Set it to restrict unused features.

Expected: geolocation=(), camera=(), microphone=()

Why this matters

Permissions-Policy locks down browser APIs you don't use — without it, every page can request camera/mic/geolocation if XSS lands.

Learn more ▾

By default every page can request the camera, microphone, geolocation, payment APIs, and dozens more. Permissions-Policy turns off the ones you don't need so a future bug can't quietly start using them. It's a defense-in-depth header — one line, big surface reduction.

Source: MDN / W3C

COOP isolates your browsing context, preventing cross-origin side-channel attacks. Set to 'same-origin'.

Expected: same-origin

Why this matters

COOP isolates your top-level browsing context from cross-origin windows — without it, popup-based side-channel attacks remain possible.

Learn more ▾

Cross-Origin-Opener-Policy: same-origin prevents cross-origin pages from sharing a browsing-context group with yours. This blocks cross-window references that enable Spectre-style timing attacks and tab-nabbing. Required if you want to enable SharedArrayBuffer.

Source: MDN / web.dev

COEP prevents loading cross-origin resources without explicit permission. Required for SharedArrayBuffer and high-resolution timers.

Expected: require-corp

Why this matters

COEP enforces that all embedded resources opt-in to cross-origin embedding — required for cross-origin isolation features.

Learn more ▾

Cross-Origin-Embedder-Policy: require-corp ensures every embedded resource (script, iframe, image) explicitly allows being loaded cross-origin. Combined with COOP, this enables the cross-origin-isolated context that unlocks SharedArrayBuffer, high-resolution timers, and other powerful APIs.

Source: MDN / web.dev

The Server header discloses the software version, aiding attackers in targeting known vulnerabilities. Remove the version number.

Why this matters

Server: nginx/1.18.0 tells attackers exactly which CVEs to test — strip the version string.

Learn more ▾

Server version disclosure helps attackers select exploits matching your stack. Configure your server to omit the version (nginx: `server_tokens off;`, Apache: `ServerTokens Prod`). Doesn't fix vulnerabilities but removes the easy reconnaissance step.

Source: OWASP

B

CORS Configuration

No CORS headers

REVIEW

No CORS headers

No CORS headers present — secure default

CORS Configuration ✓ Secure

No CORS headers detected.

Cross-origin requests are blocked by browser same-origin policy.

Origin reflection test

Some servers mirror the request Origin header, which can be exploited. Test manually:

curl -sI -H "Origin: https://evil.com" <url> | grep -i access-control

A

Content Security Policy

7 of 10 CSP checks passed

PASS

7 of 10 CSP checks passed

Raw CSP policy

Got: script-src 'none'; object-src 'none'; default-src 'none'; base-uri 'none'; form-action 'none'; report-to csp-endpoint;

default-src directive is set

Got: default-src 'none'

No 'unsafe-inline' in script source

No 'unsafe-eval' in script source

No wildcard in script source

object-src is set to 'none'

Got: object-src 'none'

base-uri is properly restricted

Got: base-uri 'none'

frame-ancestors directive is missing

frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.

Expected: frame-ancestors 'self'

form-action directive is set

Got: form-action 'none'

upgrade-insecure-requests is not set

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests

frame-ancestors controls who can embed your page, preventing clickjacking. Set it to 'self' or 'none'.

Expected: frame-ancestors 'self'

Why this matters

Security gaps expose your site and users to attacks, eroding trust.

This directive upgrades HTTP resources to HTTPS automatically, preventing mixed content.

Expected: upgrade-insecure-requests

Why this matters

Without upgrade-insecure-requests, any HTTP subresource link survives as a mixed-content warning instead of auto-upgrading.

Learn more ▾

Adding `upgrade-insecure-requests` to your CSP turns every http:// subresource fetch into https:// at the browser layer. One-line defense against accidental mixed content from legacy links or third-party widgets.

Source: MDN CSP

Parsed Policy

script-src 'none'

object-src 'none'

default-src 'none'

base-uri 'none'

form-action 'none'

report-to csp-endpoint

A+

TLS & Certificates

TLS 1.2, 7 checks passed

PASS

TLS 1.2, 7 checks passed

TLS 1.2 is used

Got: TLS 1.2

TLS 1.3 is not negotiated

TLS 1.3 offers improved performance and security. Consider enabling it.

Got: TLS 1.2

Strong cipher suite is used

Got: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

HTTP/2 is not negotiated

HTTP/2 provides multiplexing and header compression for better performance.

Got: http/1.1

Certificate is valid (expires in 145 days)

Got: 2026-09-08T23:59:59Z

Certificate chain has 3 certificates

Certificate uses modern signature algorithm

Got: SHA256-RSA

Certificate covers 2 domain(s)

Got: *.rakuten.com, rakuten.com

Certificate is issued by a trusted CA

Got: CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US

TLS 1.3 offers improved performance and security. Consider enabling it.

Why this matters

TLS 1.3 not in use — connection falls back to 1.2 and pays the extra round-trip.

Learn more ▾

Most clients prefer TLS 1.3 if both sides support it. If your server has TLS 1.3 enabled but it's not being negotiated, check for a downgrade-attack mitigation issue or a misconfigured cipher list. nginx ≥ 1.13.0 and OpenSSL ≥ 1.1.1 support TLS 1.3.

Source: RFC 8446 / Mozilla SSL Config

HTTP/2 provides multiplexing and header compression for better performance.

Why this matters

HTTP/1.1 forces the browser to make sequential requests, multiplying latency on every page.

Learn more ▾

HTTP/2 (and HTTP/3) multiplex many requests over a single connection, eliminating head-of-line blocking. HTTP/1.1 forces the browser to either queue requests or open many parallel connections — both worse. Most modern web servers support HTTP/2 with one config line.

Source: MDN Web Docs

Connection

Protocol

TLS 1.2

Cipher Suite

TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

HTTP Version

HTTP/1.1

Certificate Chain

Leaf Certificate

Subject CN=*.rakuten.com,O=Rakuten Group\, Inc.,L=Setagaya-ku,ST=Tokyo,C=JPIssuer CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=USValid 2025-08-19T00:00:00Z → 2026-09-08T23:59:59ZExpires in 145 days SANs *.rakuten.com, rakuten.comSignature SHA256-RSASerial 4bb2563acbf3b4a3c42f56f9f2b7c0a

Intermediate (CA Certificate)

Subject CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=USIssuer CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=USValid 2021-03-30T00:00:00Z → 2031-03-29T23:59:59ZExpires in 1808 days Signature SHA256-RSASerial cf5bd062b5602f47ab8502c23ccf066

Intermediate (CA Certificate)

Subject CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=USIssuer CN=DigiCert Global Root CA,OU=www.digicert.com,O=DigiCert Inc,C=USValid 2023-08-15T00:00:00Z → 2031-11-09T23:59:59ZExpires in 2033 days Signature SHA256-RSASerial 446c1ecbb8462b5a91772f9aa18e67b

A

Cookie Security

1 cookies analyzed, 1 checks passed

PASS

1 cookies analyzed, 1 checks passed

Cookie 'parked' has the Secure flag

Cookie 'parked' is missing the HttpOnly flag

Without HttpOnly, this cookie can be accessed by JavaScript, making it vulnerable to XSS-based theft.

Cookie 'parked' has no SameSite attribute

Without an explicit SameSite attribute, browser default behavior varies. Set SameSite=Lax or Strict.

1 cookies analyzed 2 warnings

Name	Secure	HttpOnly	SameSite	Size	Issues
parked	✓	✗	—	10 B	2

A+

JS Library Vulnerabilities

No known vulnerabilities

PASS

No known vulnerabilities

No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+

Information Leakage

No exposures

PASS

No exposures

No security.txt found

Consider adding a security.txt at /.well-known/security.txt.

No sensitive files exposed

No sensitive files exposed — all paths returned 404.

Path	Status	Category	Risk
/.git/HEAD	✓ Not found	Version Control	—
/.git/config	✓ Not found	Version Control	—
/.svn/entries	✓ Not found	Version Control	—
/.env	✓ Not found	Configuration	—
/.env.local	✓ Not found	Configuration	—
/.env.production	✓ Not found	Configuration	—
/wp-config.php	✓ Not found	Configuration	—
/.htaccess	✓ Not found	Configuration	—
/phpinfo.php	✓ Not found	Debug	—
/server-status	✓ Not found	Debug	—
/server-info	✓ Not found	Debug	—
/.well-known/security.txt	✓ Not found	Security Policy	—

A+

Email Security

DMARC: reject

PASS

DMARC: reject

DMARC policy is reject — strongest protection

DMARC

Policy reject — strongest protection Record v=DMARC1; p=reject; rua=mailto:dmarc-report-a@rx.rakuten.co.jp

A

Transport Security

HTTP/3, HSTS, and TLS version analysis

PASS

HTTP/3, HSTS, and TLS version analysis

HTTP/3 (QUIC) not advertised

HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.

HSTS enabled (includeSubDomains)