Skip to main content

Security report for moe.best

Privacy service provided by Withheld for Privacy ehf · Technology · Iceland

Medium risk. 7 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

The website moe.best is a personal blog primarily focused on technology, software projects, tutorials, and moe/anime culture. It serves a niche audience of technology enthusiasts and fans of Japanese pop culture. The blog is powered by the Typecho CMS and uses a modern but lightweight tech stack including Bootstrap and jQuery. The site is hosted behind Cloudflare DNS but the exact hosting provider is not disclosed. The domain is privacy protected and was registered in 2018, consistent with the blog's content age and activity. The site uses HTTPS and includes analytics from Google and Baidu, but lacks formal privacy and cookie policies, which is a compliance gap.

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

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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

Keep watching moe.best

This scan found 25 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. 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
59
Security headers
30
Email security
85
DNS health
70
Network security
100
GDPR outside view
35
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 moe.best, from OffSeq Breach.

Total records
7
Employees
0
Customers
7
Third parties
0
Weak passwords
0%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for moe.best.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Brand lookalikes

Add-on

Domains that imitate moe.best and could be used for phishing or spoofed email, tracked in OffSeq Breach.

Tracked
14
Registered
14
Resolving
14
High or critical
0

Last checked 2026-06-19

Masked preview

  • mo•••.bestMediumbitsquatting
  • mm•••.bestMediumbitsquatting
  • mo•••.bestMediumbitsquatting

See the full lookalike list

A one-off add-on that lists up to 20 of the highest-risk lookalikes of moe.best with registration, mail-server, certificate and DNS signals.

Select it in the checkout above.

Lookalike data refreshes continuously. Monitoring on Breach alerts you when a variant is registered, gains a mail server or starts serving HTTPS.

Technical appendix

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

Business context

Business profile

The blog operates as a small-scale content publishing platform with a focus on sharing open source projects, tutorials, and affiliate hosting recommendations. It targets a specialized audience interested in technology and moe culture. The business model appears to be content-driven with monetization through affiliate links for VPS hosting. The site maintains partnerships or references to related domains such as lolicon.app and arkn.lolicon.app, indicating an ecosystem of related projects. The blog has a consistent branding and a moderate level of trust indicators, though it lacks formal certifications or business registrations.

Security posture

The website demonstrates a basic security posture with HTTPS enabled and domain transfer protection. However, it lacks DNSSEC and important HTTP security headers, which could improve protection against certain attacks. No vulnerability disclosure or incident response information is provided, and no security.txt file is found. The site does not expose sensitive data in the HTML and uses standard security practices for forms. Overall, the security maturity is moderate but could be improved with additional controls and transparency.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy to improve compliance and user trust.
  2. Enable DNSSEC on the domain to enhance DNS security.
  3. Add HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Create and publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Consider adding direct contact emails or verified contact information for business and security inquiries.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Privacy service provided by Withheld for Privacy ehf
Description
Personal blog focused on technology, software projects, tutorials, and moe-themed content.
Key services
Blog articles, Open source projects, Tutorials, Affiliate hosting recommendations
Content quality
good
Branding
consistent

Technology

Stack
Typecho CMS, Bootstrap 3.3.7, jQuery 2.2.4, MathJax 2.7.9, Cloudflare DNS, Google Analytics, Baidu Analytics
Frameworks
Bootstrap
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
65/100
Good practices seen
  • HTTPS enforced
  • Client transfer prohibited domain status
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Baidu Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Baidu Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is a personal blog focused on technology and moe culture.
  2. No privacy, cookie, or terms of service policies found.
  3. Contact available only via contact page form and login form; no direct emails or phone numbers found.
  4. Uses Typecho CMS with Bootstrap and jQuery.
  5. Includes Google and Baidu analytics scripts.
  6. No DNSSEC enabled; domain status clientTransferProhibited.
  7. No security.txt or vulnerability disclosure found.
  8. No explicit security headers detected in HTML content.
  9. Content is safe and suitable for general audiences.
  10. No WAF or blocking detected; content fully accessible.
Technical notes

Notes

The site uses a well-known CMS (Typecho) with Bootstrap and jQuery for frontend styling and interactivity. It loads external resources from reliable CDNs and includes MathJax for mathematical rendering. The site is mobile optimized and has good SEO metadata. Performance is moderate with asynchronous loading of analytics scripts. There is some technical debt in the form of missing DNSSEC and security headers. The site could benefit from modernization of JavaScript libraries and enhanced accessibility features.
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 moe.best. 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 moe.best.

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.