Skip to main content

Security report for ncheckout.dev

Other · N/a

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

Security score

66/100

Risk levelMedium

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

The website ncheckout.dev is currently inaccessible beyond a Cloudflare Access 403 Forbidden page, indicating that it is protected by a Web Application Firewall (WAF) and requires proper authorization to view content. Due to this restriction, no business-related content, contact information, or policies are available for analysis. The site appears to be in a development or restricted access phase, with no visible public-facing information. The technical infrastructure includes Cloudflare Access as a security layer, but no further details on hosting or CMS are available. The security posture cannot be fully assessed due to lack of content access, but the presence of Cloudflare Access indicates some level of security enforcement. Overall, the site currently presents a high risk for external users due to lack of accessible information and transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 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. 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 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

    • 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 ncheckout.dev

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
75
Security headers
55
Email security
40
DNS health
75
Network security
100
GDPR outside view
50
Average
66

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 ncheckout.dev, from OffSeq Breach.

No leaked records found

Breach holds no records for ncheckout.dev 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

No business intelligence can be derived from the current accessible content. The domain is privacy protected in WHOIS, and no registrant or company information is publicly available. There are no visible partnerships, certifications, or market positioning details. The domain name suggests a payment or checkout related service, but this cannot be confirmed. The lack of public content and contact details limits any competitive or market analysis.

Security posture

The security posture is partially indicated by the use of Cloudflare Access WAF, which blocks unauthorized access and protects the site from unauthorized viewing. However, no security headers or SSL configuration details are visible. No vulnerabilities or security best practices can be confirmed due to lack of content access. The absence of privacy and cookie policies also indicates compliance gaps. Incident response and vulnerability disclosure mechanisms are not visible.

Recommendations

  1. Provide authorized access or a public landing page to allow content analysis and user engagement.
  2. Publish clear privacy, cookie, and terms of service policies to improve compliance and trust.
  3. Add visible contact information and incident response channels for transparency and support.
  4. Implement and expose security headers and ensure HTTPS is enforced and visible.
  5. Consider publishing a security.txt file or vulnerability disclosure policy to enhance security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Cloudflare detected. The website content is blocked by Cloudflare Access WAF, showing a 403 Forbidden error page with no access to actual site content. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
moderate

Technology

Stack
Cloudflare Access
Mobile
basic
Accessibility
basic
SEO
poor

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is inaccessible due to Cloudflare Access 403 Forbidden page.
  2. No visible business or contact information on the page.
  3. No privacy, cookie, or terms of service policies detected.
  4. No forms or data collection mechanisms present.
  5. No external links or social media references found.
  6. No analytics or advertising scripts detected.
  7. Page is minimal and serves as a security gate rather than a business site.
  8. Logo present is a Cloudflare Access logo, not company branding.
  9. No SEO or metadata beyond basic HTML title and meta tags.
  10. No structured data (JSON-LD or Open Graph) found.
Technical notes

Notes

The site is hosted behind Cloudflare Access, which acts as a security gateway blocking unauthorized users. No CMS or platform is detectable. The HTML content is minimal and serves only as an error page. No analytics, advertising, or tracking scripts are present. The site lacks SEO metadata and accessibility features. Mobile optimization is basic due to minimal content. The technical debt cannot be assessed but the current setup suggests a development or staging environment rather than a production site.
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

Earlier scans of this domain

  1. 90/100Low14 findingsView report
Reviews of this site

Share your experience with ncheckout.dev. 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 ncheckout.dev.

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.