Skip to main content

Security report for okanenohonne.com

オカネノホンネ｜保険・金融メディア · Finance · Japan

Medium risk. 8 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

63/100

Risk levelMedium

0–100, higher is better. How it is calculated

オカネノホンネ is a Japanese online media platform specializing in insurance, finance, investment, loans, and life planning content. It targets Japanese individuals seeking clear and honest financial information. The site is powered by WordPress and uses common SEO and UI plugins to enhance user experience and search visibility. The technical infrastructure includes nginx web server, jQuery, Slick Carousel, and YouTube API integrations. Hosting is provided by Xserver, a Japanese hosting provider. Security posture shows a valid SSL certificate but lacks modern TLS protocol support and advanced security headers. No cookie consent or detailed privacy compliance mechanisms are present, though a basic privacy policy is linked on the parent company’s domain. Advertising and analytics are managed via Google Adsense and Google Analytics respectively.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

8 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

Need hands-on remediation? Email guard@offseq.com

Keep watching okanenohonne.com

This scan found 19 issues across 5 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
70
Security headers
15
Email security
100
DNS health
85
Network security
85
GDPR outside view
25
Average
63

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention okanenohonne.com, from OffSeq Breach.

No leaked records found

Breach holds no records for okanenohonne.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The website operates as a niche financial media outlet under DIGITALIO, Inc., focusing on insurance and personal finance topics for the Japanese market. Its business model revolves around content marketing, advertising revenue, and possibly affiliate partnerships. The site maintains a consistent brand and good content quality, appealing to individuals interested in financial planning and insurance products. Partnerships with DIGITALIO and PeX.jp suggest a broader ecosystem for content and marketing. The absence of direct contact information on the site indicates a primarily informational and media-focused operation rather than direct sales or customer service.

Security posture

The current security maturity is basic with a valid SSL certificate but no TLS 1.2 or higher enabled, which is a significant gap. DNSSEC is not enabled, and no security.txt or vulnerability disclosure policies are found. The site lacks advanced security headers and cookie consent mechanisms, which may impact GDPR and other privacy compliance. PHP warnings visible in the menu code could expose minor information leakage risks. Incident response and security policies are not publicly documented. Overall, the security posture is adequate for a content site but requires improvements to meet modern standards and regulatory compliance.

Recommendations

  1. Enable TLS 1.2 or higher protocols to secure HTTPS connections properly.
  2. Implement HSTS header with includeSubDomains and preload to prevent protocol downgrade attacks.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Enable DNSSEC to protect DNS integrity and prevent spoofing.
  5. Fix PHP warnings and errors to avoid information leakage and improve backend stability.
  6. Implement a cookie consent mechanism to comply with privacy regulations.
  7. Publish explicit security and incident response policies to enhance trust.
  8. Consider adding contact information or a dedicated contact page for user support.
Technical notes

Notes

The website uses a standard WordPress CMS with a custom theme (muum_tcd085) and several plugins including All in One SEO and Table of Contents Plus. Frontend technologies include jQuery, Slick Carousel, and YouTube IFrame API for media content. Hosting is on Xserver with nginx as the web server. Performance is fast with no reported load times or resource counts, indicating efficient delivery. Mobile optimization is good with responsive CSS and mobile-specific images. SEO is enhanced by structured data (JSON-LD) and Open Graph tags. However, the SSL configuration is incomplete with no TLS protocols enabled, which is a critical technical risk. Minor PHP warnings in theme files indicate some technical debt. Overall, the technical infrastructure is solid but requires security modernization.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with okanenohonne.com. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review okanenohonne.com.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.