Skip to content
https://ameblo.jp

Security

· 12 checks — HTTP headers, CSP, TLS handshake, and cookie hygiene rolled into one auditable list.
SCORE
70
GRADE
C
FIX
4
REVIEW
4
PASS
4
INFO
0
Checks
12
4 PASS 4 REVIEW 4 FIX
D
Security Headers
Action
5 of 10 headers properly configured
FIX
5 of 10 headers properly configured
Critical::
HSTS header is missing
Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.
Expected: max-age=31536000; includeSubDomains
Info::
X-Content-Type-Options is properly configured
Got: nosniff
Warning::
X-Frame-Options header is missing
This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.
Expected: DENY
Warning::
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
Info::
Permissions-Policy is set
Got: ch-ua-full=*
Info::
Content-Security-Policy is present
Got: upgrade-insecure-requests
Warning::
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
Warning::
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
Info::
X-Powered-By header is not present
Info::
Server header is not present

Strict-Transport-Security forces browsers to use HTTPS, preventing downgrade attacks. Add the header with a max-age of at least 1 year.

Expected: max-age=31536000; includeSubDomains
Why this matters

Without HSTS, a network attacker can downgrade the very first connection to HTTP and steal the user's session.

Learn more ▾

HSTS tells browsers 'never speak HTTP to this domain again.' Without it, a network attacker (public WiFi, malicious ISP, hostile DNS) intercepts the first HTTP attempt and serves a downgraded version of your site. One header, big surface reduction.

Source: RFC 6797 / OWASP

This header prevents clickjacking by controlling who can embed your page in a frame. Set it to DENY or SAMEORIGIN.

Expected: DENY
Why this matters

Without frame protection, your site can be embedded in a hostile page and used for clickjacking.

Learn more ▾

Clickjacking overlays your site under a transparent malicious page so users click invisible buttons. Setting X-Frame-Options: DENY (or a modern frame-ancestors CSP directive) blocks the embedding entirely. There's almost never a legitimate reason to allow it.

Source: OWASP / MDN

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

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

F
Subresource Integrity
Action
0 of 20 external resources have SRI
FIX
0 of 20 external resources have SRI
Warning::
External script from www.googletagmanager.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.googletagmanager.com/gtag/destination?id=AW-608763171&cx=c&gtm=4e64f0
Warning::
External script from ln.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: //ln.ameba.jp/fuse.js
Warning::
External script from www.googletagmanager.com lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://www.googletagmanager.com/gtag/js?id=G-HQSMEN0RQG&cx=c&gtm=4e64f0
Warning::
External link from c.stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://c.stat100.ameba.jp/ameblo/symbols/v3.24.0/fonts/ameba-symbols.css
Warning::
External link from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/css/0c0026eb20939fae.css
Warning::
External link from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/css/076f1a3e8702e85e.css
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/chunks/polyfills-c67a75d1b6f99dc8.js
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/chunks/webpack-9b3c9204b9be25ec.js
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/chunks/framework-24fda4117f092221.js
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/chunks/main-9c5dd558e4dc80e5.js
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/chunks/pages/_app-9c6a2c95cf72d0ee.js
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/chunks/537-85a5f4af8dfebcc4.js
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/chunks/438-ff01bd82a91e4ca0.js
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/chunks/207-2c6122a0ff6fad1e.js
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/chunks/441-3ebaef9854842f0d.js
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/chunks/421-8d83f79d793f08af.js
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/chunks/338-fe1ec5b81d564b83.js
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/chunks/pages/index-ff9728a8e546a00c.js
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/20251212-4180222/_buildManifest.js
Warning::
External script from stat100.ameba.jp lacks integrity attribute
Without SRI, if this CDN is compromised, attackers could inject malicious code.
Got: https://stat100.ameba.jp/ameblo/portal/20251212-4180222/_next/static/20251212-4180222/_ssgManifest.js
SRI Coverage 0 / 20 of external resources have integrity hashes
TagDomainIntegrity
<script>www.googletagmanager.com✗ Missing
<script>ln.ameba.jp✗ Missing
<script>www.googletagmanager.com✗ Missing
<link>c.stat100.ameba.jp✗ Missing
<link>stat100.ameba.jp✗ Missing
<link>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
<script>stat100.ameba.jp✗ Missing
D
Email Security
Action
DMARC: none
FIX
DMARC: none
Warning::
DMARC policy is none — monitoring only
This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject.
DMARC
Policy none — monitoring only, does not block spoofing Record v=DMARC1; p=none

This only monitors, it doesn't block spoofed emails. Change to p=quarantine or p=reject.

Why this matters

DMARC p=none collects reports but doesn't actually block spoofed mail — phishing emails still reach inboxes.

Learn more ▾

DMARC's three policies are p=none (monitor only), p=quarantine (mark as spam), and p=reject (bounce). Most domains start at p=none to gather data, but stay there forever, leaving spoofers unblocked. After 30 days of clean DMARC reports, graduate to p=quarantine, then p=reject.

Source: DMARC.org / NIST

D
security.txt
Action
No /.well-known/security.txt published
FIX

security.txt

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

C
Content Security Policy
Action
2 of 10 CSP checks passed
REVIEW
2 of 10 CSP checks passed
Info::
Raw CSP policy
Got: upgrade-insecure-requests
Warning::
default-src directive is missing
default-src provides a fallback for other directives. Set it to restrict default resource loading.
Expected: default-src 'self'
Info::
No script-src or default-src to check for 'unsafe-inline'
Info::
No script-src or default-src to check for 'unsafe-eval'
Info::
No script-src or default-src to check for wildcard
Info::
object-src falls back to default-src
Warning::
base-uri directive is missing
Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.
Expected: base-uri 'self'
Warning::
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'
Warning::
form-action directive is missing
form-action restricts where forms can submit data, preventing form hijacking.
Expected: form-action 'self'
Info::
upgrade-insecure-requests is enabled

default-src provides a fallback for other directives. Set it to restrict default resource loading.

Expected: default-src 'self'
Why this matters

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

Without base-uri, attackers can inject a <base> tag to hijack relative URLs. Set it to 'self' or 'none'.

Expected: base-uri 'self'
Why this matters

Missing base-uri in CSP leaves a base-tag injection attack path open even on otherwise strict policies.

Learn more ▾

A common omission: developers add CSP for script-src and frame-ancestors but forget base-uri. The result is a CSP that looks strict but lets an attacker rewrite every URL on the page via <base href>. Add `base-uri 'self'` to close the gap.

Source: MDN CSP

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.

form-action restricts where forms can submit data, preventing form hijacking.

Expected: form-action 'self'
Why this matters

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

Parsed Policy

upgrade-insecure-requests
C
Permissions-Policy
Action
1 directives, 5 missing
REVIEW
1 directives, 5 missing
Info::
ch-ua-full=*
Info::
camera not restricted
Consider adding camera=() to block camera access from embedded content.
Info::
microphone not restricted
Consider adding microphone=() to block microphone access from embedded content.
Info::
geolocation not restricted
Consider adding geolocation=() to block geolocation access from embedded content.
Info::
payment not restricted
Consider adding payment=() to block payment access from embedded content.
Info::
usb not restricted
Consider adding usb=() to block usb access from embedded content.

Raw Header

ch-ua-full=*

Feature Permissions

Blocked Self Only Unrestricted Not Set
ch-ua-full Unrestricted
camera Not Set
microphone Not Set
geolocation Not Set
payment Not Set
usb Not Set
B
CORS Configuration
No CORS headers
REVIEW
No CORS headers
Info::
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
B
Transport Security
HTTP/3, HSTS, and TLS version analysis
REVIEW
HTTP/3, HSTS, and TLS version analysis
Info::
HTTP/3 (QUIC) not advertised
HTTP/3 eliminates head-of-line blocking. If your CDN supports it, consider enabling it.
Warning::
Missing Strict-Transport-Security header
HSTS tells browsers to only use HTTPS, preventing SSL stripping attacks.
A
TLS & Certificates
TLS 1.2, 7 checks passed
PASS
TLS 1.2, 7 checks passed
Info::
TLS 1.2 is used
Got: TLS 1.2
Info::
TLS 1.3 is not negotiated
TLS 1.3 offers improved performance and security. Consider enabling it.
Got: TLS 1.2
Info::
Strong cipher suite is used
Got: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
Info::
HTTP/2 is not negotiated
HTTP/2 provides multiplexing and header compression for better performance.
Got: http/1.1
Info::
Certificate is valid (expires in 13 days)
Got: 2026-04-30T14:59:00Z
Warning::
Certificate expires soon (13 days remaining)
Renew the certificate before it expires to avoid browser warnings.
Got: 2026-04-30T14:59:00Z
Info::
Certificate chain has 2 certificates
Info::
Certificate uses modern signature algorithm
Got: SHA256-RSA
Info::
Certificate covers 2 domain(s)
Got: *.ameblo.jp, ameblo.jp
Info::
Certificate is issued by a trusted CA
Got: CN=Cybertrust Japan SureServer CA G4,O=Cybertrust Japan Co.\, Ltd.,C=JP

Renew the certificate before it expires to avoid browser warnings.

Why this matters

Cert expiry within the renewal window — fix now while there's no user impact, instead of after expiry when there's a full outage.

Learn more ▾

Most CAs recommend renewal at 30 days remaining. Inside that window, schedule the renewal immediately and verify auto-renewal is configured if applicable. Don't wait until 7 days; weekend / holiday timing can leave you exposed.

Source: Let's Encrypt / CA renewal best practice

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=*.ameblo.jp,O=CyberAgent\, Inc.,L=Shibuya-ku,ST=Tokyo,C=JPIssuer CN=Cybertrust Japan SureServer CA G4,O=Cybertrust Japan Co.\, Ltd.,C=JPValid 2025-04-01T01:01:00Z → 2026-04-30T14:59:00ZExpires in 13 days — expiring soon! SANs *.ameblo.jp, ameblo.jpSignature SHA256-RSASerial 6334c9b0aacf80b4ce94a6ba715cd91f47059c58
Intermediate (CA Certificate)
Subject CN=Cybertrust Japan SureServer CA G4,O=Cybertrust Japan Co.\, Ltd.,C=JPIssuer OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JPValid 2023-12-13T05:57:30Z → 2029-05-29T05:00:39ZExpires in 1138 days Signature SHA256-RSASerial 22b9b1a074641857f7a01332db42b9ec
A+
Cookie Security
No cookies set — no cookie security risks
PASS
No cookies set — no cookie security risks
Info::
No cookies set — no cookie security risks

No cookies detected — no cookie security risks to report.

A+
JS Library Vulnerabilities
No known vulnerabilities
PASS
No known vulnerabilities
Info::
No known JavaScript library vulnerabilities detected

No known JavaScript library vulnerabilities detected.

A+
Information Leakage
No exposures
PASS
No exposures
Info::
No security.txt found
Consider adding a security.txt at /.well-known/security.txt.
Info::
No sensitive files exposed

No sensitive files exposed — all paths returned 404.

PathStatusCategoryRisk
/.git/HEAD✓ Not foundVersion Control—
/.git/config✓ Not foundVersion Control—
/.svn/entries✓ Not foundVersion Control—
/.env✓ Not foundConfiguration—
/.env.local✓ Not foundConfiguration—
/.env.production✓ Not foundConfiguration—
/wp-config.php✓ Not foundConfiguration—
/.htaccess✓ Not foundConfiguration—
/phpinfo.php✓ Not foundDebug—
/server-status✓ Not foundDebug—
/server-info✓ Not foundDebug—
/.well-known/security.txt✓ Not foundSecurity Policy—
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback