Skip to main content

Security report for gimmicklog.com

Technology · Japan

Medium risk. 10 critical or high findings in Email security, Security headers and 2 other checks.

Security score

57/100

Risk levelMedium

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

Gimmick log is a Japanese language technical blog established in 2019, focusing on web development topics such as jQuery, WordPress, JavaScript, web design, and marketing tools. The site targets web developers, designers, and marketers seeking practical tutorials and tips. It operates primarily as a content publishing platform monetized through advertising. Technically, the site is built on WordPress CMS, uses modern JavaScript libraries like jQuery, and integrates Google Analytics, Google Tag Manager, Microsoft Clarity, and Google Adsense for analytics and monetization. The site is hosted likely by GMO Internet Group, consistent with the domain registrar information. Security-wise, the site uses HTTPS with a valid SSL certificate and has domain transfer protection enabled. However, it lacks DNSSEC and important security headers, and no privacy or cookie policies are published, indicating compliance gaps. No contact information or incident response details are provided, limiting transparency. Overall, the site is functional, moderately secure, and professionally presented but would benefit from enhanced privacy compliance and security hardening.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

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

  3. 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

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

Keep watching gimmicklog.com

This scan found 27 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
62
Security headers
15
Email security
60
DNS health
70
Network security
100
GDPR outside view
35
Average
57

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

The website occupies a niche position as a Japanese technical blog focused on web technologies, catering to a specialized audience of developers and marketers. Its business model relies on content creation and advertising revenue. The site demonstrates consistent branding and content quality with a clear focus on educational material. The absence of direct contact information and formal policies suggests a small-scale operation, likely a personal or small team blog. The use of popular analytics and advertising platforms indicates an understanding of digital marketing practices. There are no indications of partnerships or subsidiaries. Growth potential exists through content expansion and improved compliance.

Security posture

The security posture is moderate. HTTPS is enforced, and the domain has clientTransferProhibited status, which protects against unauthorized transfers. However, the absence of DNSSEC and security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security reduces defense-in-depth. No vulnerability disclosure or incident response information is available, which is a gap in security transparency. The site uses third-party scripts for analytics and advertising, which may introduce privacy and security risks if not properly managed. No exposed sensitive data or known vulnerabilities were detected in the content. Overall, the site should improve its security policies and technical controls to enhance trust and compliance.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement essential security headers like Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish clear privacy and cookie policies to comply with GDPR and other regulations.
  4. Add a security.txt file or vulnerability disclosure page to facilitate responsible reporting.
  5. Provide contact information for incident response and general inquiries to improve transparency and trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
A blog site focused on sharing information about jQuery, WordPress, Web design, JavaScript, and marketing tools. It serves as a personal memo and knowledge sharing platform.
Key services
Technical articles, Tutorials, Tips on jQuery, WordPress, JavaScript, Web design, Marketing
Content quality
good
Branding
consistent

Technology

Stack
jQuery 3.2.1, Google Analytics, Google Tag Manager, Google Adsense, Microsoft Clarity, AMP for WP
Frameworks
WordPress
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status

Analytics and tracking

Services
Google Analytics, Microsoft Clarity
Tracking level
moderate
Privacy practices
poor

Advertising

Ad networks
Google Adsense
Tracking pixels
Microsoft Clarity
Marketing tools
Microsoft Clarity
Transparency
basic

Site quality

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

Key observations

  1. Website is a Japanese language technical blog focused on web development topics.
  2. No explicit privacy, cookie, or terms of service policies found.
  3. Uses multiple third-party analytics and advertising services.
  4. No contact emails or phone numbers explicitly provided.
  5. No security.txt or vulnerability disclosure information available.
  6. Domain is secured with HTTPS and has clientTransferProhibited status.
  7. No DNSSEC enabled, which is a recommended security improvement.
  8. Content is well structured with categories and popular posts.
  9. No signs of adult or questionable content.
Technical notes

Notes

The website is built on WordPress CMS with a theme and plugins that include AMP for WP, Table of Contents Plus, and WordPress Popular Posts. It uses jQuery 3.2.1 and loads scripts asynchronously for Google Analytics, Google Tag Manager, Microsoft Clarity, and Google Adsense. The site is mobile optimized with responsive design and uses modern CSS variables and gradients. Performance is moderate with some external dependencies on CDNs. Accessibility is basic but functional. SEO is supported by meta tags and structured data (JSON-LD BreadcrumbList). No critical technical debt or errors were detected in the HTML content. Hosting appears to be with GMO Internet Group, consistent with the registrar and DNS servers.
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 gimmicklog.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 gimmicklog.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.