Skip to main content

Security report for komegashi.org

Japanese Restaurant | Jersey City, NJ | Komegashi Too · Hospitality · United States

Medium risk. 7 critical or high findings in Email security, SSL/TLS and 2 other checks.

Security score

53/100

Risk levelMedium

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

Komegashi Too is a small local Japanese restaurant based in Jersey City, NJ, offering authentic Japanese cuisine and a pleasant dining experience. The website presents a professional and consistent brand image with a focus on hospitality services. The business appears to have been founded in 2013, although the domain registration is recent, indicating possible domain renewal or re-registration. The target audience is general consumers seeking Japanese dining in the local area. Technically, the website is built on WordPress CMS using the Flatsome theme, hosted with Cloudflare DNS and registered via NameCheap, Inc. The site shows moderate performance and good mobile optimization, with basic accessibility and SEO optimizations in place. The technical infrastructure is modern but could benefit from enhanced security headers and DNSSEC activation. From a security perspective, HTTPS is enabled, and the domain status clientTransferProhibited is set, which are positive indicators. However, the site lacks explicit privacy and cookie policies, security.txt or vulnerability disclosure pages, and advanced security headers. No signs of WAF blocking or security challenges were detected, and no vulnerabilities were found in the provided content. Overall, the security posture is moderate but could be improved to meet best practices and compliance requirements. The overall risk assessment is low to moderate, with recommendations to implement privacy and cookie policies, enhance security headers, enable DNSSEC, and provide a vulnerability disclosure mechanism. These steps will improve trust, compliance, and security maturity, supporting the business's online presence and customer confidence.

Scanned

NIS2 and GDPR posture

GDPR outside view
70/ 100 · Medium
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

7 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

  3. 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';…

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

Keep watching komegashi.org

This scan found 21 issues across 6 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. See sample alerts.

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
0
Security headers
15
Email security
60
DNS health
70
Network security
100
GDPR outside view
70
Average
53

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

Technical appendix

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

Business context

Business profile

Komegashi Too operates as a small hospitality business specializing in authentic Japanese cuisine in Jersey City, NJ. The business model centers on providing quality dining experiences to local customers. Market positioning is local and niche, targeting consumers interested in Japanese food. The website content and metadata reflect a consistent brand identity with a focus on quality and authenticity. There is no evidence of parent companies or subsidiaries, indicating an independent operation. The lack of visible trust indicators such as certifications or testimonials suggests opportunities to enhance credibility. The business appears stable with a long history since 2013, although the domain is newly registered, which may reflect a recent website update or migration. No partnerships or related domains were identified from the content.

Security posture

The website demonstrates a basic to moderate security posture. HTTPS is enforced, and the domain has clientTransferProhibited status, reducing risk of unauthorized domain transfers. However, the absence of key security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options is a gap. No privacy or cookie policies are present, which impacts compliance with GDPR and other privacy regulations. No incident response or security contact information is provided, limiting readiness for security incidents. No vulnerability disclosure or security.txt file is found, reducing transparency for security researchers. The site does not appear to use any WAF or advanced security mechanisms beyond Cloudflare DNS. Overall, the site is secure enough for a small restaurant website but should improve privacy compliance and security best practices to reduce risk and enhance trust.

Recommendations

  1. Implement a comprehensive privacy policy and make it easily accessible on the website.
  2. Add a cookie policy and consent mechanism to comply with privacy regulations.
  3. Enable and configure security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  4. Enable DNSSEC on the domain to improve DNS security.
  5. Create a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  6. Add clear contact information including security or abuse contacts for incident response.
  7. Improve accessibility features to enhance compliance and user experience.
  8. Consider adding trust indicators such as certifications, testimonials, or awards.
  9. Regularly audit and update third-party libraries and plugins to avoid vulnerabilities.
  10. Monitor website performance and optimize loading times for better user experience.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Japanese Restaurant | Jersey City, NJ | Komegashi Too
Description
Komegashi Too welcomes you to a pleasant and memorable dining experience. We feature authentic Japanese cuisine. We take pride in serving you the finest.
Key services
authentic Japanese cuisine, dining experience
Content quality
good
Branding
consistent

Technology

Stack
Cloudflare DNS, WordPress CMS, PHP, JavaScript
Frameworks
Flatsome theme
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is a small local Japanese restaurant site with authentic cuisine focus.
  2. No privacy, cookie, or terms of service policies found on the homepage HTML.
  3. No contact emails or phone numbers explicitly found in the HTML content provided.
  4. No social media links explicitly found in the HTML content provided.
  5. Website uses WordPress CMS with Flatsome theme and Cloudflare DNS.
  6. HTTPS is enabled and domain status clientTransferProhibited is set.
  7. No security.txt or vulnerability disclosure page detected.
  8. No advertising or tracking scripts detected in the provided HTML snippet.
  9. Content is safe and suitable for general audiences.
  10. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website is built on WordPress CMS with the Flatsome theme, a popular e-commerce and business theme. It uses Cloudflare DNS services and is registered through NameCheap, Inc. The site is served over HTTPS, indicating a valid SSL/TLS certificate. The HTML content is well-structured with proper meta tags for SEO and social media sharing (Open Graph and Twitter cards). The site includes JSON-LD structured data describing the organization and webpage, enhancing search engine understanding. Performance is moderate with good mobile optimization. Accessibility is basic but could be improved. No heavy advertising or tracking scripts were detected, indicating a clean technical environment. The site lacks advanced security headers and privacy compliance features, which are technical debt areas to address. Overall, the technical infrastructure is modern and suitable for a small hospitality business website.
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 komegashi.org. 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 komegashi.org.

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.